From: Steven Price <steven.price@arm.com>
To: Chia-I Wu <olvaffe@gmail.com>,
Boris Brezillon <boris.brezillon@collabora.com>,
Liviu Dudau <liviu.dudau@arm.com>,
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>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] drm/panthor: add custom ASN hash support
Date: Fri, 29 Aug 2025 14:40:58 +0100 [thread overview]
Message-ID: <ac4838eb-7613-4642-a007-577a9f665984@arm.com> (raw)
In-Reply-To: <20250828201806.3541261-1-olvaffe@gmail.com>
On 28/08/2025 21:18, Chia-I Wu wrote:
> Some socs such as mt8196 require custom ASN hash.
I don't know the full details of this, but I'm puzzled by the "require"
here.
AIUI the "custom ASN hash support" (or L2C_SLICE_HASH as it was renamed)
affects the efficiency of the L2 caches in the GPU. It basically
determines how addresses are striped over the individual caches.
So (unless there is a specific errata) not setting a custom hash will
work just fine, but the performance might be slightly reduced.
kbase provides both a DT option and a module parameter which can be used
to override the defaults (although the parameter descriptions say "for
testing" which I think is somewhat telling).
How we should describe this somewhat depends on whether this is a
specific workaround for a SoC - in which case Boris's suggestion of
using a different compatible string and panthor_soc_data seems like a
good choice. Or if this is exposed as a general "tuning" parameter, in
which case this might be appropriate.
I believe the tuning is related to more than just a SoC (the external
memory system has an impact). So I guess a DT level knob makes most
sense here.
Steve
> Chia-I Wu (2):
> dt-bindings: gpu: mali-valhall-csf: add asn-hash
> drm/panthor: add asn-hash support
>
> .../bindings/gpu/arm,mali-valhall-csf.yaml | 8 ++++++
> drivers/gpu/drm/panthor/panthor_device.c | 28 +++++++++++++++++++
> drivers/gpu/drm/panthor/panthor_device.h | 6 ++++
> drivers/gpu/drm/panthor/panthor_gpu.c | 17 +++++++++++
> drivers/gpu/drm/panthor/panthor_regs.h | 4 +++
> 5 files changed, 63 insertions(+)
>
next prev parent reply other threads:[~2025-08-29 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 20:18 Chia-I Wu
2025-08-28 20:18 ` [PATCH 1/2] dt-bindings: gpu: mali-valhall-csf: add asn-hash Chia-I Wu
2025-08-29 8:32 ` Boris Brezillon
2025-08-29 13:42 ` Krzysztof Kozlowski
2025-08-28 20:18 ` [PATCH 2/2] drm/panthor: add asn-hash support Chia-I Wu
2025-08-29 13:41 ` Steven Price
2025-08-29 13:40 ` Steven Price [this message]
2025-08-29 21:50 ` [PATCH 0/2] drm/panthor: add custom ASN hash support Chia-I Wu
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=ac4838eb-7613-4642-a007-577a9f665984@arm.com \
--to=steven.price@arm.com \
--cc=airlied@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=olvaffe@gmail.com \
--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
all inboxes | Powered by JetHome®