From: Dirk Behme <dirk.behme@de.bosch.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Simon Horman <horms+renesas@verge.net.au>,
<linux-renesas-soc@vger.kernel.org>,
Koji Matsuoka <koji.matsuoka.xm@renesas.com>
Cc: Dirk Behme <dirk.behme@de.bosch.com>
Subject: [PATCH 2/4] arm64: dts: Renesas: R-Car3: Add product register
Date: Wed, 25 May 2016 10:58:26 +0200 [thread overview]
Message-ID: <1464166708-18320-3-git-send-email-dirk.behme@de.bosch.com> (raw)
In-Reply-To: <1464166708-18320-1-git-send-email-dirk.behme@de.bosch.com>
The product register of the Renesas R-Car3 isn't part of any SoC
module, but "just" a register at address 0xFFF00044.
It provides some configuration information about the SoC itself, like
the number of the CA57, CA53 and CR7 cores, the product description
(R-Car H3, R-Car M3-W etc) and the sample revision.
This information is needed by some drivers to enable or disable
specific features which are present or not in the SoC.
Signed-off-by: Dirk Behme <dirk.behme@de.bosch.com>
---
.../bindings/soc/renesas/renesas,rcar-gen3-prr.txt | 21 +++++++++++++++++++++
arch/arm64/boot/dts/renesas/r8a7795.dtsi | 6 ++++++
arch/arm64/boot/dts/renesas/r8a7796.dtsi | 6 ++++++
3 files changed, 33 insertions(+)
create mode 100644 Documentation/devicetree/bindings/soc/renesas/renesas,rcar-gen3-prr.txt
diff --git a/Documentation/devicetree/bindings/soc/renesas/renesas,rcar-gen3-prr.txt b/Documentation/devicetree/bindings/soc/renesas/renesas,rcar-gen3-prr.txt
new file mode 100644
index 0000000..23101cd
--- /dev/null
+++ b/Documentation/devicetree/bindings/soc/renesas/renesas,rcar-gen3-prr.txt
@@ -0,0 +1,21 @@
+Renesas R-Car3 product register binding
+---------------------------------------
+
+The product register of the Renesas R-Car3 provides some configuration
+information about the SoC itself, like the number of the CA57, CA53 and
+CR7 cores, the product description (R-Car H3, R-Car M3-W etc) and the
+sample revision. This information is needed by some drivers to enable
+or disable specific features which are present or not in the SoC.
+
+Required properties:
+- compatible : "renesas,rcar-gen3-prr"
+ and additionally a SoC specific property like
+ "renesas,r8a7795-prr" or
+ "renesas,r8a7796-prr"
+- reg : Location and size of the product register
+
+Example:
+ prr: product-register@fff00044 {
+ compatible = "renesas,rcar-gen3-prr", "renesas,r8a7795-prr";
+ reg = <0 0xfff00044 0 0x4>;
+ };
diff --git a/arch/arm64/boot/dts/renesas/r8a7795.dtsi b/arch/arm64/boot/dts/renesas/r8a7795.dtsi
index 26df300..0ae4687 100644
--- a/arch/arm64/boot/dts/renesas/r8a7795.dtsi
+++ b/arch/arm64/boot/dts/renesas/r8a7795.dtsi
@@ -1610,5 +1610,11 @@
interrupts = <0 436 IRQ_TYPE_LEVEL_HIGH>;
clocks = <&cpg CPG_MOD 728>;
};
+
+ prr: product-register@fff00044 {
+ compatible = "renesas,rcar-gen3-prr",
+ "renesas,r8a7795-prr";
+ reg = <0 0xfff00044 0 0x4>;
+ };
};
};
diff --git a/arch/arm64/boot/dts/renesas/r8a7796.dtsi b/arch/arm64/boot/dts/renesas/r8a7796.dtsi
index 1389528..100b531 100644
--- a/arch/arm64/boot/dts/renesas/r8a7796.dtsi
+++ b/arch/arm64/boot/dts/renesas/r8a7796.dtsi
@@ -141,5 +141,11 @@
power-domains = <&sysc R8A7796_PD_ALWAYS_ON>;
status = "disabled";
};
+
+ prr: product-register@fff00044 {
+ compatible = "renesas,rcar-gen3-prr",
+ "renesas,r8a7796-prr";
+ reg = <0 0xfff00044 0 0x4>;
+ };
};
};
--
2.8.0
next prev parent reply other threads:[~2016-05-25 8:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 8:58 [PATCH 0/4] ARM: Renesas: R-Car3: Add product register support Dirk Behme
2016-05-25 8:58 ` [PATCH 1/4] " Dirk Behme
2016-05-25 8:58 ` Dirk Behme [this message]
2016-05-25 8:58 ` [PATCH 3/4] ARM: Renesas: R-Car3: Add cpu and revision handlers Dirk Behme
2016-05-25 8:58 ` [PATCH 4/4] drm: rcar-du: Use product register framework Dirk Behme
2016-05-27 3:40 ` Magnus Damm
2016-05-27 8:16 ` Dirk Behme
2016-05-27 9:56 ` Magnus Damm
2016-05-27 10:18 ` Dirk Behme
2016-06-01 2:33 ` Magnus Damm
2016-05-26 7:14 ` [PATCH 0/4] ARM: Renesas: R-Car3: Add product register support Geert Uytterhoeven
2016-05-26 7:48 ` Dirk Behme
2016-05-27 3:13 ` Magnus Damm
2016-05-27 7:56 ` Dirk Behme
2016-05-27 8:39 ` Geert Uytterhoeven
2016-05-27 8:44 ` Dirk Behme
2016-05-27 9:00 ` Geert Uytterhoeven
2016-06-01 5:19 ` Magnus Damm
2016-06-01 7:19 ` Dirk Behme
2016-06-01 7:27 ` Geert Uytterhoeven
2016-06-01 7:38 ` Dirk Behme
2016-06-01 8:26 ` Geert Uytterhoeven
2016-06-01 8:36 ` Dirk Behme
2016-06-01 8:40 ` Geert Uytterhoeven
2016-06-01 8:43 ` Dirk Behme
2016-06-29 7:58 ` Dirk Behme
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=1464166708-18320-3-git-send-email-dirk.behme@de.bosch.com \
--to=dirk.behme@de.bosch.com \
--cc=geert+renesas@glider.be \
--cc=horms+renesas@verge.net.au \
--cc=koji.matsuoka.xm@renesas.com \
--cc=linux-renesas-soc@vger.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