All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
To: gregkh@linuxfoundation.org
Cc: t-kristo@ti.com, stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "PM / QoS: Fix default runtime_pm device resume latency" has been added to the 4.13-stable tree
Date: Tue, 7 Nov 2017 01:49:03 +0100	[thread overview]
Message-ID: <4e20ae00-83c4-660b-0a5d-1fc6a8411e2a@intel.com> (raw)
In-Reply-To: <1509893078233166@kroah.com>

On 11/5/2017 3:44 PM, gregkh@linuxfoundation.org wrote:
> This is a note to let you know that I've just added the patch titled
>
>      PM / QoS: Fix default runtime_pm device resume latency
>
> to the 4.13-stable tree which can be found at:
>      http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> The filename of the patch is:
>       pm-qos-fix-default-runtime_pm-device-resume-latency.patch
> and it can be found in the queue-4.13 subdirectory.
>
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.
>
>
>  From 2a9a86d5c81389cd9afe6a4fea42c585733cd705 Mon Sep 17 00:00:00 2001
> From: Tero Kristo <t-kristo@ti.com>
> Date: Mon, 30 Oct 2017 09:10:46 +0200
> Subject: PM / QoS: Fix default runtime_pm device resume latency
>
> From: Tero Kristo <t-kristo@ti.com>
>
> commit 2a9a86d5c81389cd9afe6a4fea42c585733cd705 upstream.
>
> The recent change to the PM QoS framework to introduce a proper
> no constraint value overlooked to handle the devices which don't
> implement PM QoS OPS.  Runtime PM is one of the more severely
> impacted subsystems, failing every attempt to runtime suspend
> a device.  This leads into some nasty second level issues like
> probe failures and increased power consumption among other
> things.
>
> Fix this by adding a proper return value for devices that don't
> implement PM QoS.
>
> Fixes: 0cc2b4e5a020 (PM / QoS: Fix device resume latency PM QoS)
> Signed-off-by: Tero Kristo <t-kristo@ti.com>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> ---
>   include/linux/pm_qos.h |    3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
>
> --- a/include/linux/pm_qos.h
> +++ b/include/linux/pm_qos.h
> @@ -175,7 +175,8 @@ static inline s32 dev_pm_qos_requested_f
>   static inline s32 dev_pm_qos_raw_read_value(struct device *dev)
>   {
>   	return IS_ERR_OR_NULL(dev->power.qos) ?
> -		0 : pm_qos_read_value(&dev->power.qos->resume_latency);
> +		PM_QOS_RESUME_LATENCY_NO_CONSTRAINT :
> +		pm_qos_read_value(&dev->power.qos->resume_latency);
>   }
>   #else
>   static inline enum pm_qos_flags_status __dev_pm_qos_flags(struct device *dev,
>
>
> Patches currently in stable-queue which might be from t-kristo@ti.com are
>
> queue-4.13/pm-qos-fix-default-runtime_pm-device-resume-latency.patch

Please drop this from the -stable queue, it has been reverted from the 
mainline.

Thanks,

Rafael

  reply	other threads:[~2017-11-07  0:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-05 14:44 Patch "PM / QoS: Fix default runtime_pm device resume latency" has been added to the 4.13-stable tree gregkh
2017-11-07  0:49 ` Rafael J. Wysocki [this message]
2017-11-07 10:32   ` Greg KH

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=4e20ae00-83c4-660b-0a5d-1fc6a8411e2a@intel.com \
    --to=rafael.j.wysocki@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=t-kristo@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.