[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20160206115910.E1D026029F@smtp.codeaurora.org>
Date: Sat, 6 Feb 2016 11:59:10 +0000 (UTC)
From: Kalle Valo <kvalo@...eaurora.org>
To: Sjoerd Simons <sjoerd.simons@...labora.co.uk>
Cc: Paul Stewart <pstew@...omium.org>,
Doug Anderson <dianders@...omium.org>,
linux-rockchip@...ts.infradead.org,
Arend van Spriel <arend@...adcom.com>,
Pieter-Paul Giesberts <pieterpg@...adcom.com>,
brcm80211-dev-list@...adcom.com, linux-wireless@...r.kernel.org,
linux-kernel@...r.kernel.org,
Hante Meuleman <meuleman@...adcom.com>,
Brett Rudley <brudley@...adcom.com>, netdev@...r.kernel.org,
"Franky (Zhenhui) Lin" <frankyl@...adcom.com>
Subject: Re: 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@...labora.co.uk>
> Reviewed-by: Julian Calaby <julian.calaby@...il.com>
> Acked-by: Arend van Spriel <arend@...adcom.com>
> Reviewed-by: Douglas Anderson <dianders@...omium.org>
Thanks, applied to wireless-drivers-next.git.
Kalle Valo
Powered by blists - more mailing lists