[<prev] [next>] [day] [month] [year] [list]
Message-ID: <9217d183-69ec-8be1-217e-0e4d67710743@gmail.com>
Date: Wed, 18 Dec 2019 22:11:58 +0300
From: Dmitry Osipenko <digetx@...il.com>
To: Kalle Valo <kvalo@...eaurora.org>
Cc: Thierry Reding <thierry.reding@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>,
Arend van Spriel <arend.vanspriel@...adcom.com>,
Franky Lin <franky.lin@...adcom.com>,
Hante Meuleman <hante.meuleman@...adcom.com>,
Chi-Hsien Lin <chi-hsien.lin@...ress.com>,
Wright Feng <wright.feng@...ress.com>,
linux-wireless@...r.kernel.org,
brcm80211-dev-list.pdl@...adcom.com,
brcm80211-dev-list@...ress.com, linux-tegra@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] brcmfmac: Keep OOB wake-interrupt disabled when it
shouldn't be enabled
18.12.2019 22:09, Kalle Valo пишет:
> Dmitry Osipenko <digetx@...il.com> wrote:
>
>> NVIDIA Tegra SoCs do not like when OOB wake is enabled and WiFi interface
>> is in DOWN state during suspend. This results in a CPU hang on programming
>> OOB wake-up state of the GPIO controller during of system's suspend.
>>
>> The solution is trivial: don't enable wake for the OOB interrupt when it
>> should be disabled.
>>
>> This fixes hang on Tegra20 (Acer A500) and Tegra30 (Nexus 7) devices which
>> are using BCM4329 and BCM4330 WiFi chips respectively.
>>
>> Signed-off-by: Dmitry Osipenko <digetx@...il.com>
>
> Patch applied to wireless-drivers-next.git, thanks.
>
> a32de68edab7 brcmfmac: Keep OOB wake-interrupt disabled when it shouldn't be enabled
>
Thank you very much!
Powered by blists - more mailing lists