From: Johannes Berg <johannes@sipsolutions.net>
To: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
Cc: "Yan, Zheng" <zheng.z.yan@intel.com>,
ilw@linux.intel.com,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH RFC] iwlwifi: add basic runtime PM support
Date: Mon, 09 Jan 2012 10:11:10 +0100 [thread overview]
Message-ID: <1326100270.3451.5.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1326071127.13074.367.camel@wwguy-huron>
On Sun, 2012-01-08 at 17:05 -0800, Guy, Wey-Yi wrote:
> I understand, but unless we figure out either make rkill interrupt works
> in runtime PM, or figure out the platform does not has HW RFKILL
> automatically, I don't see how this patch can upstream without generate
> a lot of issues and bug reports.
I suppose the question is -- will any tools/users enable it and then
scream about their rfkill?
Maybe we can use pm_runtime_forbid() to disable it completely, and add a
module parameter or something to enable it -- just so people are aware
of the tradeoffs?
johannes
next prev parent reply other threads:[~2012-01-09 9:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 2:41 [PATCH RFC] iwlwifi: add basic runtime PM support Yan, Zheng
[not found] ` <4F065F59.2070107-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2012-01-06 9:47 ` Johannes Berg
2012-01-09 1:01 ` Yan, Zheng
2012-01-09 0:34 ` Guy, Wey-Yi
2012-01-09 1:55 ` Yan, Zheng
2012-01-09 1:05 ` Guy, Wey-Yi
2012-01-09 9:04 ` Yan, Zheng
2012-01-09 9:11 ` Johannes Berg [this message]
[not found] ` <1326100270.3451.5.camel-8upI4CBIZJIJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2012-01-09 14:39 ` Guy, Wey-Yi
2012-01-09 9:10 ` Johannes Berg
2012-01-06 15:14 ` wwguy
2012-01-09 1:37 ` Yan, Zheng
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=1326100270.3451.5.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ilw@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wey-yi.w.guy@intel.com \
--cc=zheng.z.yan@intel.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).