From: Tony Lindgren <tony@atomide.com>
To: Benoit Parrot <bparrot@ti.com>
Cc: Tero Kristo <t-kristo@ti.com>,
linux-omap@vger.kernel.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Patch v2 02/10] ARM: dts: dra7: add cam clkctrl node
Date: Fri, 8 Nov 2019 08:58:12 -0800 [thread overview]
Message-ID: <20191108165812.GG5610@atomide.com> (raw)
In-Reply-To: <20191104204853.4355-3-bparrot@ti.com>
* Benoit Parrot <bparrot@ti.com> [191104 20:49]:
> Add clkctrl nodes for CAM domain.
This too should mention that we need to use custom node naming. Other
than that this looks good to me. Again, I can queue the dts changes once
I have an immutable clock changes branch to use as base from Tero.
And up to Tero to consider if he wants to pick this clock node patch too.
Regards,
Tony
> 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
>
next prev parent reply other threads:[~2019-11-08 16:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 20:48 [Patch v2 00/10] ARM: dts: dra7: add cal nodes Benoit Parrot
2019-11-04 20:48 ` [Patch v2 01/10] clk: ti: dra7: add cam clkctrl data Benoit Parrot
2019-11-04 20:48 ` [Patch v2 02/10] ARM: dts: dra7: add cam clkctrl node Benoit Parrot
2019-11-08 16:58 ` Tony Lindgren [this message]
2019-11-04 20:48 ` [Patch v2 03/10] ARM: OMAP: DRA7xx: Make CAM clock domain SWSUP only Benoit Parrot
2019-11-04 20:48 ` [Patch v2 04/10] ARM: dts: dra7-l4: Add ti-sysc node for CAM Benoit Parrot
2019-11-04 20:48 ` [Patch v2 05/10] ARM: dts: DRA72: Add CAL dtsi node Benoit Parrot
2019-11-04 20:48 ` [Patch v2 06/10] arm: dts: dra72-evm-common: Add entries for the CSI2 cameras Benoit Parrot
2019-11-04 20:48 ` [Patch v2 07/10] arm: dtsi: dra76x: Add CAL dtsi node Benoit Parrot
2019-11-04 20:48 ` [Patch v2 08/10] arm: dts: dra76-evm: Add CAL and OV5640 nodes Benoit Parrot
2019-11-04 20:48 ` [Patch v2 09/10] arm64: dts: k3-am65-main Add CAL node Benoit Parrot
2019-11-04 20:48 ` [Patch v2 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=20191108165812.GG5610@atomide.com \
--to=tony@atomide.com \
--cc=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-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=t-kristo@ti.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).