From: Chanwoo Choi <cw00.choi@samsung.com>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Brian Norris <briannorris@chromium.org>,
Douglas Anderson <dianders@chromium.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
Lee Jones <lee.jones@linaro.org>,
Benson Leung <bleung@chromium.org>,
Olof Johansson <olof@lixom.net>
Subject: Re: [PATCH v5 04/12] PM / devfreq: Add struct devfreq_policy
Date: Thu, 12 Jul 2018 17:38:09 +0900 [thread overview]
Message-ID: <4863cf97-37d9-7d81-f44b-10de3dc8267e@samsung.com> (raw)
In-Reply-To: <20180706170701.GF129942@google.com>
Hi Matthias,
On 2018년 07월 07일 02:07, Matthias Kaehlcke wrote:
> Hi,
>
> On Wed, Jul 04, 2018 at 11:51:30AM +0900, Chanwoo Choi wrote:
>> Hi,
>>
>> On 2018년 07월 04일 08:46, Matthias Kaehlcke wrote:
>>> Move variables related with devfreq policy changes from struct devfreq
>>> to the new struct devfreq_policy and add a policy field to struct devfreq.
>>>
>>> The following variables are moved:
>>>
>>> df->min/max_freq => p->user.min/max_freq
>>> df->scaling_min/max_freq => p->devinfo.min/max_freq
>>> df->governor => p->governor
>>> df->governor_name => p->governor_name
>>>
>>> Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
>>> Reviewed-by: Brian Norris <briannorris@chromium.org>
>>> ---
>>> Changes in v5:
>>> - none
>>>
>>> Changes in v4:
>>> - added 'Reviewed-by: Brian Norris <briannorris@chromium.org>' tag
>>>
>>> Changes in v3:
>>> - none
>>>
>>> Changes in v2:
>>> - performance, powersave and simpleondemand governors don't need changes
>>> with "PM / devfreq: Don't adjust to user limits in governors"
>>> - formatting fixes
>>> ---
>>> drivers/devfreq/devfreq.c | 137 ++++++++++++++++-------------
>>> drivers/devfreq/governor_passive.c | 4 +-
>>> include/linux/devfreq.h | 38 +++++---
>
>
>>> 3 files changed, 103 insertions(+), 76 deletions(-)
>>>
>>
>> (skip)
>>
>>>
>>> diff --git a/drivers/devfreq/governor_passive.c b/drivers/devfreq/governor_passive.c
>>> index 3bc29acbd54e..e0987c749ec2 100644
>>> --- a/drivers/devfreq/governor_passive.c
>>> +++ b/drivers/devfreq/governor_passive.c
>>> @@ -99,12 +99,12 @@ static int update_devfreq_passive(struct devfreq *devfreq, unsigned long freq)
>>> {
>>> int ret;
>>>
>>> - if (!devfreq->governor)
>>> + if (!devfreq->policy.governor)
>>> return -EINVAL;
>>>
>>> mutex_lock_nested(&devfreq->lock, SINGLE_DEPTH_NESTING);
>>>
>>> - ret = devfreq->governor->get_target_freq(devfreq, &freq);
>>> + ret = devfreq->policy.governor->get_target_freq(devfreq, &freq);
>>> if (ret < 0)
>>> goto out;
>>>
>>> diff --git a/include/linux/devfreq.h b/include/linux/devfreq.h
>>> index 3aae5b3af87c..9bf23b976f4d 100644
>>> --- a/include/linux/devfreq.h
>>> +++ b/include/linux/devfreq.h
>>> @@ -109,6 +109,30 @@ struct devfreq_dev_profile {
>>> unsigned int max_state;
>>> };
>>>
>>> +/**
>>> + * struct devfreq_freq_limits - Devfreq frequency limits
>>> + * @min_freq: minimum frequency
>>> + * @max_freq: maximum frequency
>>> + */
>>> +struct devfreq_freq_limits {
>>> + unsigned long min_freq;
>>> + unsigned long max_freq;
>>> +};
>>> +
>>> +/**
>>> + * struct devfreq_policy - Devfreq policy
>>> + * @user: frequency limits requested by the user
>>> + * @devinfo: frequency limits of the device (available OPPs)
>>> + * @governor: method how to choose frequency based on the usage.
>>
>> nitpick. remove '.' on the end of line.
>
> Ok
>
>>> + * @governor_name: devfreq governor name for use with this devfreq
>>> + */
>>> +struct devfreq_policy {
>>> + struct devfreq_freq_limits user;
>>> + struct devfreq_freq_limits devinfo;
>>> + const struct devfreq_governor *governor;
>>> + char governor_name[DEVFREQ_NAME_LEN];
>>> +};
>>> +
>>> /**
>>> * struct devfreq - Device devfreq structure
>>> * @node: list node - contains the devices with devfreq that have been
>>> @@ -117,8 +141,6 @@ struct devfreq_dev_profile {
>>> * @dev: device registered by devfreq class. dev.parent is the device
>>> * using devfreq.
>>> * @profile: device-specific devfreq profile
>>> - * @governor: method how to choose frequency based on the usage.
>>> - * @governor_name: devfreq governor name for use with this devfreq
>>> * @nb: notifier block used to notify devfreq object that it should
>>> * reevaluate operable frequencies. Devfreq users may use
>>> * devfreq.nb to the corresponding register notifier call chain.
>>> @@ -126,10 +148,7 @@ struct devfreq_dev_profile {
>>> * @previous_freq: previously configured frequency value.
>>> * @data: Private data of the governor. The devfreq framework does not
>>> * touch this.
>>> - * @min_freq: Limit minimum frequency requested by user (0: none)
>>> - * @max_freq: Limit maximum frequency requested by user (0: none)
>>> - * @scaling_min_freq: Limit minimum frequency requested by OPP interface
>>> - * @scaling_max_freq: Limit maximum frequency requested by OPP interface
>>> + * @policy: Policy for frequency adjustments
>>
>> The devfreq_policy contains the range of frequency and governor information.
>> But, this description focus on the frequency. You need to explain the more
>> correct description of 'policy'.
>
> I wouldn't say that the focus is on 'frequency', but on 'frequency
> adjustments', and the governor is an integral part of them.
OK. I agree your original description.
>
> I can change it to "Policy for frequency adjustments, including
> frequency limits and the governor" if you prefer. I'm open to other
> suggestions.
(snip)
--
Best Regards,
Chanwoo Choi
Samsung Electronics
next prev parent reply other threads:[~2018-07-12 8:38 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 23:46 [PATCH v5 00/12] Add throttler driver for non-thermal throttling Matthias Kaehlcke
2018-07-03 23:46 ` [PATCH v5 01/12] PM / devfreq: Init user limits from OPP limits, not viceversa Matthias Kaehlcke
2018-07-03 23:46 ` [PATCH v5 02/12] PM / devfreq: Fix handling of min/max_freq == 0 Matthias Kaehlcke
2018-07-04 2:20 ` Chanwoo Choi
2018-07-06 16:36 ` Matthias Kaehlcke
2018-07-12 8:34 ` Chanwoo Choi
2018-07-03 23:46 ` [PATCH v5 03/12] PM / devfreq: Don't adjust to user limits in governors Matthias Kaehlcke
2018-07-04 2:27 ` Chanwoo Choi
2018-08-02 23:36 ` Matthias Kaehlcke
2018-08-03 0:03 ` Chanwoo Choi
2018-08-03 0:24 ` Matthias Kaehlcke
2018-08-03 0:43 ` Chanwoo Choi
2018-07-03 23:46 ` [PATCH v5 04/12] PM / devfreq: Add struct devfreq_policy Matthias Kaehlcke
2018-07-04 2:51 ` Chanwoo Choi
2018-07-06 17:07 ` Matthias Kaehlcke
2018-07-12 8:38 ` Chanwoo Choi [this message]
2018-08-03 0:04 ` Chanwoo Choi
2018-07-03 23:46 ` [PATCH v5 05/12] PM / devfreq: Add support for policy notifiers Matthias Kaehlcke
2018-07-04 6:41 ` Chanwoo Choi
2018-07-06 17:53 ` Matthias Kaehlcke
2018-07-12 8:44 ` Chanwoo Choi
2018-07-16 17:50 ` Matthias Kaehlcke
2018-07-31 19:39 ` Matthias Kaehlcke
2018-08-01 1:22 ` Chanwoo Choi
2018-08-01 17:08 ` Matthias Kaehlcke
2018-08-02 1:58 ` Chanwoo Choi
2018-08-02 23:13 ` Matthias Kaehlcke
2018-08-02 23:48 ` Matthias Kaehlcke
2018-08-03 0:14 ` Chanwoo Choi
2018-08-06 19:21 ` Matthias Kaehlcke
2018-08-06 22:31 ` Chanwoo Choi
2018-08-06 22:50 ` Chanwoo Choi
2018-08-07 0:23 ` Matthias Kaehlcke
2018-08-07 1:35 ` Chanwoo Choi
2018-08-07 22:34 ` Matthias Kaehlcke
2018-08-02 23:56 ` Chanwoo Choi
2018-08-06 18:46 ` Matthias Kaehlcke
2018-08-06 22:16 ` Chanwoo Choi
2018-07-03 23:46 ` [PATCH v5 06/12] PM / devfreq: Make update_devfreq() public Matthias Kaehlcke
2018-08-01 8:32 ` Chanwoo Choi
2018-07-03 23:47 ` [PATCH v5 07/12] PM / devfreq: export devfreq_class Matthias Kaehlcke
2018-07-04 5:30 ` Chanwoo Choi
2018-07-06 18:09 ` Matthias Kaehlcke
2018-07-12 9:08 ` Chanwoo Choi
2018-07-16 19:41 ` Matthias Kaehlcke
2018-07-31 19:29 ` Matthias Kaehlcke
2018-08-01 8:18 ` Chanwoo Choi
2018-08-01 17:18 ` Matthias Kaehlcke
2018-07-03 23:47 ` [PATCH v5 08/12] cpufreq: Add stub for cpufreq_update_policy() Matthias Kaehlcke
2018-07-04 10:41 ` Rafael J. Wysocki
2018-07-10 22:24 ` Matthias Kaehlcke
2018-07-04 10:44 ` Viresh Kumar
2018-07-03 23:47 ` [PATCH v5 09/12] dt-bindings: misc: add bindings for throttler Matthias Kaehlcke
2018-07-04 10:00 ` Viresh Kumar
2018-08-01 8:27 ` Chanwoo Choi
2018-08-01 17:39 ` Matthias Kaehlcke
2018-07-03 23:47 ` [PATCH v5 10/12] misc: throttler: Add core support for non-thermal throttling Matthias Kaehlcke
2018-07-03 23:47 ` [PATCH v5 11/12] misc: throttler: Add Chrome OS EC throttler Matthias Kaehlcke
2018-07-03 23:47 ` [PATCH v5 12/12] mfd: cros_ec: Add throttler sub-device Matthias Kaehlcke
2018-07-04 7:59 ` Lee Jones
[not found] ` <CGME20180703234727epcas3p1b9f4a41b1f1714c8c059100d46b816dd@epcms1p5>
2018-07-04 2:24 ` [PATCH v5 01/12] PM / devfreq: Init user limits from OPP limits, not viceversa MyungJoo Ham
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=4863cf97-37d9-7d81-f44b-10de3dc8267e@samsung.com \
--to=cw00.choi@samsung.com \
--cc=arnd@arndb.de \
--cc=bleung@chromium.org \
--cc=briannorris@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=kyungmin.park@samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mka@chromium.org \
--cc=myungjoo.ham@samsung.com \
--cc=olof@lixom.net \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=viresh.kumar@linaro.org \
/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).