From: Lukasz Luba <lukasz.luba@arm.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: rjw@rjwysocki.net, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Zhang Rui <rui.zhang@intel.com>, Amit Kucheria <amitk@kernel.org>
Subject: Re: [PATCH v3 1/2] thermal/core: Make the userspace governor deprecated
Date: Thu, 21 Oct 2021 16:30:28 +0100 [thread overview]
Message-ID: <942b9998-9858-7776-97b7-b5ac1c637a2e@arm.com> (raw)
In-Reply-To: <6372f16d-7d2d-cb1e-be86-23b21b41816b@linaro.org>
Hi Daniel,
On 10/20/21 11:47 AM, Daniel Lezcano wrote:
>
> Hi Lukasz,
>
> Do you agree with these changes ?
Yes, I agree with these changes.
>
> On 19/10/2021 18:35, Daniel Lezcano wrote:
>> The userspace governor is sending temperature when polling is active
>> and trip point crossed events. Nothing else.
>>
>> AFAICT, this governor is used with custom kernels making the userspace
>> governor co-existing with another governor on the same thermal zone
>> because there was no notification mechanism, implying a hack in the
>> framework to support this configuration.
>>
>> The new netlink thermal notification is able to provide more
>> information than the userspace governor and give the opportunity to
>> the users of this governor to replace it by a dedicated notification
>> framework.
>>
>> The userspace governor will be removed as its usage is no longer
>> needed.
>>
>> Add a warning message to tell the userspace governor is deprecated.
>>
>> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
>> Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>> ---
>> drivers/thermal/gov_user_space.c | 9 +++++++++
>> 1 file changed, 9 insertions(+)
>>
>> diff --git a/drivers/thermal/gov_user_space.c b/drivers/thermal/gov_user_space.c
>> index 82a7198bbe71..f4fe050e1cbc 100644
>> --- a/drivers/thermal/gov_user_space.c
>> +++ b/drivers/thermal/gov_user_space.c
>> @@ -15,6 +15,14 @@
>>
>> #include "thermal_core.h"
>>
>> +static int user_space_bind(struct thermal_zone_device *tz)
>> +{
>> + pr_warn("Userspace governor deprecated: use thermal netlink " \
>> + "notification instead\n");
>> +
>> + return 0;
>> +}
>> +
>> /**
>> * notify_user_space - Notifies user space about thermal events
>> * @tz: thermal_zone_device
>> @@ -43,5 +51,6 @@ static int notify_user_space(struct thermal_zone_device *tz, int trip)
>> static struct thermal_governor thermal_gov_user_space = {
>> .name = "user_space",
>> .throttle = notify_user_space,
>> + .bind_to_tz = user_space_bind,
>> };
>> THERMAL_GOVERNOR_DECLARE(thermal_gov_user_space);
>>
>
>
You can add:
Reviewed-by: Lukasz Luba <lukasz.luba@arm.com>
Regards,
Lukasz
next prev parent reply other threads:[~2021-10-21 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 16:35 Daniel Lezcano
2021-10-19 16:35 ` [PATCH v3 2/2] thermal/core: Deprecate changing cooling device state from userspace Daniel Lezcano
2021-10-19 16:38 ` Rafael J. Wysocki
2021-10-20 10:47 ` [PATCH v3 1/2] thermal/core: Make the userspace governor deprecated Daniel Lezcano
2021-10-21 15:30 ` Lukasz Luba [this message]
2021-10-21 15:35 ` 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=942b9998-9858-7776-97b7-b5ac1c637a2e@arm.com \
--to=lukasz.luba@arm.com \
--cc=amitk@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.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
all inboxes | Powered by JetHome®