linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leonard Crestez <leonard.crestez@nxp.com>
To: Chanwoo Choi <cw00.choi@samsung.com>,
	Matthias Kaehlcke <mka@chromium.org>
Cc: "MyungJoo Ham" <myungjoo.ham@samsung.com>,
	"Kyungmin Park" <kyungmin.park@samsung.com>,
	"Artur Świgoń" <a.swigon@partner.samsung.com>,
	"Saravana Kannan" <saravanak@google.com>,
	"Krzysztof Kozlowski" <krzk@kernel.org>,
	"Alexandre Bailon" <abailon@baylibre.com>,
	"Georgi Djakov" <georgi.djakov@linaro.org>,
	"Abel Vesa" <abel.vesa@nxp.com>, "Jacky Bai" <ping.bai@nxp.com>,
	"Viresh Kumar" <viresh.kumar@linaro.org>,
	"Lukasz Luba" <l.luba@partner.samsung.com>,
	dl-linux-imx <linux-imx@nxp.com>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v8 5/6] PM / devfreq: Add PM QoS support
Date: Wed, 25 Sep 2019 19:40:25 +0000	[thread overview]
Message-ID: <VI1PR04MB7023910B94E4920D329427C8EE870@VI1PR04MB7023.eurprd04.prod.outlook.com> (raw)
In-Reply-To: 080027a2-d807-5fa4-f148-4469678ce849@samsung.com

On 25.09.2019 05:13, Chanwoo Choi wrote:
> On 19. 9. 25. 오전 4:22, Leonard Crestez wrote:
>> On 24.09.2019 22:11, Matthias Kaehlcke wrote:
>>> On Tue, Sep 24, 2019 at 01:11:29PM +0300, Leonard Crestez wrote:
>>>> Register notifiers with the PM QoS framework in order to respond to
>>>> requests for DEV_PM_QOS_MIN_FREQUENCY and DEV_PM_QOS_MAX_FREQUENCY.
>>>>
>>>> No notifiers are added by this patch but PM QoS constraints can be
>>>> imposed externally (for example from other devices).
>>>>
>>>> Signed-off-by: Leonard Crestez <leonard.crestez@nxp.com>
>>>> Reviewed-by: Matthias Kaehlcke <mka@chromium.org>
>>>> ---
>>>>    drivers/devfreq/devfreq.c | 75 +++++++++++++++++++++++++++++++++++++++
>>>>    include/linux/devfreq.h   |  5 +++
>>>>    2 files changed, 80 insertions(+)
>>>>
>>>> diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c
>>>> index eee403e70c84..784f3e40536a 100644
>>>> --- a/drivers/devfreq/devfreq.c
>>>> +++ b/drivers/devfreq/devfreq.c
>>>> @@ -22,15 +22,18 @@
>>>>    #include <linux/platform_device.h>
>>>>    #include <linux/list.h>
>>>>    #include <linux/printk.h>
>>>>    #include <linux/hrtimer.h>
>>>>    #include <linux/of.h>
>>>> +#include <linux/pm_qos.h>
>>>>    #include "governor.h"
>>>>    
>>>>    #define CREATE_TRACE_POINTS
>>>>    #include <trace/events/devfreq.h>
>>>>    
>>>> +#define HZ_PER_KHZ	1000
>>>> +
>>>>    static struct class *devfreq_class;
>>>>    
>>>>    /*
>>>>     * devfreq core provides delayed work based load monitoring helper
>>>>     * functions. Governors can use these or can implement their own
>>>> @@ -109,10 +112,11 @@ static unsigned long find_available_max_freq(struct devfreq *devfreq)
>>>>    static void get_freq_range(struct devfreq *devfreq,
>>>>    			   unsigned long *min_freq,
>>>>    			   unsigned long *max_freq)
>>>>    {
>>>>    	unsigned long *freq_table = devfreq->profile->freq_table;
>>>> +	unsigned long qos_min_freq, qos_max_freq;
>>>>    
>>>>    	lockdep_assert_held(&devfreq->lock);
>>>>    
>>>>    	/*
>>>>    	 * Init min/max frequency from freq table.
>>>> @@ -125,10 +129,18 @@ static void get_freq_range(struct devfreq *devfreq,
>>>>    	} else {
>>>>    		*min_freq = freq_table[devfreq->profile->max_state - 1];
>>>>    		*max_freq = freq_table[0];
>>>>    	}
>>>>    
>>>> +	/* constraints from PM QoS */
>>>> +	qos_min_freq = dev_pm_qos_read_value(devfreq->dev.parent,
>>>> +					     DEV_PM_QOS_MIN_FREQUENCY);
>>>> +	qos_max_freq = dev_pm_qos_read_value(devfreq->dev.parent,
>>>> +					     DEV_PM_QOS_MIN_FREQUENCY); >
>>> This needs to be DEV_PM_QOS_MAX_FREQUENCY. I missed this in the earlier
>>> reviews, but stumbled across it when testing.
>>>
>>> !Reviewed-by: Matthias Kaehlcke <mka@chromium.org>
>>
>> I broke it in v8 while processing comments. Thanks for catching it.
> 
> Did you test this patchset with v8?
> Maybe it is not working with this mistake.

I ran some scripts which test that min_freq requests work as expected 
(using imx interconnect+devfreq). They don't touch max_freq.

--
Regards,
Leonard

  reply	other threads:[~2019-09-25 19:40 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20190924101140epcas1p4abeedf42f223e65f58c88a0ddf1e4e56@epcas1p4.samsung.com>
2019-09-24 10:11 ` [PATCH v8 0/6] PM / devfreq: Add dev_pm_qos support Leonard Crestez
2019-09-24 10:11   ` [PATCH v8 1/6] PM / devfreq: Don't fail devfreq_dev_release if not in list Leonard Crestez
2019-09-24 10:11   ` [PATCH v8 2/6] PM / devfreq: Move more initialization before registration Leonard Crestez
2019-09-25  1:46     ` Chanwoo Choi
2019-09-24 10:11   ` [PATCH v8 3/6] PM / devfreq: Don't take lock in devfreq_add_device Leonard Crestez
2019-09-24 10:11   ` [PATCH v8 4/6] PM / devfreq: Introduce get_freq_range helper Leonard Crestez
2019-09-25  1:37     ` Chanwoo Choi
2019-09-25 20:55       ` Leonard Crestez
2019-09-26  1:06         ` Chanwoo Choi
2019-09-26 14:03           ` Leonard Crestez
2019-09-24 10:11   ` [PATCH v8 5/6] PM / devfreq: Add PM QoS support Leonard Crestez
2019-09-24 19:11     ` Matthias Kaehlcke
2019-09-24 19:22       ` Leonard Crestez
2019-09-25  2:17         ` Chanwoo Choi
2019-09-25 19:40           ` Leonard Crestez [this message]
2019-09-26  1:08             ` Chanwoo Choi
2019-09-25  2:15     ` Chanwoo Choi
2019-09-25 16:06       ` Matthias Kaehlcke
2019-09-25 21:18       ` Leonard Crestez
2019-09-26  1:12         ` Chanwoo Choi
2019-09-26 13:43           ` Leonard Crestez
2019-09-27  1:49             ` Chanwoo Choi
2019-09-30 13:16               ` Leonard Crestez
2019-09-30 21:42                 ` Chanwoo Choi
2019-10-01  9:39                   ` Leonard Crestez
2019-10-01 21:55                     ` Chanwoo Choi
2019-09-26  1:19         ` Chanwoo Choi
2019-09-30 12:43           ` Leonard Crestez
2019-09-30 21:21             ` Chanwoo Choi
2019-09-24 10:11   ` [PATCH v8 6/6] PM / devfreq: Use PM QoS for sysfs min/max_freq Leonard Crestez
2019-09-25  2:41     ` Chanwoo Choi
2019-09-25 16:45       ` Matthias Kaehlcke
2019-09-26  1:25         ` Chanwoo Choi
2019-09-26 16:04           ` Matthias Kaehlcke
2019-09-27  1:58             ` Chanwoo Choi
2019-09-25 22:11       ` Leonard Crestez
2019-09-26  1:26         ` Chanwoo Choi
2019-09-25  1:44   ` [PATCH v8 0/6] PM / devfreq: Add dev_pm_qos support Chanwoo Choi
2019-09-25 19:37     ` Leonard Crestez
     [not found]   ` <CGME20190924101139epcas1p4c6799a5de9bdb4e90abb74de1e881388@epcms1p4>
2019-09-25  1:58     ` [PATCH v8 2/6] PM / devfreq: Move more initialization before registration MyungJoo Ham
2019-09-25 19:33       ` Leonard Crestez

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=VI1PR04MB7023910B94E4920D329427C8EE870@VI1PR04MB7023.eurprd04.prod.outlook.com \
    --to=leonard.crestez@nxp.com \
    --cc=a.swigon@partner.samsung.com \
    --cc=abailon@baylibre.com \
    --cc=abel.vesa@nxp.com \
    --cc=cw00.choi@samsung.com \
    --cc=georgi.djakov@linaro.org \
    --cc=krzk@kernel.org \
    --cc=kyungmin.park@samsung.com \
    --cc=l.luba@partner.samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=mka@chromium.org \
    --cc=myungjoo.ham@samsung.com \
    --cc=ping.bai@nxp.com \
    --cc=saravanak@google.com \
    --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).