summaryrefslogtreecommitdiffstats
path: root/drivers/net/wireless/intersil
diff options
context:
space:
mode:
authorSjoerd Simons <sjoerd.simons@collabora.co.uk>2016-01-25 11:47:29 +0100
committerKalle Valo <kvalo@codeaurora.org>2016-02-06 13:58:47 +0200
commit97f1a17109272b9f060cbd6d1d5be41528643000 (patch)
tree1b69a9dca71796cdbf64580c316839a8a33a16fe /drivers/net/wireless/intersil
parentd1e61b86a2b1b99e5dcd4d41aa23d033b83542a1 (diff)
downloadop-kernel-dev-97f1a17109272b9f060cbd6d1d5be41528643000.zip
op-kernel-dev-97f1a17109272b9f060cbd6d1d5be41528643000.tar.gz
brcmfmac: sdio: Increase the default timeouts a bit
On a Radxa Rock2 board with a Ampak AP6335 (Broadcom 4339 core) it seems the card responds very quickly most of the time, unfortunately during initialisation it sometimes seems to take just a bit over 2 seconds to respond. This results intialization failing with message like: brcmf_c_preinit_dcmds: Retreiving cur_etheraddr failed, -52 brcmf_bus_start: failed: -52 brcmf_sdio_firmware_callback: dongle is not responding Increasing the timeout to allow for a bit more headroom allows the card to initialize reliably. A quick search online after diagnosing/fixing this showed that Google has a similar patch in their ChromeOS tree, so this doesn't seem specific to the board I'm using. Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk> Reviewed-by: Julian Calaby <julian.calaby@gmail.com> Acked-by: Arend van Spriel <arend@broadcom.com> Reviewed-by: Douglas Anderson <dianders@chromium.org> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Diffstat (limited to 'drivers/net/wireless/intersil')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud