From: Steven Price <steven.price@arm.com>
To: "Adrián Larumbe" <adrian.larumbe@collabora.com>,
"Boris Brezillon" <boris.brezillon@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>,
"Daniel Vetter" <daniel@ffwll.ch>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
kernel@collabora.com
Subject: Re: [PATCH 0/2] Panfrost devfreq and GEM status fixes
Date: Thu, 30 Nov 2023 11:29:00 +0000 [thread overview]
Message-ID: <871c4b6d-fb37-41ae-9dcf-b98345e70c77@arm.com> (raw)
In-Reply-To: <20231125205438.375407-1-adrian.larumbe@collabora.com>
On 25/11/2023 20:52, Adrián Larumbe wrote:
> During recent development of the Mali CSF GPU Panthor driver, a user
> noticed that GPU frequency values as reported by fdinfo were
> incorrect. This was traced back to incorrect handling of frequency value
> updates. The same problem was seen in Panfrost.
>
> Also one should consider GEM objects from a dma-buf import as being
> resident in system memory, so that this can be reflected on fdinfo.
>
> Adrián Larumbe (2):
> drm/panfrost: Consider dma-buf imported objects as resident
> drm/panfrost: Fix incorrect updating of current device frequency
>
> drivers/gpu/drm/panfrost/panfrost_devfreq.c | 17 +++++++++++++++--
> drivers/gpu/drm/panfrost/panfrost_gem.c | 2 +-
> 2 files changed, 16 insertions(+), 3 deletions(-)
>
>
> base-commit: 38f922a563aac3148ac73e73689805917f034cb5
Pushed to drm-misc-fixes
Thanks,
Steve
prev parent reply other threads:[~2023-11-30 11:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 20:52 Adrián Larumbe
2023-11-25 20:52 ` [PATCH 1/2] drm/panfrost: Consider dma-buf imported objects as resident Adrián Larumbe
2023-11-27 11:33 ` Steven Price
2023-11-25 20:52 ` [PATCH 2/2] drm/panfrost: Fix incorrect updating of current device frequency Adrián Larumbe
2023-11-27 11:34 ` Steven Price
2023-11-30 11:29 ` 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=871c4b6d-fb37-41ae-9dcf-b98345e70c77@arm.com \
--to=steven.price@arm.com \
--cc=adrian.larumbe@collabora.com \
--cc=airlied@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=boris.brezillon@collabora.com \
--cc=daniel@ffwll.ch \
--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=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
all inboxes | Powered by JetHome®