From: Tony Lindgren <tony@atomide.com>
To: Benoit Parrot <bparrot@ti.com>
Cc: Tero Kristo <t-kristo@ti.com>, Rob Herring <robh+dt@kernel.org>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [Patch 5/9] arm: dts: dra72-evm-common: Add entries for the CSI2 cameras
Date: Tue, 22 Oct 2019 08:44:46 -0700 [thread overview]
Message-ID: <20191022154446.GN5610@atomide.com> (raw)
In-Reply-To: <20191018154849.3127-6-bparrot@ti.com>
* Benoit Parrot <bparrot@ti.com> [191018 15:46]:
> Add device nodes for CSI2 camera board OV5640.
> Add the CAL port nodes with the necessary linkage to the ov5640 nodes.
>
> Signed-off-by: Benoit Parrot <bparrot@ti.com>
> ---
> arch/arm/boot/dts/dra72-evm-common.dtsi | 35 +++++++++++++++++++++++++
> 1 file changed, 35 insertions(+)
>
> diff --git a/arch/arm/boot/dts/dra72-evm-common.dtsi b/arch/arm/boot/dts/dra72-evm-common.dtsi
> index 8641a3d7d8ad..e4c01a67f6de 100644
> --- a/arch/arm/boot/dts/dra72-evm-common.dtsi
> +++ b/arch/arm/boot/dts/dra72-evm-common.dtsi
> @@ -187,6 +187,12 @@
> gpio = <&gpio5 8 GPIO_ACTIVE_HIGH>;
> enable-active-high;
> };
> +
> + clk_ov5640_fixed: clk_ov5640_fixed {
> + compatible = "fixed-clock";
> + #clock-cells = <0>;
> + clock-frequency = <24000000>;
> + };
> };
The clock node name should be generic and not use
undescores. If there is a hidden dependency to the
clock node name here, it should be mentioned in the
patch for the non-standard use.
Regards,
Tony
next prev parent reply other threads:[~2019-10-22 15:44 UTC|newest]
Thread overview: 28+ 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 ` Benoit Parrot
2019-10-18 15:48 ` [Patch 1/9] ARM: dts: dra7: add cam clkctrl node Benoit Parrot
2019-10-18 15:48 ` Benoit Parrot
2019-10-22 15:40 ` Tony Lindgren
2019-10-22 16:13 ` Benoit Parrot
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 ` 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 ` Benoit Parrot
2019-10-18 15:48 ` [Patch 4/9] ARM: dts: DRA72: Add CAL dtsi node Benoit Parrot
2019-10-18 15:48 ` 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-18 15:48 ` Benoit Parrot
2019-10-22 15:44 ` Tony Lindgren [this message]
2019-10-22 16:16 ` Benoit Parrot
2019-10-22 16:16 ` Benoit Parrot
2019-10-22 16:27 ` Tony Lindgren
2019-10-18 15:48 ` [Patch 6/9] arm: dtsi: dra76x: Add CAL dtsi node Benoit Parrot
2019-10-18 15:48 ` Benoit Parrot
2019-10-18 15:48 ` [Patch 7/9] arm: dts: dra76-evm: Add CAL and OV5640 nodes Benoit Parrot
2019-10-18 15:48 ` 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 ` Benoit Parrot
2019-10-18 15:48 ` [Patch 9/9] arm64: dts: k3-am654-base-board: Add CSI2 OV5640 camera Benoit Parrot
2019-10-18 15:48 ` 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=20191022154446.GN5610@atomide.com \
--to=tony@atomide.com \
--cc=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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.