summaryrefslogtreecommitdiff
path: root/drivers/firewire/fw-device.c
diff options
context:
space:
mode:
authorKristian Høgsberg <krh@redhat.com>2007-03-27 01:43:43 -0400
committerStefan Richter <stefanr@s5r6.in-berlin.de>2007-03-28 21:30:16 +0200
commitc5dfd0a5b09bf20adf26b3242258679e305c39c8 (patch)
tree13bcdf65831086637e7e6adada7ecc5516842859 /drivers/firewire/fw-device.c
parent93e4fd455c62085cdceea3af4c56d95758d3cb74 (diff)
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>
Diffstat (limited to 'drivers/firewire/fw-device.c')
-rw-r--r--drivers/firewire/fw-device.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/firewire/fw-device.c b/drivers/firewire/fw-device.c
index 5db666fd265b..71976571c807 100644
--- 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)