From: Steven Price <steven.price@arm.com>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
boris.brezillon@collabora.com
Cc: robh@kernel.org, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de, airlied@gmail.com,
daniel@ffwll.ch, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, wenst@chromium.org,
kernel@collabora.com
Subject: Re: [PATCH] drm/panfrost: Really power off GPU cores in panfrost_gpu_power_off()
Date: Wed, 8 Nov 2023 13:20:00 +0000 [thread overview]
Message-ID: <7928524a-b581-483b-b1a1-6ffd719ce650@arm.com> (raw)
In-Reply-To: <20231102141507.73481-1-angelogioacchino.delregno@collabora.com>
On 02/11/2023 14:15, AngeloGioacchino Del Regno wrote:
> The layout of the registers {TILER,SHADER,L2}_PWROFF_LO, used to request
> powering off cores, is the same as the {TILER,SHADER,L2}_PWRON_LO ones:
> this means that in order to request poweroff of cores, we are supposed
> to write a bitmask of cores that should be powered off!
> This means that the panfrost_gpu_power_off() function has always been
> doing nothing.
>
> Fix powering off the GPU by writing a bitmask of the cores to poweroff
> to the relevant PWROFF_LO registers and then check that the transition
> (from ON to OFF) has finished by polling the relevant PWRTRANS_LO
> registers.
>
> While at it, in order to avoid code duplication, move the core mask
> logic from panfrost_gpu_power_on() to a new panfrost_get_core_mask()
> function, used in both poweron and poweroff.
>
> Fixes: f3ba91228e8e ("drm/panfrost: Add initial panfrost driver")
> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Reviewed-by: Steven Price <steven.price@arm.com>
Thanks,
Steve
next prev parent reply other threads:[~2023-11-08 13:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 14:15 AngeloGioacchino Del Regno
2023-11-08 13:20 ` Steven Price [this message]
2023-11-21 15:34 ` Krzysztof Kozlowski
2023-11-21 16:11 ` AngeloGioacchino Del Regno
2023-11-21 16:35 ` Krzysztof Kozlowski
2023-11-21 16:55 ` Boris Brezillon
2023-11-21 17:08 ` Krzysztof Kozlowski
2023-11-22 9:02 ` Boris Brezillon
2023-11-22 9:06 ` AngeloGioacchino Del Regno
2023-11-22 9:29 ` Krzysztof Kozlowski
2023-11-24 12:45 ` Marek Szyprowski
2023-11-27 11:24 ` Marek Szyprowski
2023-11-27 11:26 ` AngeloGioacchino Del Regno
2023-12-04 7:53 ` Krzysztof Kozlowski
2023-11-22 9:48 ` Steven Price
2023-11-22 10:33 ` AngeloGioacchino Del Regno
2023-11-22 9:54 ` Boris Brezillon
2023-11-22 10:23 ` AngeloGioacchino Del Regno
2023-11-22 10:42 ` Boris Brezillon
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=7928524a-b581-483b-b1a1-6ffd719ce650@arm.com \
--to=steven.price@arm.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 \
--cc=wenst@chromium.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
all inboxes | Powered by JetHome®