From: Kalle Valo <kvalo@codeaurora.org>
To: Tony Lindgren <tony@atomide.com>
Cc: Eyal Reizer <eyalr@ti.com>,
Kishon Vijay Abraham I <kishon@ti.com>, Guy Mishol <guym@ti.com>,
Luca Coelho <luciano.coelho@intel.com>,
Maital Hahn <maitalm@ti.com>,
Maxim Altshul <maxim.altshul@ti.com>,
Shahar Patury <shaharp@ti.com>,
linux-wireless@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [1/8] wlcore: Add missing PM call for wlcore_cmd_wait_for_event_or_timeout()
Date: Wed, 27 Jun 2018 15:46:56 +0000 (UTC) [thread overview]
Message-ID: <20180627154656.9E51960714@smtp.codeaurora.org> (raw)
In-Reply-To: <20180619094342.81831-2-tony@atomide.com>
Tony Lindgren <tony@atomide.com> wrote:
> Otherwise we can get:
>
> WARNING: CPU: 0 PID: 55 at drivers/net/wireless/ti/wlcore/io.h:84
>
> I've only seen this few times with the runtime PM patches enabled
> so this one is probably not needed before that. This seems to
> work currently based on the current PM implementation timer. Let's
> apply this separately though in case others are hitting this issue.
>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
8 patches applied to wireless-drivers-next.git, thanks.
4ec7cece87b3 wlcore: Add missing PM call for wlcore_cmd_wait_for_event_or_timeout()
02edf81362fe wlcore: Make sure PM calls are paired
fa2648a34e73 wlcore: Add support for runtime PM
3ebbabea4219 wlcore: Fix misplaced PM call for scan_complete_work()
db68052bdf58 wlcore: Fix timout errors after recovery
45aa7f071b06 wlcore: Use generic runtime pm calls for wowlan elp configuration
c40aad28a3cf wlcore: Make sure firmware is initialized in wl1271_op_add_interface()
9b71578de087 wlcore: Enable runtime PM autosuspend support
--
https://patchwork.kernel.org/patch/10473893/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2018-06-27 15:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 9:43 [PATCHv4 0/8] Runtime PM support for wlcore Tony Lindgren
2018-06-19 9:43 ` [PATCH 1/8] wlcore: Add missing PM call for wlcore_cmd_wait_for_event_or_timeout() Tony Lindgren
2018-06-27 15:46 ` Kalle Valo [this message]
2018-06-19 9:43 ` [PATCH 2/8] wlcore: Make sure PM calls are paired Tony Lindgren
2018-06-19 9:43 ` [PATCH 3/8] wlcore: Add support for runtime PM Tony Lindgren
2018-06-19 9:43 ` [PATCH 4/8] wlcore: Fix misplaced PM call for scan_complete_work() Tony Lindgren
2018-06-19 9:43 ` [PATCH 5/8] wclore: Fix timout errors after recovery Tony Lindgren
2018-06-27 15:41 ` [5/8] " Kalle Valo
[not found] ` <20180627154152.BCECB60714@smtp.codeaurora.org>
2018-06-28 9:07 ` Tony Lindgren
2018-06-28 9:19 ` Kalle Valo
2018-06-19 9:43 ` [PATCH 6/8] wlcore: Use generic runtime pm calls for wowlan elp configuration Tony Lindgren
2018-06-19 9:43 ` [PATCH 7/8] wlcore: Make sure firmware is initialized in wl1271_op_add_interface() Tony Lindgren
2018-06-19 9:43 ` [PATCH 8/8] wlcore: Enable runtime PM autosuspend support Tony Lindgren
2018-06-26 15:53 ` [PATCHv4 0/8] Runtime PM support for wlcore Kalle Valo
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=20180627154656.9E51960714@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=eyalr@ti.com \
--cc=guym@ti.com \
--cc=kishon@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--cc=maitalm@ti.com \
--cc=maxim.altshul@ti.com \
--cc=shaharp@ti.com \
--cc=tony@atomide.com \
/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).