[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <F311713B-D7DC-4029-90F2-5E162648349D@gmail.com>
Date: Tue, 24 Dec 2019 13:44:55 +0400
From: Christian Hewitt <christianshewitt@...il.com>
To: Arend Van Spriel <arend.vanspriel@...adcom.com>
Cc: Soeren Moch <smoch@....de>, Kalle Valo <kvalo@...eaurora.org>,
Heiko Stuebner <heiko@...ech.de>,
linux-wireless@...r.kernel.org,
brcm80211-dev-list.pdl@...adcom.com,
brcm80211-dev-list@...ress.com, netdev@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org,
Neil Armstrong <narmstrong@...libre.com>
Subject: Re: [PATCH v2 0/9] brcmfmac: add support for BCM4359 SDIO chipset
> On 24 Dec 2019, at 1:01 pm, Arend Van Spriel <arend.vanspriel@...adcom.com> wrote:
>
> Can you elaborate on the "known SDIO issue"? Is it an issue with ADMA or something else. I am asking because there is a workaround in brcmfmac to avoid scatter-gather lists, which may or may not address the issue.
This describes the issue: https://patchwork.kernel.org/cover/10962975/
Below is the current workaround I’m using, which restricts the hack to Amlogic G12A and G12B devices that inherit “amlogic,dram-access-quirk” from a common SoC dtsi.
https://github.com/chewitt/linux/commit/187527747861b047c835f494fe3267d9b4959be1
Testing by Khadas staff found the max_segs/max_blk_count values and shows a performance impact (not a big surprise) but they appear to give a stable connection, which is better than a very unstable one. I’ve flagged things to linux-amlogic maintainer Neil Armstrong (on CC) and I expect he or colleagues will take a more scientific look in January.
NB: I’m happy to test other things. Just remember that I don’t code so you need to spoon-feed me with patches not suggestions.
Christian
Powered by blists - more mailing lists