From: Conor Dooley <conor@kernel.org>
To: linux-renesas-soc@vger.kernel.org
Cc: conor@kernel.org, Conor Dooley <conor.dooley@microchip.com>,
Ben Zong-You Xie <ben717@andestech.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: [PATCH v1 1/2] dt-bindings: cache: add specific RZ/Five compatible to ax45mp
Date: Fri, 9 May 2025 16:37:57 +0100 [thread overview]
Message-ID: <20250509-dwindle-remold-98b3d03d0631@spud> (raw)
In-Reply-To: <20250509-sapling-exhale-72815a023ac1@spud>
From: Conor Dooley <conor.dooley@microchip.com>
When the binding was originally written, it was assumed that all
ax45mp-caches had the same properties etc. This has turned out to be
incorrect, as the QiLai SoC has a different number of cache-sets.
Add a specific compatible for the RZ/Five for property enforcement and
in case there turns out to be additional differences between these
implementations of the cache controller.
Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
---
.../devicetree/bindings/cache/andestech,ax45mp-cache.yaml | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/cache/andestech,ax45mp-cache.yaml b/Documentation/devicetree/bindings/cache/andestech,ax45mp-cache.yaml
index d2cbe49f4e15f..f533bd178a9f6 100644
--- a/Documentation/devicetree/bindings/cache/andestech,ax45mp-cache.yaml
+++ b/Documentation/devicetree/bindings/cache/andestech,ax45mp-cache.yaml
@@ -28,6 +28,7 @@ select:
properties:
compatible:
items:
+ - const: renesas,r9a07g043f-cache
- const: andestech,ax45mp-cache
- const: cache
@@ -70,7 +71,7 @@ examples:
#include <dt-bindings/interrupt-controller/irq.h>
cache-controller@13400000 {
- compatible = "andestech,ax45mp-cache", "cache";
+ compatible = "renesas,r9a07g043f-cache", "andestech,ax45mp-cache", "cache";
reg = <0x13400000 0x100000>;
interrupts = <508 IRQ_TYPE_LEVEL_HIGH>;
cache-line-size = <64>;
--
2.45.2
next prev parent reply other threads:[~2025-05-09 15:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 15:37 [PATCH v1 0/2] Add specific RZ/Five cache compatible Conor Dooley
2025-05-09 15:37 ` Conor Dooley [this message]
2025-05-12 3:43 ` [PATCH v1 1/2] dt-bindings: cache: add specific RZ/Five compatible to ax45mp Ben Zong-You Xie
2025-05-12 9:01 ` Geert Uytterhoeven
2025-05-12 9:59 ` Conor Dooley
2025-05-12 10:05 ` Lad, Prabhakar
2025-05-12 11:05 ` Geert Uytterhoeven
2025-05-12 11:53 ` Conor Dooley
2025-05-12 12:01 ` Lad, Prabhakar
2025-05-09 15:37 ` [PATCH v1 2/2] riscv: dts: renesas: add specific RZ/Five cache compatible Conor Dooley
2025-05-12 3:44 ` Ben Zong-You Xie
2025-05-12 8:00 ` [PATCH v1 0/2] Add " Geert Uytterhoeven
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=20250509-dwindle-remold-98b3d03d0631@spud \
--to=conor@kernel.org \
--cc=ben717@andestech.com \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=magnus.damm@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@kernel.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