From: Tony Lindgren <tony@atomide.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Jan Kiszka <jan.kiszka@web.de>, Kalle Valo <kvalo@codeaurora.org>,
Eyal Reizer <eyalr@ti.com>,
linux-wireless@vger.kernel.org,
Ricardo Salveti <rsalveti@rsalveti.net>,
Kishon Vijay Abraham I <kishon@ti.com>,
Anders Roxell <anders.roxell@linaro.org>,
John Stultz <john.stultz@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [PATCH V2] wlcore: sdio: Fixup power on/off sequence
Date: Fri, 18 Jan 2019 07:35:42 -0800 [thread overview]
Message-ID: <20190118153541.GU5544@atomide.com> (raw)
In-Reply-To: <CAPDyKFo=m50jiQ639xzP9tzn+=Bn0CXXwO6p0_jPH0EnSc0UQg@mail.gmail.com>
* Ulf Hansson <ulf.hansson@linaro.org> [190118 15:09]:
> On Fri, 18 Jan 2019 at 13:09, Jan Kiszka <jan.kiszka@web.de> wrote:
> > Yeah, I'm not claiming at all I know what I'm doing there, just that it happens
> > to work.
>
> I see. Good to know, thanks!
This seems like some separate issue. I wonder if adding
another reset just before pm_runtime_put() clears this
one instead of using the msleep? Just guessing..
Regards,
Tony
next prev parent reply other threads:[~2019-01-18 15:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 11:37 [PATCH V2] wlcore: sdio: Fixup power on/off sequence Ulf Hansson
2019-01-16 15:43 ` Tony Lindgren
2019-01-16 15:48 ` Ulf Hansson
2019-01-16 16:18 ` Kalle Valo
2019-01-18 15:05 ` Anders Roxell
2019-01-18 15:36 ` Kalle Valo
2019-01-18 15:49 ` Tony Lindgren
2019-01-16 20:26 ` Jan Kiszka
2019-01-17 9:54 ` Ulf Hansson
2019-01-18 12:09 ` Jan Kiszka
2019-01-18 15:09 ` Ulf Hansson
2019-01-18 15:35 ` Tony Lindgren [this message]
2019-01-21 14:40 ` Ulf Hansson
2019-01-21 19:30 ` Tony Lindgren
2019-01-22 16:08 ` Jan Kiszka
2019-01-23 8:50 ` Ulf Hansson
2019-01-23 20:17 ` Jan Kiszka
2019-01-23 21:18 ` Ulf Hansson
2019-01-22 16:24 ` Kalle Valo
[not found] ` <20190122162421.7F047609B4@smtp.codeaurora.org>
2019-01-23 8:52 ` Ulf Hansson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190118153541.GU5544@atomide.com \
--to=tony@atomide.com \
--cc=anders.roxell@linaro.org \
--cc=eyalr@ti.com \
--cc=jan.kiszka@web.de \
--cc=john.stultz@linaro.org \
--cc=kishon@ti.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rsalveti@rsalveti.net \
--cc=ulf.hansson@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).