linux-kernel - Re: [v2] wlcore: sdio: allow pm to handle sdio power

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]

Message-Id: <20180430103127.274E86079C@smtp.codeaurora.org>
Date:   Mon, 30 Apr 2018 10:31:27 +0000 (UTC)
From:   Kalle Valo <kvalo@...eaurora.org>
To:     Eyal Reizer <eyalreizer@...il.com>
Cc:     linux-wireless@...r.kernel.org, robh@...nel.org, sre@...nel.org,
        tony@...mide.com, linux-kernel@...r.kernel.org,
        Eyal Reizer <eyalr@...com>
Subject: Re: [v2] wlcore: sdio: allow pm to handle sdio power

Eyal Reizer <eyalreizer@...il.com> wrote:

> pm_runtime handles sdio power on and power off transitions.
> An old workaround for trying to control the power explicitly from the
> driver was in fact causing failures on suspend/resume as the mmc layer
> already power the module on resume.
> 
> In case of resume pm_runtime_get sync returns a positive device's usage
> count causing the driver to try an re-initialize an already initialized
> device. This was causing sdio bus failure on resume.
> 
> Remove this manual power on/off sequence as it is in-fact not needed.
> 
> Signed-off-by: Eyal Reizer <eyalr@...com>
> Acked-by: Tony Lindgren <tony@...mide.com>

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

60f36637bbbd wlcore: sdio: allow pm to handle sdio power

-- 
https://patchwork.kernel.org/patch/10364645/

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