aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/net/wimax/i2400m/fw.c
diff options
context:
space:
mode:
authorInaky Perez-Gonzalez <inaky@linux.intel.com>2009-06-03 04:13:14 -0400
committerInaky Perez-Gonzalez <inaky@linux.intel.com>2009-06-11 06:30:23 -0400
commitecddfd5ed73c070413f07a5251c16c10e69f35a2 (patch)
tree4caaeedf3b8a49441d3656ffdd2ac8e8479991a2 /drivers/net/wimax/i2400m/fw.c
parentb4013f91cdda10f3f15530914f3c7f39738b0b50 (diff)
wimax/i2400m: Allow bus-specific driver to specify retry count
The code that sets up the i2400m (firmware load and general driver setup after it) includes a couple of retry loops. The SDIO device sometimes can get in more complicated corners than the USB one (due to its interaction with other SDIO functions), that require trying a few more times. To solve that, without having a failing USB device taking longer to be considered dead, allow the retry counts to be specified by the bus-specific driver, which the general driver takes as a parameter. Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com>
Diffstat (limited to 'drivers/net/wimax/i2400m/fw.c')
-rw-r--r--drivers/net/wimax/i2400m/fw.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/net/wimax/i2400m/fw.c b/drivers/net/wimax/i2400m/fw.c
index 01c926ed309e..c48fa241857a 100644
--- a/drivers/net/wimax/i2400m/fw.c
+++ b/drivers/net/wimax/i2400m/fw.c
@@ -980,7 +980,7 @@ int i2400m_fw_dnload(struct i2400m *i2400m, const struct i2400m_bcf_hdr *bcf,
980{ 980{
981 int ret = 0; 981 int ret = 0;
982 struct device *dev = i2400m_dev(i2400m); 982 struct device *dev = i2400m_dev(i2400m);
983 int count = I2400M_BOOT_RETRIES; 983 int count = i2400m->bus_bm_retries;
984 984
985 d_fnstart(5, dev, "(i2400m %p bcf %p size %zu)\n", 985 d_fnstart(5, dev, "(i2400m %p bcf %p size %zu)\n",
986 i2400m, bcf, bcf_size); 986 i2400m, bcf, bcf_size);