[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190611234543.GI137143@google.com>
Date: Tue, 11 Jun 2019 16:45:43 -0700
From: Matthias Kaehlcke <mka@...omium.org>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: Rafael Wysocki <rjw@...ysocki.net>,
Len Brown <len.brown@...el.com>, Pavel Machek <pavel@....cz>,
Kevin Hilman <khilman@...nel.org>,
Ulf Hansson <ulf.hansson@...aro.org>, linux-pm@...r.kernel.org,
Vincent Guittot <vincent.guittot@...aro.org>,
Qais.Yousef@....com, juri.lelli@...il.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH V3 1/5] PM / QOS: Pass request type to
dev_pm_qos_{add|remove}_notifier()
On Mon, Jun 10, 2019 at 04:21:32PM +0530, Viresh Kumar wrote:
> In order to use the same set of routines to register notifiers for
> different request types, update the existing
> dev_pm_qos_{add|remove}_notifier() routines with an additional
> parameter: request-type.
>
> For now, it only supports resume-latency request type.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@...aro.org>
> ---
> Documentation/power/pm_qos_interface.txt | 10 ++++++----
> drivers/base/power/domain.c | 8 +++++---
> drivers/base/power/qos.c | 14 ++++++++++++--
> include/linux/pm_qos.h | 12 ++++++++----
> 4 files changed, 31 insertions(+), 13 deletions(-)
My QoS background is nil, but this looks reasonable to me:
Reviewed-by: Matthias Kaehlcke <mka@...omium.org>
Powered by blists - more mailing lists