From: Dmitry Osipenko <digetx@gmail.com>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
Peter Geis <pgwipeout@gmail.com>,
linux-pm@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 17/19] PM / devfreq: tegra30: Support variable polling interval
Date: Fri, 1 Nov 2019 16:55:12 +0300 [thread overview]
Message-ID: <a60d5949-a980-306a-e65a-6017b40a7321@gmail.com> (raw)
In-Reply-To: <00ddcbd5-262b-2130-6242-b1ec364825f3@samsung.com>
01.11.2019 10:41, Chanwoo Choi пишет:
> On 19. 10. 30. 오전 7:00, Dmitry Osipenko wrote:
>> The ACTMON governor is interrupt-driven and currently hardware's polling
>> interval is fixed to 16ms in the driver. Devfreq supports variable polling
>> interval by the generic governors, let's re-use the generic interface for
>> changing of the polling interval. Now the polling interval can be changed
>> dynamically via /sys/class/devfreq/devfreq0/polling_interval.
>>
>> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
>> ---
>> drivers/devfreq/tegra30-devfreq.c | 35 ++++++++++++++++++++++++-------
>> 1 file changed, 28 insertions(+), 7 deletions(-)
>>
>> diff --git a/drivers/devfreq/tegra30-devfreq.c b/drivers/devfreq/tegra30-devfreq.c
>> index b745a973c35a..d0dd42856e5b 100644
>> --- a/drivers/devfreq/tegra30-devfreq.c
>> +++ b/drivers/devfreq/tegra30-devfreq.c
>> @@ -218,7 +218,7 @@ static void tegra_devfreq_update_avg_wmark(struct tegra_devfreq *tegra,
>> {
>> u32 avg = dev->avg_count;
>> u32 avg_band_freq = tegra->max_freq * ACTMON_DEFAULT_AVG_BAND / KHZ;
>> - u32 band = avg_band_freq * ACTMON_SAMPLING_PERIOD;
>> + u32 band = avg_band_freq * tegra->devfreq->profile->polling_ms;
>>
>> device_writel(dev, avg + band, ACTMON_DEV_AVG_UPPER_WMARK);
>>
>> @@ -229,7 +229,7 @@ static void tegra_devfreq_update_avg_wmark(struct tegra_devfreq *tegra,
>> static void tegra_devfreq_update_wmark(struct tegra_devfreq *tegra,
>> struct tegra_devfreq_device *dev)
>> {
>> - u32 val = tegra->cur_freq * ACTMON_SAMPLING_PERIOD;
>> + u32 val = tegra->cur_freq * tegra->devfreq->profile->polling_ms;
>>
>> device_writel(dev, do_percent(val, dev->config->boost_up_threshold),
>> ACTMON_DEV_UPPER_WMARK);
>> @@ -308,7 +308,7 @@ static unsigned long actmon_device_target_freq(struct tegra_devfreq *tegra,
>> unsigned int avg_sustain_coef;
>> unsigned long target_freq;
>>
>> - target_freq = dev->avg_count / ACTMON_SAMPLING_PERIOD;
>> + target_freq = dev->avg_count / tegra->devfreq->profile->polling_ms;
>> avg_sustain_coef = 100 * 100 / dev->config->boost_up_threshold;
>> target_freq = do_percent(target_freq, avg_sustain_coef);
>> target_freq += dev->boost_freq;
>> @@ -465,7 +465,7 @@ static void tegra_actmon_configure_device(struct tegra_devfreq *tegra,
>>
>> dev->target_freq = tegra->cur_freq;
>>
>> - dev->avg_count = tegra->cur_freq * ACTMON_SAMPLING_PERIOD;
>> + dev->avg_count = tegra->cur_freq * tegra->devfreq->profile->polling_ms;
>> device_writel(dev, dev->avg_count, ACTMON_DEV_INIT_AVG);
>>
>> tegra_devfreq_update_avg_wmark(tegra, dev);
>> @@ -506,7 +506,11 @@ static int tegra_actmon_start(struct tegra_devfreq *tegra)
>> unsigned int i;
>> int err;
>>
>> - actmon_writel(tegra, ACTMON_SAMPLING_PERIOD - 1,
>> + if (!tegra->devfreq->profile->polling_ms ||
>> + tegra->devfreq->stop_polling)
>
> I think that the access of 'devfreq->stop_polling' is not good
> on governor. It is possible to alter with DEVFREQ_GOV_START/STOP/SUSPEND/RESUME
> notification.
Could you please clarify what you're meaning by "alter with notification"?
Do you mean to have the start/stop state tracking done by the
tegra30-devfreq driver itself?
>> + return 0;> +
>> + actmon_writel(tegra, tegra->devfreq->profile->polling_ms - 1,
>> ACTMON_GLB_PERIOD_CTRL);
>>
>> /*
>> @@ -554,6 +558,10 @@ static int tegra_actmon_start(struct tegra_devfreq *tegra)
>>
>> static void tegra_actmon_stop(struct tegra_devfreq *tegra)
>> {
>> + if (!tegra->devfreq->profile->polling_ms ||
>> + tegra->devfreq->stop_polling)
>
> ditto.
>
>> + return;
>> +
>> disable_irq(tegra->irq);
>>
>> cpufreq_unregister_notifier(&tegra->cpu_rate_change_nb,
>> @@ -623,7 +631,7 @@ static int tegra_devfreq_get_dev_status(struct device *dev,
>> stat->busy_time *= 100 / BUS_SATURATION_RATIO;
>>
>> /* Number of cycles in a sampling period */
>> - stat->total_time = ACTMON_SAMPLING_PERIOD * cur_freq;
>> + stat->total_time = tegra->devfreq->profile->polling_ms * cur_freq;
>>
>> stat->busy_time = min(stat->busy_time, stat->total_time);
>>
>> @@ -631,7 +639,7 @@ static int tegra_devfreq_get_dev_status(struct device *dev,
>> }
>>
>> static struct devfreq_dev_profile tegra_devfreq_profile = {
>> - .polling_ms = 0,
>> + .polling_ms = ACTMON_SAMPLING_PERIOD,
>> .target = tegra_devfreq_target,
>> .get_dev_status = tegra_devfreq_get_dev_status,
>> };
>> @@ -671,6 +679,7 @@ static int tegra_governor_event_handler(struct devfreq *devfreq,
>> unsigned int event, void *data)
>> {
>> struct tegra_devfreq *tegra = dev_get_drvdata(devfreq->dev.parent);
>> + unsigned int *new_delay = data;
>> int ret = 0;
>>
>> /*
>> @@ -690,6 +699,17 @@ static int tegra_governor_event_handler(struct devfreq *devfreq,
>> devfreq_monitor_stop(devfreq);
>> break;
>>
>> + case DEVFREQ_GOV_INTERVAL:
>> + if (*new_delay > 256) {
>
> Need to add the comment why the maximum delay is under 256 ms.
Okay, will add comment in v8. The 256ms max is the hardware's capability.
next prev parent reply other threads:[~2019-11-01 13:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 22:00 [PATCH v7 00/19] More improvements for Tegra30 devfreq driver Dmitry Osipenko
2019-10-29 22:00 ` [PATCH v7 01/19] PM / devfreq: tegra30: Change irq type to unsigned int Dmitry Osipenko
2019-10-29 22:00 ` [PATCH v7 02/19] PM / devfreq: tegra30: Keep interrupt disabled while governor is stopped Dmitry Osipenko
2019-10-29 22:00 ` [PATCH v7 03/19] PM / devfreq: tegra30: Handle possible round-rate error Dmitry Osipenko
2019-10-29 22:00 ` [PATCH v7 04/19] PM / devfreq: tegra30: Drop write-barrier Dmitry Osipenko
2019-10-29 22:00 ` [PATCH v7 05/19] PM / devfreq: tegra30: Fix integer overflow on CPU's freq max out Dmitry Osipenko
2019-10-29 22:00 ` [PATCH v7 06/19] PM / devfreq: tegra30: Use kHz units uniformly in the code Dmitry Osipenko
2019-10-31 4:44 ` Chanwoo Choi
2019-10-31 23:08 ` Dmitry Osipenko
2019-10-29 22:00 ` [PATCH v7 07/19] PM / devfreq: tegra30: Use CPUFreq notifier Dmitry Osipenko
2019-10-29 22:00 ` [PATCH v7 08/19] PM / devfreq: tegra30: Move clk-notifier's registration to governor's start Dmitry Osipenko
2019-10-29 22:00 ` [PATCH v7 09/19] PM / devfreq: tegra30: Reset boosting on startup Dmitry Osipenko
2019-10-29 22:00 ` [PATCH v7 10/19] PM / devfreq: tegra30: Don't enable consecutive-down interrupt " Dmitry Osipenko
2019-10-29 22:00 ` [PATCH v7 11/19] PM / devfreq: tegra30: Constify structs Dmitry Osipenko
2019-10-29 22:00 ` [PATCH v7 12/19] PM / devfreq: tegra30: Include appropriate header Dmitry Osipenko
2019-10-29 22:00 ` [PATCH v7 13/19] PM / devfreq: tegra30: Increase sampling period to 16ms Dmitry Osipenko
2019-11-01 21:53 ` Michał Mirosław
2019-10-29 22:00 ` [PATCH v7 14/19] PM / devfreq: tegra30: Don't enable already enabled consecutive interrupts Dmitry Osipenko
2019-11-01 7:00 ` Chanwoo Choi
2019-10-29 22:00 ` [PATCH v7 15/19] PM / devfreq: tegra30: Disable consecutive interrupts when appropriate Dmitry Osipenko
2019-11-01 7:01 ` Chanwoo Choi
2019-10-29 22:00 ` [PATCH v7 16/19] PM / devfreq: Add new interrupt_driven flag for governors Dmitry Osipenko
2019-11-01 7:32 ` Chanwoo Choi
2019-11-01 13:56 ` Dmitry Osipenko
2019-10-29 22:00 ` [PATCH v7 17/19] PM / devfreq: tegra30: Support variable polling interval Dmitry Osipenko
2019-11-01 7:41 ` Chanwoo Choi
2019-11-01 13:55 ` Dmitry Osipenko [this message]
2019-11-01 21:58 ` Michał Mirosław
2019-11-01 22:23 ` Dmitry Osipenko
2019-11-03 15:25 ` Dmitry Osipenko
2019-10-29 22:00 ` [PATCH v7 18/19] PM / devfreq: tegra30: Tune up MCCPU boost-down coefficient Dmitry Osipenko
2019-11-01 7:45 ` Chanwoo Choi
2019-11-01 14:14 ` Dmitry Osipenko
2019-10-29 22:00 ` [PATCH v7 19/19] PM / devfreq: tegra20/30: Add Dmitry as a maintainer Dmitry Osipenko
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=a60d5949-a980-306a-e65a-6017b40a7321@gmail.com \
--to=digetx@gmail.com \
--cc=cw00.choi@samsung.com \
--cc=jonathanh@nvidia.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=pgwipeout@gmail.com \
--cc=thierry.reding@gmail.com \
--cc=tomeu.vizoso@collabora.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
Powered by JetHome