From: Sudeep Holla <sudeep.holla@arm.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Lukasz Luba <lukasz.luba@arm.com>,
rui.zhang@intel.com, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
"open list:CPU IDLE TIME MANAGEMENT FRAMEWORK"
<linux-pm@vger.kernel.org>, Sudeep Holla <sudeep.holla@arm.com>,
open list <linux-kernel@vger.kernel.org>,
"open list:CPUIDLE DRIVER - ARM PSCI"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4 4/4] thermal: cpuidle: Register cpuidle cooling device
Date: Fri, 15 May 2020 10:58:02 +0100 [thread overview]
Message-ID: <20200515095751.GA25267@bogus> (raw)
In-Reply-To: <f3cee834-4946-10bd-a504-df6cf62d9e90@linaro.org>
On Mon, May 04, 2020 at 08:00:01PM +0200, Daniel Lezcano wrote:
>
> Hi,
>
> On 29/04/2020 23:01, Daniel Lezcano wrote:
> > On 29/04/2020 22:02, Lukasz Luba wrote:
> >>
> >>
> >> On 4/29/20 11:36 AM, Daniel Lezcano wrote:
> >>> The cpuidle driver can be used as a cooling device by injecting idle
> >>> cycles. The DT binding for the idle state added an optional
> >>>
> >>> When the property is set, register the cpuidle driver with the idle
> >>> state node pointer as a cooling device. The thermal framework will do
> >>> the association automatically with the thermal zone via the
> >>> cooling-device defined in the device tree cooling-maps section.
> >>>
> >>> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> >>> ---
> >>> - V4:
> >>> - Do not check the return value as the function does no longer
> >>> return one
> >>> ---
> >
> > [ ... ]
> >
> >> Reviewed-by: Lukasz Luba <lukasz.luba@arm.com>
> >
> > Thanks Lukasz for the review.
> >
> > Rafael, as Lorenzo and Sudeep are not responsive, could you consider ack
> > this patch so I can merge the series through the thermal tree ?
>
> Gentle ping ... Sudeep, Lorenzo or Rafael ?
>
Sorry for the delay. I ignore this as it was generic and I was fine with
it. Didn't know you were waiting me, sorry for that.
FWIW:
Acked-by: Sudeep Holla <sudeep.holla@arm.com>
--
Regards,
Sudeep
next prev parent reply other threads:[~2020-05-15 9:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 10:36 [PATCH v4 1/4] powercap/drivers/idle_inject: Specify idle state max latency Daniel Lezcano
2020-04-29 10:36 ` [PATCH v4 2/4] dt-bindings: thermal: Add the idle cooling device Daniel Lezcano
2020-05-06 9:57 ` Amit Kucheria
2020-04-29 10:36 ` [PATCH v4 3/4] thermal/drivers/cpuidle_cooling: Change the registration function Daniel Lezcano
2020-04-29 20:00 ` Lukasz Luba
2020-05-06 9:57 ` Amit Kucheria
2025-04-11 20:14 ` Konrad Dybcio
2020-04-29 10:36 ` [PATCH v4 4/4] thermal: cpuidle: Register cpuidle cooling device Daniel Lezcano
2020-04-29 20:02 ` Lukasz Luba
2020-04-29 21:01 ` Daniel Lezcano
2020-05-04 18:00 ` Daniel Lezcano
2020-05-15 9:58 ` Sudeep Holla [this message]
2020-05-15 11:03 ` Daniel Lezcano
2020-05-06 9:57 ` Amit Kucheria
2020-06-15 11:25 ` Ulf Hansson
2020-05-06 9:56 ` [PATCH v4 1/4] powercap/drivers/idle_inject: Specify idle state max latency Amit Kucheria
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=20200515095751.GA25267@bogus \
--to=sudeep.holla@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=lukasz.luba@arm.com \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@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;
as well as URLs for NNTP newsgroup(s).