From: Benoit Parrot <bparrot@ti.com>
To: Tony Lindgren <tony@atomide.com>, Tero Kristo <t-kristo@ti.com>
Cc: Rob Herring <robh+dt@kernel.org>, <linux-omap@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Benoit Parrot <bparrot@ti.com>
Subject: [Patch 6/9] arm: dtsi: dra76x: Add CAL dtsi node
Date: Fri, 18 Oct 2019 10:48:46 -0500 [thread overview]
Message-ID: <20191018154849.3127-7-bparrot@ti.com> (raw)
In-Reply-To: <20191018154849.3127-1-bparrot@ti.com>
Add the required dtsi node to support the Camera
Adaptation Layer (CAL) for the DRA76 family of devices.
Signed-off-by: Benoit Parrot <bparrot@ti.com>
---
arch/arm/boot/dts/dra76x.dtsi | 43 +++++++++++++++++++++++++++++++++++
1 file changed, 43 insertions(+)
diff --git a/arch/arm/boot/dts/dra76x.dtsi b/arch/arm/boot/dts/dra76x.dtsi
index cdcba3f561c4..b6f7591bc590 100644
--- a/arch/arm/boot/dts/dra76x.dtsi
+++ b/arch/arm/boot/dts/dra76x.dtsi
@@ -41,6 +41,49 @@
};
+&l4_per3 {
+ target-module@1b0000 { /* 0x489b0000, ap 25 34.0 */
+ compatible = "ti,sysc-omap4", "ti,sysc";
+ reg = <0x1b0000 0x4>,
+ <0x1b0010 0x4>;
+ reg-names = "rev", "sysc";
+ ti,sysc-midle = <SYSC_IDLE_FORCE>,
+ <SYSC_IDLE_NO>;
+ ti,sysc-sidle = <SYSC_IDLE_FORCE>,
+ <SYSC_IDLE_NO>;
+ clocks = <&cam_clkctrl DRA7_CAM_VIP3_CLKCTRL 0>;
+ clock-names = "fck";
+ #address-cells = <1>;
+ #size-cells = <1>;
+ ranges = <0x0 0x1b0000 0x10000>;
+
+ cal: cal@0 {
+ compatible = "ti,dra76-cal";
+ reg = <0x0000 0x400>,
+ <0x0800 0x40>,
+ <0x0900 0x40>;
+ reg-names = "cal_top",
+ "cal_rx_core0",
+ "cal_rx_core1";
+ interrupts = <GIC_SPI 353 IRQ_TYPE_LEVEL_HIGH>;
+ syscon-camerrx = <&scm_conf 0x6dc>;
+ status = "disabled";
+
+ ports {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ csi2_0: port@0 {
+ reg = <0>;
+ };
+ csi2_1: port@1 {
+ reg = <1>;
+ };
+ };
+ };
+ };
+};
+
/* MCAN interrupts are hard-wired to irqs 67, 68 */
&crossbar_mpu {
ti,irqs-skip = <10 67 68 133 139 140>;
--
2.17.1
next prev parent reply other threads:[~2019-10-18 15:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 15:48 [Patch 0/9] ARM: dts: dra7: add cal nodes Benoit Parrot
2019-10-18 15:48 ` [Patch 1/9] ARM: dts: dra7: add cam clkctrl node Benoit Parrot
2019-10-22 15:40 ` Tony Lindgren
2019-10-22 16:13 ` Benoit Parrot
2019-10-22 16:28 ` Tony Lindgren
2019-10-18 15:48 ` [Patch 2/9] ARM: OMAP: DRA7xx: Make CAM clock domain SWSUP only Benoit Parrot
2019-10-18 15:48 ` [Patch 3/9] ARM: dts: dra7-l4: Add ti-sysc node for CAM Benoit Parrot
2019-10-18 15:48 ` [Patch 4/9] ARM: dts: DRA72: Add CAL dtsi node Benoit Parrot
2019-10-18 15:48 ` [Patch 5/9] arm: dts: dra72-evm-common: Add entries for the CSI2 cameras Benoit Parrot
2019-10-22 15:44 ` Tony Lindgren
2019-10-22 16:16 ` Benoit Parrot
2019-10-22 16:27 ` Tony Lindgren
2019-10-18 15:48 ` Benoit Parrot [this message]
2019-10-18 15:48 ` [Patch 7/9] arm: dts: dra76-evm: Add CAL and OV5640 nodes Benoit Parrot
2019-10-18 15:48 ` [Patch 8/9] arm64: dts: k3-am65-main Add CAL node Benoit Parrot
2019-10-18 15:48 ` [Patch 9/9] arm64: dts: k3-am654-base-board: Add CSI2 OV5640 camera Benoit Parrot
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=20191018154849.3127-7-bparrot@ti.com \
--to=bparrot@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).