From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com ([192.55.52.93]:25762 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755103AbdKGAtG (ORCPT ); Mon, 6 Nov 2017 19:49:06 -0500 Subject: Re: Patch "PM / QoS: Fix default runtime_pm device resume latency" has been added to the 4.13-stable tree To: gregkh@linuxfoundation.org Cc: t-kristo@ti.com, stable@vger.kernel.org, stable-commits@vger.kernel.org References: <1509893078233166@kroah.com> From: "Rafael J. Wysocki" Message-ID: <4e20ae00-83c4-660b-0a5d-1fc6a8411e2a@intel.com> Date: Tue, 7 Nov 2017 01:49:03 +0100 MIME-Version: 1.0 In-Reply-To: <1509893078233166@kroah.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Sender: stable-owner@vger.kernel.org List-ID: 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 know about it. > > > From 2a9a86d5c81389cd9afe6a4fea42c585733cd705 Mon Sep 17 00:00:00 2001 > From: Tero Kristo > Date: Mon, 30 Oct 2017 09:10:46 +0200 > Subject: PM / QoS: Fix default runtime_pm device resume latency > > From: Tero Kristo > > 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 > Signed-off-by: Rafael J. Wysocki > Signed-off-by: Greg Kroah-Hartman > > --- > 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