From: "Donadkar, Rishikesh" <r-donadkar@ti.com>
To: Devarsh Thakkar <devarsht@ti.com>, <nm@ti.com>, <vigneshr@ti.com>
Cc: <kristo@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <vaishnav.a@ti.com>,
<y-abhilashchandra@ti.com>, <s-jain1@ti.com>,
<jai.luthra@linux.dev>, <jai.luthra@ideasonboard.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<imx@lists.linux.dev>
Subject: Re: [PATCH v1 4/4] arm64: dts: ti: k3-am62x: Add required voltage supplies for TEVI-OV5640
Date: Fri, 2 May 2025 16:43:37 +0530 [thread overview]
Message-ID: <87d38b3d-607d-45c3-8f29-70f6c01187db@ti.com> (raw)
In-Reply-To: <f73d24a6-7da6-4bcc-95ba-9d84b865a7a7@ti.com>
On 02-05-2025 14:37, Devarsh Thakkar wrote:
>
> On 29/04/25 21:11, Rishikesh Donadkar wrote:
>> The device tree overlay for TEVI-OV5640 requires following voltage
>> supplies:
>>
>> AVDD-supply: Analog voltage supply, 2.8 volts
>> DOVDD-supply: Digital I/O voltage supply, 1.8 volts
>> DVDD-supply: Digital core voltage supply, 1.5 volts
>>
> I think this contradicts the voltage mentioned in TEVI-OV56540 doc [1]
> which mention digital voltage as 3.3 volts ?
Thank you for pointing out, I will fix it.
>
>> Add them in the DT overlay.
>>
> [1]:
> https://www.technexion.com/wp-content/uploads/2023/09/product-brief_tevi-ov5640.pdf
>
> Regards
> Devarsh
>> Signed-off-by: Rishikesh Donadkar <r-donadkar@ti.com>
>> ---
>> .../dts/ti/k3-am62x-sk-csi2-tevi-ov5640.dtso | 32 +++++++++++++++++++
>> 1 file changed, 32 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-am62x-sk-csi2-tevi-ov5640.dtso b/arch/arm64/boot/dts/ti/k3-am62x-sk-csi2-tevi-ov5640.dtso
>> index b6bfdfbbdd984..123ab0e5e8dfa 100644
>> --- a/arch/arm64/boot/dts/ti/k3-am62x-sk-csi2-tevi-ov5640.dtso
>> +++ b/arch/arm64/boot/dts/ti/k3-am62x-sk-csi2-tevi-ov5640.dtso
>> @@ -15,6 +15,33 @@ clk_ov5640_fixed: ov5640-xclk {
>> #clock-cells = <0>;
>> clock-frequency = <24000000>;
>> };
>> +
>> + reg_2p8v: regulator-2p8v {
>> + compatible = "regulator-fixed";
>> + regulator-name = "2P8V";
>> + regulator-min-microvolt = <2800000>;
>> + regulator-max-microvolt = <2800000>;
>> + vin-supply = <&vcc_3v3_sys>;
>> + regulator-always-on;
>> + };
>> +
>> + reg_1p8v: regulator-1p8v {
>> + compatible = "regulator-fixed";
>> + regulator-name = "1P8V";
>> + regulator-min-microvolt = <1800000>;
>> + regulator-max-microvolt = <1800000>;
>> + vin-supply = <&vcc_3v3_sys>;
>> + regulator-always-on;
>> + };
>> +
>> + reg_1p5v: regulator-1p5v {
>> + compatible = "regulator-fixed";
>> + regulator-name = "1P5V";
>> + regulator-min-microvolt = <1500000>;
>> + regulator-max-microvolt = <1500000>;
>> + vin-supply = <&vcc_3v3_sys>;
>> + regulator-always-on;
>> + };
>> };
>>
>> &main_i2c2 {
>> @@ -40,6 +67,11 @@ ov5640: camera@3c {
>>
>> clocks = <&clk_ov5640_fixed>;
>> clock-names = "xclk";
>> +
>> + AVDD-supply = <®_2p8v>;
>> + DOVDD-supply = <®_1p8v>;
>> + DVDD-supply = <®_1p5v>;
>> +
>> powerdown-gpios = <&exp1 13 GPIO_ACTIVE_LOW>;
>>
>> port {
prev parent reply other threads:[~2025-05-02 11:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 15:41 [PATCH v1 0/4] Fix dtbs_check warnings in sensor overlays Rishikesh Donadkar
2025-04-29 15:41 ` [PATCH v1 1/4] arm64: dts: ti: k3-am62p5-sk: Add regulator nodes for AM62P Rishikesh Donadkar
2025-05-02 7:48 ` Devarsh Thakkar
2025-04-29 15:41 ` [PATCH v1 2/4] arm64: dts: ti: k3-am62x: Add required voltage supplies for IMX219 Rishikesh Donadkar
2025-05-02 8:07 ` Devarsh Thakkar
2025-05-02 8:15 ` Devarsh Thakkar
2025-05-02 11:09 ` Donadkar, Rishikesh
2025-04-29 15:41 ` [PATCH v1 3/4] arm64: dts: ti: k3-am62x: Add required voltage supplies for OV5640 Rishikesh Donadkar
2025-05-02 8:43 ` Devarsh Thakkar
2025-04-29 15:41 ` [PATCH v1 4/4] arm64: dts: ti: k3-am62x: Add required voltage supplies for TEVI-OV5640 Rishikesh Donadkar
2025-05-02 9:07 ` Devarsh Thakkar
2025-05-02 11:13 ` Donadkar, Rishikesh [this message]
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=87d38b3d-607d-45c3-8f29-70f6c01187db@ti.com \
--to=r-donadkar@ti.com \
--cc=conor+dt@kernel.org \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=jai.luthra@ideasonboard.com \
--cc=jai.luthra@linux.dev \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=s-jain1@ti.com \
--cc=vaishnav.a@ti.com \
--cc=vigneshr@ti.com \
--cc=y-abhilashchandra@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