From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: cwchoi00@gmail.com
Cc: Lukasz Luba <lukasz.luba@arm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>,
Steven Price <steven.price@arm.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>
Subject: Re: [PATCH v3 1/4] devfreq: Register devfreq as a cooling device on demand
Date: Sun, 7 Mar 2021 15:28:59 +0100 [thread overview]
Message-ID: <76b5b6bc-952b-aa7c-025b-3eeb2ca23c79@linaro.org> (raw)
In-Reply-To: <CAGTfZH3jFJ8CaJ1Yg=oxhVSYVDULWr83iPokL+tut8mKgSufFA@mail.gmail.com>
On 07/03/2021 15:16, Chanwoo Choi wrote:
> On 21. 3. 7. 오후 6:45, Daniel Lezcano wrote:
>> Currently the default behavior is to manually having the devfreq
>> backend to register themselves as a devfreq cooling device.
>>
>> Instead of adding the code in the drivers for the thermal cooling
>> device registering, let's provide a flag in the devfreq's profile to
>> tell the common devfreq code to register the newly created devfreq as
>> a cooling device.
>>
>> Suggested-by: Chanwoo Choi <cwchoi00@gmail.com>
>> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
>> ---
>> V3:
>> - Rebased on linux-pm branch without units.h
>> - Set the cdev to NULL in case of error
>> - Added description for the cdev field in the devfreq structure
>> V2:
>> - Added is_cooling_device boolean in profile structure
>> - Register cooling device when the is_cooling_device boolean is set
>> - Remove devfreq cooling device registration in the backend drivers
>> V1:
>> - Register devfreq as a cooling device unconditionnally
>> ---
[ ... ]
>> return devfreq;
>>
>> err_init:
>> @@ -960,6 +971,8 @@ int devfreq_remove_device(struct devfreq *devfreq)
>> if (!devfreq)
>> return -EINVAL;
>>
>> + thermal_cooling_device_unregister(devfreq->cdev);
>
> I have a question. Why don't you use devfreq_cooling_unregister()?
> When thermal_cooling_device_unregister(), how can we remove
> the pm_qos_request of devfreq device?
You are perfectly right. I failed to call the right function :/
Will fix it with a v4.
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2021-03-07 14:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 9:45 Daniel Lezcano
2021-03-07 9:45 ` [PATCH v3 2/4] devfreq/drivers/msm: Use devfreq cooling device registration Daniel Lezcano
2021-03-07 9:45 ` [PATCH v3 3/4] devfreq/drivers/panfrost: " Daniel Lezcano
2021-03-07 9:45 ` [PATCH v3 4/4] devfreq/drivers/lima: " Daniel Lezcano
2021-03-07 14:15 ` [PATCH v3 1/4] devfreq: Register devfreq as a cooling device on demand Chanwoo Choi
2021-03-07 14:16 ` Chanwoo Choi
2021-03-07 14:28 ` Daniel Lezcano [this message]
2021-03-07 15:14 ` Chanwoo Choi
2021-03-07 15:16 ` 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=76b5b6bc-952b-aa7c-025b-3eeb2ca23c79@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=cw00.choi@samsung.com \
--cc=cwchoi00@gmail.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=myungjoo.ham@samsung.com \
--cc=steven.price@arm.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®