mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
To: Tomas Winkler <tomas.winkler@intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Alexander Usyskin <alexander.usyskin@intel.com>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [char-misc-next] mei: me: allow runtime pm for platform with D0i3
Date: Wed, 3 Jan 2018 13:26:22 +0100	[thread overview]
Message-ID: <da1323db-510f-f089-dbb1-ece0860b4786@intel.com> (raw)
In-Reply-To: <20180102100141.703-1-tomas.winkler@intel.com>

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".

The change itself look OK, though.

> This policy cannot be applied globally as some older platforms
> were found to have broken power management.
>
> Cc: <stable@vger.kernel.org> v4.13+
> Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
> Reviewed-by: Alexander Usyskin <alexander.usyskin@intel.com>
> ---
>   drivers/misc/mei/pci-me.c | 5 ++++-
>   1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/misc/mei/pci-me.c b/drivers/misc/mei/pci-me.c
> index f4f17552c9b8..4a0ccda4d04b 100644
> --- a/drivers/misc/mei/pci-me.c
> +++ b/drivers/misc/mei/pci-me.c
> @@ -238,8 +238,11 @@ static int mei_me_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
>   	 */
>   	mei_me_set_pm_domain(dev);
>   
> -	if (mei_pg_is_enabled(dev))
> +	if (mei_pg_is_enabled(dev)) {
>   		pm_runtime_put_noidle(&pdev->dev);
> +		if (hw->d0i3_supported)
> +			pm_runtime_allow(&pdev->dev);
> +	}
>   
>   	dev_dbg(&pdev->dev, "initialization successful.\n");
>   

  reply	other threads:[~2018-01-03 12:26 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 [this message]
2018-01-04  8:27   ` Winkler, Tomas
2018-01-04 15:47     ` Rafael J. Wysocki

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=da1323db-510f-f089-dbb1-ece0860b4786@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®