linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benoit Parrot <bparrot@ti.com>
To: Tony Lindgren <tony@atomide.com>, Tero Kristo <t-kristo@ti.com>
Cc: <linux-omap@vger.kernel.org>, <linux-clk@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Benoit Parrot <bparrot@ti.com>
Subject: [Patch v3 02/10] ARM: dts: dra7: add cam clkctrl node
Date: Tue, 12 Nov 2019 08:27:45 -0600	[thread overview]
Message-ID: <20191112142753.22976-3-bparrot@ti.com> (raw)
In-Reply-To: <20191112142753.22976-1-bparrot@ti.com>

Add clkctrl nodes for CAM domain.

Note that because of the current dts node name dependency for mapping to
clock domain, we must still use "cam-clkctrl@" naming instead of generic
"clock@" naming for the node. And because of this, it's probably best to
apply the dts node addition together along with the other clock changes.

Signed-off-by: Benoit Parrot <bparrot@ti.com>
---
 arch/arm/boot/dts/dra7xx-clocks.dtsi | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/arch/arm/boot/dts/dra7xx-clocks.dtsi b/arch/arm/boot/dts/dra7xx-clocks.dtsi
index d1c2406ec71c..199f8d483f75 100644
--- a/arch/arm/boot/dts/dra7xx-clocks.dtsi
+++ b/arch/arm/boot/dts/dra7xx-clocks.dtsi
@@ -1734,6 +1734,20 @@
 		};
 	};
 
+	cam_cm: cam-cm@1000 {
+		compatible = "ti,omap4-cm";
+		reg = <0x1000 0x100>;
+		#address-cells = <1>;
+		#size-cells = <1>;
+		ranges = <0 0x1000 0x100>;
+
+		cam_clkctrl: cam-clkctrl@20 {
+			compatible = "ti,clkctrl";
+			reg = <0x20 0x2c>;
+			#clock-cells = <2>;
+		};
+	};
+
 	dss_cm: dss-cm@1100 {
 		compatible = "ti,omap4-cm";
 		reg = <0x1100 0x100>;
-- 
2.17.1


  parent reply	other threads:[~2019-11-12 14:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-12 14:27 [Patch v3 00/10] ARM: dts: dra7: add cal nodes Benoit Parrot
2019-11-12 14:27 ` [Patch v3 01/10] clk: ti: dra7: add cam clkctrl data Benoit Parrot
2019-11-12 15:27   ` Tony Lindgren
2019-11-18 17:38   ` Rob Herring
2019-11-12 14:27 ` Benoit Parrot [this message]
2019-11-12 15:29   ` [Patch v3 02/10] ARM: dts: dra7: add cam clkctrl node Tony Lindgren
2019-11-12 14:27 ` [Patch v3 03/10] ARM: OMAP: DRA7xx: Make CAM clock domain SWSUP only Benoit Parrot
2019-11-12 15:31   ` Tony Lindgren
2019-11-12 14:27 ` [Patch v3 04/10] ARM: dts: dra7-l4: Add ti-sysc node for CAM Benoit Parrot
2019-11-12 14:27 ` [Patch v3 05/10] ARM: dts: DRA72: Add CAL dtsi node Benoit Parrot
2019-11-12 15:34   ` Tony Lindgren
2019-11-12 14:27 ` [Patch v3 06/10] arm: dts: dra72-evm-common: Add entries for the CSI2 cameras Benoit Parrot
2019-11-12 14:27 ` [Patch v3 07/10] arm: dtsi: dra76x: Add CAL dtsi node Benoit Parrot
2019-11-12 14:27 ` [Patch v3 08/10] arm: dts: dra76-evm: Add CAL and OV5640 nodes Benoit Parrot
2019-11-12 14:27 ` [Patch v3 09/10] arm64: dts: k3-am65-main Add CAL node Benoit Parrot
2019-11-12 15:38   ` Tony Lindgren
2019-11-12 14:27 ` [Patch v3 10/10] 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=20191112142753.22976-3-bparrot@ti.com \
    --to=bparrot@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.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).