From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
To: "Winkler, Tomas" <tomas.winkler@intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Usyskin, Alexander" <alexander.usyskin@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [char-misc-next] mei: me: allow runtime pm for platform with D0i3
Date: Thu, 4 Jan 2018 16:47:01 +0100 [thread overview]
Message-ID: <ff398866-b49e-c7e6-f55d-7e0818501e31@intel.com> (raw)
In-Reply-To: <5B8DA87D05A7694D9FA63FD143655C1B74A8C3F3@hasmsx108.ger.corp.intel.com>
On 1/4/2018 9:27 AM, Winkler, Tomas wrote:
> mei: me: allow runtime pm for platform with
>> D0i3
>>
>> On 1/2/2018 11:01 AM, Tomas Winkler wrote:
>>> From the pci power documentation:
>>> "The driver itself should not call pm_runtime_allow(), though.
>>> Instead, it should let user space or some platform-specific code do
>>> that (user space can do it via sysfs as stated above)..."
>>>
>>> However, the S0ix residency cannot be reached without MEI device
>>> getting into low power state. Hence, for mei devices that support
>>> D0i3, it's better to make runtime power management mandatory and not
>>> rely on the system integration such as udev rules.
>> It still is not mandatory with this change. The default changes from "on" to
>> "auto", but still user space can change it back to "on".
> That's correct, maybe better statement would be 'default setting' instead of 'mandatory'.
> I can respin the patch if needed, let me know.
Greg has applied it already it seems, so I guess that shouldn't be
necessary. :-)
Thanks,
Rafael
prev parent reply other threads:[~2018-01-04 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 10:01 Tomas Winkler
2018-01-03 12:26 ` Rafael J. Wysocki
2018-01-04 8:27 ` Winkler, Tomas
2018-01-04 15:47 ` Rafael J. Wysocki [this message]
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=ff398866-b49e-c7e6-f55d-7e0818501e31@intel.com \
--to=rafael.j.wysocki@intel.com \
--cc=alexander.usyskin@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tomas.winkler@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
all inboxes | Powered by JetHome®