Devicetree
 help / color / mirror / Atom feed
From: Navid Ghahremani <ghahramani.navid@gmail.com>
To: Agustin Santiago Isasmendi <isasmendi.agus@gmail.com>
Cc: linux@armlinux.org.uk, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, arnd@arndb.de,
	stefandoesinger@gmail.com, krzk@kernel.org, robh@kernel.org,
	conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 0/2] ARM: l2c: honour status = "disabled" on the L2 cache node
Date: Fri, 13 Nov 2026 00:36:41 +0000	[thread overview]
Message-ID: <20261113003641.3664652-1-ghahramani.navid@gmail.com> (raw)
In-Reply-To: <20261112072953.989664-1-isasmendi.agus@gmail.com>

Hi Agustin,

I tested v2 as posted on my ZTE ZXHN H3600 with 512 MiB and an L2C-310
r3p3, running 6.18.60 with the OpenWrt patches for this board and
booted with kexec.

With the cache node enabled the cache comes up as before. With the node
disabled the kernel reports that the L2C is disabled by the device tree
and leaves the cache off, and the board ran 10 minutes of Wi-Fi
receive, Ethernet send and PCIe config reads on both CPUs together
without a hang. Like in my earlier test, the previous kernel had already
turned the cache off before the kexec, so this does not show what the
boot loader leaves, but you checked that part on your unit.

Tested-by: Navid Ghahremani <ghahramani.navid@gmail.com>

Best regards,
Navid

      parent reply	other threads:[~2026-11-13  0:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12  7:29 [PATCH v2 0/2] ARM: l2c: honour status = "disabled" on the L2 cache node Agustin Santiago Isasmendi
2026-11-12  7:29 ` [PATCH v2 1/2] dt-bindings: cache: l2c2x0: a disabled node is left to the firmware Agustin Santiago Isasmendi
2026-11-13 15:00   ` Rob Herring
2026-11-12  7:29 ` [PATCH v2 2/2] ARM: l2c: honour status = "disabled" on the L2 cache node Agustin Santiago Isasmendi
2026-11-12  7:37   ` sashiko-bot
2026-11-13  0:36 ` Navid Ghahremani [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=20261113003641.3664652-1-ghahramani.navid@gmail.com \
    --to=ghahramani.navid@gmail.com \
    --cc=arnd@arndb.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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=robh@kernel.org \
    --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