From: "Arnd Bergmann" <arnd@arndb.de>
To: "Agustin Santiago Isasmendi" <isasmendi.agus@gmail.com>,
"Russell King" <linux@armlinux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
"Stefan Dösinger" <stefandoesinger@gmail.com>,
"Navid Ghahremani" <ghahramani.navid@gmail.com>,
"Krzysztof Kozlowski" <krzk@kernel.org>
Subject: Re: [PATCH 2/2] ARM: l2c: honour status = "disabled" on the L2 cache node
Date: Wed, 11 Nov 2026 14:56:34 +0100 [thread overview]
Message-ID: <49846243-34ae-4643-9b39-1537947fbd96@app.fastmail.com> (raw)
In-Reply-To: <20261111133930.3665251-3-isasmendi.agus@gmail.com>
On Wed, Nov 11, 2026, at 14:39, Agustin Santiago Isasmendi wrote:
> l2x0_of_init() looks the L2 cache node up by compatible and enables the
> cache whatever its status property says, so a device tree cannot keep
> the L2 cache off.
>
> On the ZTE ZX279128S (dual Cortex-A9, L2C-310 r3p3) a PCIe read on one
> CPU deadlocks against an L2C-310 line operation by physical address or a
> Cache Sync on the other CPU, and the board hangs within seconds of WiFi
> traffic. Running with the L2 cache off avoids the deadlock, so a board
> needs a way to say so.
>
> Honour the status property, as the newer cache controller drivers
> already do (drivers/cache/ax45mp_cache.c, starfive_starlink_cache.c).
> If the firmware left the cache enabled, it cannot simply be ignored,
> since nothing would maintain it: clean, invalidate and disable it
> instead. No in-tree L2 cache node is disabled, so nothing changes for
> existing device trees.
>
> Tested on the ZTE ZXHN H3600: with the node disabled the cache stays
> off and the system runs normally; with it enabled the cache comes up as
> before. The firmware-enabled path was exercised with a test-only
> change that enables the cache before the check.
>
> Assisted-by: LLM
> Signed-off-by: Agustin Santiago Isasmendi <isasmendi.agus@gmail.com>
Hi Augustin,
It is a little strange to use the MMIO registers of a status="disabled"
device to turn it off, and it would be nice if we could require
the firmware to leave it in a consistent state instead, but I assume
you can't do that for the one device you are interested in because
you don't have the firmware sources, right?
In this case
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
but maybe add a code comment that explains this to the reader.
prev parent reply other threads:[~2026-11-11 13:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 13:39 [PATCH 0/2] " Agustin Santiago Isasmendi
2026-11-11 13:39 ` [PATCH 1/2] ARM: l2c: factor out the number of ways Agustin Santiago Isasmendi
2026-11-11 14:24 ` Arnd Bergmann
2026-11-11 13:39 ` [PATCH 2/2] ARM: l2c: honour status = "disabled" on the L2 cache node Agustin Santiago Isasmendi
2026-11-11 13:56 ` Arnd Bergmann [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=49846243-34ae-4643-9b39-1537947fbd96@app.fastmail.com \
--to=arnd@arndb.de \
--cc=ghahramani.navid@gmail.com \
--cc=isasmendi.agus@gmail.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=stefandoesinger@gmail.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 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®