Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org E950E600C9
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [v2] wlcore: sdio: allow pm to handle sdio power
From:   Kalle Valo <kvalo@codeaurora.org>
In-Reply-To: <1524721631-5983-1-git-send-email-eyalr@ti.com>
References: <1524721631-5983-1-git-send-email-eyalr@ti.com>
To:     Eyal Reizer <eyalreizer@gmail.com>
Cc:     linux-wireless@vger.kernel.org, robh@kernel.org, sre@kernel.org,
        tony@atomide.com, linux-kernel@vger.kernel.org,
        Eyal Reizer <eyalr@ti.com>
User-Agent: pwcli/0.0.0-git (https://github.com/kvalo/pwcli/) Python/2.7.12
Message-Id: <20180430103127.274E86079C@smtp.codeaurora.org>
Date:   Mon, 30 Apr 2018 10:31:27 +0000 (UTC)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Eyal Reizer <eyalreizer@gmail.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@ti.com>
> Acked-by: Tony Lindgren <tony@atomide.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