[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1453799572.30130.51.camel@collabora.co.uk>
Date: Tue, 26 Jan 2016 10:12:52 +0100
From: Sjoerd Simons <sjoerd.simons@...labora.co.uk>
To: Arend van Spriel <arend@...adcom.com>,
Doug Anderson <dianders@...omium.org>,
Arend van Spriel <aspriel@...il.com>
Cc: Kalle Valo <kvalo@...eaurora.org>,
Paul Stewart <pstew@...omium.org>,
"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
Pieter-Paul Giesberts <pieterpg@...adcom.com>,
brcm80211-dev-list@...adcom.com,
"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
"linux-kernel@...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>,
Adrian Hunter <adrian.hunter@...el.com>,
"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>
Subject: Re: [PATCH] brcmfmac: sdio: Increase the default timeouts a bit
On Mon, 2016-01-25 at 21:07 +0100, Arend van Spriel wrote:
> On 25-1-2016 20:23, Doug Anderson wrote:
> > Kinda curious: do we get one or two really slow responses on every
> > bootup, or just some bootups? Do we ever succeed even with a slow
> > (like 1.8 or 1.9 seconds) response, or is it always either "fast"
> > or
> > "2.1" seconds?
>
> Now these are interesting questions that I should have spilled out in
> the first place. Thanks.
I would need to get a more data to really conclusively say, but what i
saw in testing thusfar was:
* The issue occurs on _some_ boots
* The issue seems to come up more often on warm reboots
* The likelyhood seemed to change depending on the kernel
configuration (iotw when the initilisation order/timing changed?)
* Forcing the brcmfmac module to load later in boot seemed to make the
likelyhood of the issue showing up lower.
* The samples I have with traces showed either quick responses on
success or slow "2.1" seconds responses on failure.
I'll try to make some time to get some statistics over a series of
boots wrt. the response time(s) for control messages so we can get a
better idea how often this happens and its behaviour.
I guess one other thing to note is that both Doug and myself were
seeing this on Rockchip RK3288 based devices. It would ofcourse be
interesting to know if this has been seen on other types of devices..
--
Sjoerd Simons
Collabora Ltd.
Powered by blists - more mailing lists