From: Steven Price <steven.price@arm.com>
To: "Adrián Larumbe" <adrian.larumbe@collabora.com>,
linux-kernel@vger.kernel.org
Cc: dri-devel@lists.freedesktop.org,
Boris Brezillon <boris.brezillon@collabora.com>,
kernel@collabora.com, Rob Herring <robh@kernel.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Subject: Re: [PATCH v3 5/5] drm/panfrost: Fix panfrost device variable name in devfreq
Date: Wed, 21 May 2025 16:52:45 +0100 [thread overview]
Message-ID: <e1d1df54-ae5e-4620-a33b-cfcd9ca5f809@arm.com> (raw)
In-Reply-To: <20250520174634.353267-6-adrian.larumbe@collabora.com>
On 20/05/2025 18:44, Adrián Larumbe wrote:
> Commit 64111a0e22a9 ("drm/panfrost: Fix incorrect updating of current
> device frequency") was a Panfrost port of a similar fix in Panthor.
>
> Fix the Panfrost device pointer variable name so that it follows
> Panfrost naming conventions.
>
> Signed-off-by: Adrián Larumbe <adrian.larumbe@collabora.com>
> Fixes: 64111a0e22a9 ("drm/panfrost: Fix incorrect updating of current device frequency")
Reviewed-by: Steven Price <steven.price@arm.com>
> ---
> drivers/gpu/drm/panfrost/panfrost_devfreq.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/panfrost/panfrost_devfreq.c b/drivers/gpu/drm/panfrost/panfrost_devfreq.c
> index 3385fd3ef41a..5d0dce10336b 100644
> --- a/drivers/gpu/drm/panfrost/panfrost_devfreq.c
> +++ b/drivers/gpu/drm/panfrost/panfrost_devfreq.c
> @@ -29,7 +29,7 @@ static void panfrost_devfreq_update_utilization(struct panfrost_devfreq *pfdevfr
> static int panfrost_devfreq_target(struct device *dev, unsigned long *freq,
> u32 flags)
> {
> - struct panfrost_device *ptdev = dev_get_drvdata(dev);
> + struct panfrost_device *pfdev = dev_get_drvdata(dev);
> struct dev_pm_opp *opp;
> int err;
>
> @@ -40,7 +40,7 @@ static int panfrost_devfreq_target(struct device *dev, unsigned long *freq,
>
> err = dev_pm_opp_set_rate(dev, *freq);
> if (!err)
> - ptdev->pfdevfreq.current_frequency = *freq;
> + pfdev->pfdevfreq.current_frequency = *freq;
>
> return err;
> }
prev parent reply other threads:[~2025-05-21 15:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 17:43 [PATCH v3 0/5] Panfrost BO tagging and GEMS debug display Adrián Larumbe
2025-05-20 17:43 ` [PATCH v3 1/5] drm/panfrost: Add BO labelling to Panfrost Adrián Larumbe
2025-05-21 6:09 ` Boris Brezillon
2025-06-02 12:55 ` Steven Price
2025-05-20 17:43 ` [PATCH v3 2/5] drm/panfrost: Internally label some BOs Adrián Larumbe
2025-05-21 6:09 ` Boris Brezillon
2025-05-21 15:52 ` Steven Price
2025-05-20 17:44 ` [PATCH v3 3/5] drm/panfrost: Add driver IOCTL for setting BO labels Adrián Larumbe
2025-05-20 17:44 ` [PATCH v3 4/5] drm/panfrost: show device-wide list of DRM GEM objects over DebugFS Adrián Larumbe
2025-05-21 6:10 ` Boris Brezillon
2025-05-21 15:52 ` Steven Price
2025-05-20 17:44 ` [PATCH v3 5/5] drm/panfrost: Fix panfrost device variable name in devfreq Adrián Larumbe
2025-05-21 6:12 ` Boris Brezillon
2025-05-21 15:52 ` Steven Price [this message]
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=e1d1df54-ae5e-4620-a33b-cfcd9ca5f809@arm.com \
--to=steven.price@arm.com \
--cc=adrian.larumbe@collabora.com \
--cc=airlied@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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