From: Lukasz Luba <lukasz.luba@arm.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: rafael@kernel.org, daniel.lezcano@linaro.org, amitk@kernel.org,
rui.zhang@intel.com, linux-pm@vger.kernel.org,
Chetankumar Mistry <chetan.mistry@arm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2][RFC 1/2] Implement Ziegler-Nichols Heuristic
Date: Mon, 20 Dec 2021 09:58:55 +0000 [thread overview]
Message-ID: <a78792dd-f755-59c1-57e5-a9ea9cc18d7f@arm.com> (raw)
In-Reply-To: <28c7a12e-6d85-d15d-8884-997eb68612e9@infradead.org>
Hi Randy,
Chetan is on holidays and I'll respond to feedback.
On 12/18/21 6:07 AM, Randy Dunlap wrote:
>
>
> On 12/17/21 10:49, Chetankumar Mistry wrote:
>> Implement the Ziegler-Nichols Heuristic algorithm to better
>> estimate the PID Coefficients for a running platform.
>> The values are tuned to minimuse the amount of overshoot in
>> the temperature of the platform and subsequently minimise
>> the number of switches for cdev states.
>>
>> Signed-off-by: Chetankumar Mistry <chetan.mistry@arm.com>
>
> The kernel-doc changes all look good and don't cause any warnings.
> Thanks.
Thank you for the testing it.
Regards,
Lukasz
next prev parent reply other threads:[~2021-12-20 9:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 18:49 [PATCH v2][RFC 1/2] Implement Ziegler-Nichols Heuristic Chetankumar Mistry
2021-12-17 18:49 ` [PATCH v2][RFC 2/2] Remove sysfs entry Chetankumar Mistry
2021-12-18 6:07 ` [PATCH v2][RFC 1/2] Implement Ziegler-Nichols Heuristic Randy Dunlap
2021-12-20 9:58 ` Lukasz Luba [this message]
2022-01-06 11:54 ` Lukasz Luba
2022-01-06 12:16 ` Daniel Lezcano
2022-01-06 13:16 ` Lukasz Luba
2022-01-07 11:52 ` Daniel Lezcano
2022-01-07 13:39 ` Lukasz Luba
[not found] ` <DB6PR0802MB22791E85B333050C801ED388F8299@DB6PR0802MB2279.eurprd08.prod.outlook.com>
2022-02-04 11:50 ` Daniel Lezcano
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=a78792dd-f755-59c1-57e5-a9ea9cc18d7f@arm.com \
--to=lukasz.luba@arm.com \
--cc=amitk@kernel.org \
--cc=chetan.mistry@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--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).