summaryrefslogtreecommitdiff
path: root/drivers/net/wimax/i2400m/usb-fw.c
diff options
context:
space:
mode:
authorInaky Perez-Gonzalez <inaky@linux.intel.com>2009-10-24 00:48:36 (GMT)
committerInaky Perez-Gonzalez <inaky@linux.intel.com>2009-11-03 20:49:39 (GMT)
commitfae92216da87d1c78aa51c4503acb312a47266e9 (patch)
tree0df0784e265e6ec55eb0ed5566b8bf99e1dd2ba7 /drivers/net/wimax/i2400m/usb-fw.c
parent02eb41ef2a8631022fd90e096c57562dec9e7a9a (diff)
downloadlinux-fsl-qoriq-fae92216da87d1c78aa51c4503acb312a47266e9.tar.xz
wimax/i2400m: don't retry SDIO enable in probe() paths
The iwmc3200 has a quirk where retrying SDIO enable during the probe() path causes bad interactions with the TOP function controller that causes a reset storm. The workaround is simply not to retry an SDIO enable in said path (and still do in the reset / reinitialization paths). The driver does so by checking i2400ms->debugfs_dentry to see if it has been initialized; if not, it is in the probe() path. Document said fact in i2400ms->debugfs_entry. Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com>
Diffstat (limited to 'drivers/net/wimax/i2400m/usb-fw.c')
0 files changed, 0 insertions, 0 deletions