netdev - Re: [PATCH] wilc1000: Fix spurious "FW not responding" error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Tue, 14 Dec 2021 18:45:33 +0000 (UTC)
From:   Kalle Valo <kvalo@...nel.org>
To:     David Mosberger-Tang <davidm@...uge.net>
Cc:     Ajay Singh <ajay.kathat@...rochip.com>,
        Claudiu Beznea <claudiu.beznea@...rochip.com>,
        Kalle Valo <kvalo@...eaurora.org>,
        "David S. Miller" <davem@...emloft.net>,
        Jakub Kicinski <kuba@...nel.org>,
        linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        David Mosberger-Tang <davidm@...uge.net>
Subject: Re: [PATCH] wilc1000: Fix spurious "FW not responding" error

David Mosberger-Tang <davidm@...uge.net> wrote:

> When deinitializing the driver, one or more "FW not responding" error
> appears on the console.  This appears to be due to wilc_wlan_stop()
> disabling host/WILC1000 communication, but then right afterwards, it
> tries to release the bus with chip-sleep enabled.  The problem is
> enabling the chip-sleep cannot success once host/WILC1000
> communication is disabled.  Fix by only releasing the bus.
> 
> Signed-off-by: David Mosberger-Tang <davidm@...uge.net>

Patch applied to wireless-drivers-next.git, thanks.

73bbef64bca7 wilc1000: Fix spurious "FW not responding" error

-- 
https://patchwork.kernel.org/project/linux-wireless/patch/20211208062747.3405221-1-davidm@egauge.net/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches