firewire: Increase the number of config rom retries and the retry delay.

Some devices have a really long power-on cycle, and we fail to
successfully probe these if they're plugged in and then turned on.

There's really no down-side to bumping the number of retries and the
retry delay, and most devices will get picked up within the first couple
of retries anyway.

Signed-off-by: Kristian Høgsberg <krh@redhat.com>
Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>

diff --git a/drivers/firewire/fw-device.c b/drivers/firewire/fw-device.c
index 5db666fd265bed0345e6ee9d32ebdf49a1dd23bc..71976571c80793570f0201e1e5acbcd9d9444963 100644 (file)
--- a/drivers/firewire/fw-device.c
+++ b/drivers/firewire/fw-device.c
@@ -592,8 +592,8 @@ static struct device_type fw_device_type = {
  * aggressive than that, since it scales pretty well; if 10 devices
  * are plugged in, they're all getting read within one second. */
 
-#define MAX_RETRIES    5
-#define RETRY_DELAY    (2 * HZ)
+#define MAX_RETRIES    10
+#define RETRY_DELAY    (3 * HZ)
 #define INITIAL_DELAY  (HZ / 2)
 
 static void fw_device_init(struct work_struct *work)