From: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
To: Steven Price <steven.price@arm.com>
Cc: Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
Rob Herring <robh@kernel.org>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/panfrost: devfreq: Round frequencies to OPPs
Date: Tue, 26 Nov 2019 09:28:14 -0500 [thread overview]
Message-ID: <20191126142814.GA6151@kevin> (raw)
In-Reply-To: <20191118173002.32015-1-steven.price@arm.com>
[-- Attachment #1: Type: text/plain, Size: 2751 bytes --]
Reviewed-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
On Mon, Nov 18, 2019 at 05:30:02PM +0000, Steven Price wrote:
> Currently when setting a frequency in panfrost_devfreq_target the
> returned frequency is the actual frequency that the clock driver reports
> (the return of clk_get_rate()). However, where the provided OPPs don't
> precisely match the frequencies that the clock actually achieves devfreq
> will then complain (repeatedly):
>
> devfreq devfreq0: Couldn't update frequency transition information.
>
> To avoid this change panfrost_devfreq_target() to fetch the opp using
> devfreq_recommened_opp() and not actually query the clock for the
> frequency.
>
> A similar problem exists with panfrost_devfreq_get_cur_freq(), but in
> this case because the function is optional we can just remove it and
> devfreq will fall back to using the previously set frequency.
>
> Fixes: 221bc77914cb ("drm/panfrost: Use generic code for devfreq")
> Signed-off-by: Steven Price <steven.price@arm.com>
> ---
> drivers/gpu/drm/panfrost/panfrost_devfreq.c | 19 ++++++-------------
> 1 file changed, 6 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/gpu/drm/panfrost/panfrost_devfreq.c b/drivers/gpu/drm/panfrost/panfrost_devfreq.c
> index 4c4e8a30a1ac..536ba93b0f46 100644
> --- a/drivers/gpu/drm/panfrost/panfrost_devfreq.c
> +++ b/drivers/gpu/drm/panfrost/panfrost_devfreq.c
> @@ -18,15 +18,18 @@ static void panfrost_devfreq_update_utilization(struct panfrost_device *pfdev);
> static int panfrost_devfreq_target(struct device *dev, unsigned long *freq,
> u32 flags)
> {
> - struct panfrost_device *pfdev = dev_get_drvdata(dev);
> + struct dev_pm_opp *opp;
> int err;
>
> + opp = devfreq_recommended_opp(dev, freq, flags);
> + if (IS_ERR(opp))
> + return PTR_ERR(opp);
> + dev_pm_opp_put(opp);
> +
> err = dev_pm_opp_set_rate(dev, *freq);
> if (err)
> return err;
>
> - *freq = clk_get_rate(pfdev->clock);
> -
> return 0;
> }
>
> @@ -60,20 +63,10 @@ static int panfrost_devfreq_get_dev_status(struct device *dev,
> return 0;
> }
>
> -static int panfrost_devfreq_get_cur_freq(struct device *dev, unsigned long *freq)
> -{
> - struct panfrost_device *pfdev = platform_get_drvdata(to_platform_device(dev));
> -
> - *freq = clk_get_rate(pfdev->clock);
> -
> - return 0;
> -}
> -
> static struct devfreq_dev_profile panfrost_devfreq_profile = {
> .polling_ms = 50, /* ~3 frames */
> .target = panfrost_devfreq_target,
> .get_dev_status = panfrost_devfreq_get_dev_status,
> - .get_cur_freq = panfrost_devfreq_get_cur_freq,
> };
>
> int panfrost_devfreq_init(struct panfrost_device *pfdev)
> --
> 2.20.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
To: Steven Price <steven.price@arm.com>
Cc: Tomeu Vizoso <tomeu.vizoso@collabora.com>,
David Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/panfrost: devfreq: Round frequencies to OPPs
Date: Tue, 26 Nov 2019 09:28:14 -0500 [thread overview]
Message-ID: <20191126142814.GA6151@kevin> (raw)
Message-ID: <20191126142814.mGTB1EZwnxvwZbjES-o4NWcuV_t0FHsLOEhWiy92uCo@z> (raw)
In-Reply-To: <20191118173002.32015-1-steven.price@arm.com>
[-- Attachment #1.1: Type: text/plain, Size: 2751 bytes --]
Reviewed-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
On Mon, Nov 18, 2019 at 05:30:02PM +0000, Steven Price wrote:
> Currently when setting a frequency in panfrost_devfreq_target the
> returned frequency is the actual frequency that the clock driver reports
> (the return of clk_get_rate()). However, where the provided OPPs don't
> precisely match the frequencies that the clock actually achieves devfreq
> will then complain (repeatedly):
>
> devfreq devfreq0: Couldn't update frequency transition information.
>
> To avoid this change panfrost_devfreq_target() to fetch the opp using
> devfreq_recommened_opp() and not actually query the clock for the
> frequency.
>
> A similar problem exists with panfrost_devfreq_get_cur_freq(), but in
> this case because the function is optional we can just remove it and
> devfreq will fall back to using the previously set frequency.
>
> Fixes: 221bc77914cb ("drm/panfrost: Use generic code for devfreq")
> Signed-off-by: Steven Price <steven.price@arm.com>
> ---
> drivers/gpu/drm/panfrost/panfrost_devfreq.c | 19 ++++++-------------
> 1 file changed, 6 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/gpu/drm/panfrost/panfrost_devfreq.c b/drivers/gpu/drm/panfrost/panfrost_devfreq.c
> index 4c4e8a30a1ac..536ba93b0f46 100644
> --- a/drivers/gpu/drm/panfrost/panfrost_devfreq.c
> +++ b/drivers/gpu/drm/panfrost/panfrost_devfreq.c
> @@ -18,15 +18,18 @@ static void panfrost_devfreq_update_utilization(struct panfrost_device *pfdev);
> static int panfrost_devfreq_target(struct device *dev, unsigned long *freq,
> u32 flags)
> {
> - struct panfrost_device *pfdev = dev_get_drvdata(dev);
> + struct dev_pm_opp *opp;
> int err;
>
> + opp = devfreq_recommended_opp(dev, freq, flags);
> + if (IS_ERR(opp))
> + return PTR_ERR(opp);
> + dev_pm_opp_put(opp);
> +
> err = dev_pm_opp_set_rate(dev, *freq);
> if (err)
> return err;
>
> - *freq = clk_get_rate(pfdev->clock);
> -
> return 0;
> }
>
> @@ -60,20 +63,10 @@ static int panfrost_devfreq_get_dev_status(struct device *dev,
> return 0;
> }
>
> -static int panfrost_devfreq_get_cur_freq(struct device *dev, unsigned long *freq)
> -{
> - struct panfrost_device *pfdev = platform_get_drvdata(to_platform_device(dev));
> -
> - *freq = clk_get_rate(pfdev->clock);
> -
> - return 0;
> -}
> -
> static struct devfreq_dev_profile panfrost_devfreq_profile = {
> .polling_ms = 50, /* ~3 frames */
> .target = panfrost_devfreq_target,
> .get_dev_status = panfrost_devfreq_get_dev_status,
> - .get_cur_freq = panfrost_devfreq_get_cur_freq,
> };
>
> int panfrost_devfreq_init(struct panfrost_device *pfdev)
> --
> 2.20.1
>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-11-26 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 17:30 [PATCH] drm/panfrost: devfreq: Round frequencies to OPPs Steven Price
2019-11-18 17:30 ` Steven Price
2019-11-26 14:28 ` Alyssa Rosenzweig [this message]
2019-11-26 14:28 ` Alyssa Rosenzweig
2019-12-06 17:16 ` Rob Herring
2019-12-06 17:16 ` Rob Herring
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=20191126142814.GA6151@kevin \
--to=alyssa.rosenzweig@collabora.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=steven.price@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.