From: Tero Kristo <t-kristo@ti.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux PM <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Reinette Chatre <reinette.chatre@intel.com>,
Ramesh Thomas <ramesh.thomas@intel.com>,
Alex Shi <alex.shi@linaro.org>
Subject: Re: [RFT][PATCH v2 0/2] PM / QoS: Device resume latency framework fix
Date: Wed, 8 Nov 2017 11:09:48 +0200 [thread overview]
Message-ID: <e6630875-b145-cedd-e204-9048c104b96b@ti.com> (raw)
In-Reply-To: <2157585.74BgekV60d@aspire.rjw.lan>
On 07/11/17 03:08, Rafael J. Wysocki wrote:
> On Monday, November 6, 2017 2:46:48 PM CET Geert Uytterhoeven wrote:
>> Hi Rafael,
>>
>> On Fri, Nov 3, 2017 at 12:42 PM, Rafael J. Wysocki <rjw@rjwysocki.net> wrote:
>>> On Thursday, November 2, 2017 12:00:27 AM CET Rafael J. Wysocki wrote:
>>>> This series is a replacement for commit 0cc2b4e5a020 (PM / QoS: Fix device
>>>> resume latency PM QoS) that had to be reverted due to problems introduced by it.
>>>>
>>>> This time the genpd PM QoS governor is first updated to be more consistent
>>>> and the PM QoS changes are made on top of that which simplifies the second
>>>> patch quite a bit.
>>>>
>>>> This is based on the linux-next branch from linux-pm.git as of now (should
>>>> also apply to the current mainline just fine).
>>>>
>>>> Please test if you can or let me know if you have any comments.
>>>
>>> The v2 removes a couple of redundant checks from the first patch (and add
>>> comments to explain why the checks are not needed) and fixes up the
>>> "no constraint" value collision with a valid constraint multiplied by
>>> NSEC_PER_USEC in the second patch.
>>>
>>> Please test if possible and let me know about any issues.
>>
>> With this series, the 3 issues I reported before do not happen.
>>
>> Tested-by: Geert Uytterhoeven <geert+renesas@glider.be>
>>
>> Thank you.
>
> Thanks!
>
> Rafael
>
The latest patches (#1 v3 and #2 v4) seem to work fine in my sanity
tests also.
Tested-by: Tero Kristo <t-kristo@ti.com>
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
next prev parent reply other threads:[~2017-11-08 9:11 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 23:00 [RFT][PATCH 0/2] PM / QoS: Device resume latency framework fix Rafael J. Wysocki
2017-11-01 23:01 ` [RFT][PATCH 1/2] PM / domains: Rework governor code to be more consistent Rafael J. Wysocki
2017-11-03 7:05 ` Ramesh Thomas
2017-11-03 7:51 ` Rafael J. Wysocki
2017-11-01 23:03 ` [RFT][PATCH 2/2] PM / QoS: Fix device resume latency framework Rafael J. Wysocki
2017-11-03 7:43 ` Ramesh Thomas
2017-11-03 7:58 ` Rafael J. Wysocki
2017-11-03 10:38 ` Rafael J. Wysocki
2017-11-03 11:42 ` [RFT][PATCH v2 0/2] PM / QoS: Device resume latency framework fix Rafael J. Wysocki
2017-11-03 11:47 ` [RFT][PATCH v2 1/2] PM / domains: Rework governor code to be more consistent Rafael J. Wysocki
2017-11-04 2:34 ` Ramesh Thomas
2017-11-04 11:24 ` Rafael J. Wysocki
2017-11-06 7:47 ` Ramesh Thomas
2017-11-06 12:10 ` Ulf Hansson
2017-11-06 12:34 ` Rafael J. Wysocki
2017-11-06 12:44 ` Ulf Hansson
2017-11-06 12:49 ` Rafael J. Wysocki
2017-11-06 14:38 ` Ulf Hansson
2017-11-06 23:07 ` Rafael J. Wysocki
2017-11-03 11:50 ` [RFT][PATCH v2 2/2] PM / QoS: Fix device resume latency framework Rafael J. Wysocki
2017-11-03 16:39 ` Reinette Chatre
2017-11-04 2:28 ` Ramesh Thomas
2017-11-04 11:30 ` Rafael J. Wysocki
2017-11-04 11:58 ` Rafael J. Wysocki
2017-11-04 11:28 ` Rafael J. Wysocki
2017-11-04 2:38 ` Ramesh Thomas
2017-11-04 12:34 ` [RFT][Update][PATCH " Rafael J. Wysocki
2017-11-06 17:47 ` Reinette Chatre
2017-11-07 1:07 ` Rafael J. Wysocki
2017-11-06 13:46 ` [RFT][PATCH v2 0/2] PM / QoS: Device resume latency framework fix Geert Uytterhoeven
2017-11-07 1:08 ` Rafael J. Wysocki
2017-11-08 9:09 ` Tero Kristo [this message]
2017-11-07 1:17 ` [PATCH v3 " Rafael J. Wysocki
2017-11-07 1:23 ` [PATCH v3 1/2] PM / domains: Rework governor code to be more consistent Rafael J. Wysocki
2017-11-07 5:05 ` Ramesh Thomas
2017-11-07 10:22 ` Rafael J. Wysocki
2017-11-07 23:24 ` Ramesh Thomas
2017-11-10 7:49 ` Ulf Hansson
2017-11-07 1:27 ` [PATCH v3 2/2] PM / QoS: Fix device resume latency framework Rafael J. Wysocki
2017-11-07 4:33 ` Ramesh Thomas
2017-11-07 10:12 ` Rafael J. Wysocki
2017-11-07 10:33 ` [PATCH v4 " Rafael J. Wysocki
2017-11-07 23:15 ` Ramesh Thomas
2017-11-08 0:09 ` Rafael J. Wysocki
2017-11-10 7:49 ` Ulf Hansson
2017-11-10 8:03 ` Geert Uytterhoeven
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=e6630875-b145-cedd-e204-9048c104b96b@ti.com \
--to=t-kristo@ti.com \
--cc=alex.shi@linaro.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=ramesh.thomas@intel.com \
--cc=reinette.chatre@intel.com \
--cc=rjw@rjwysocki.net \
--cc=ulf.hansson@linaro.org \
/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).