public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: "Kumar, Udit" <u-kumar1@ti.com>
To: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>, <nm@ti.com>,
	<vigneshr@ti.com>, <kristo@kernel.org>, <robh@kernel.org>,
	<krzk+dt@kernel.org>, <conor+dt@kernel.org>
Cc: <vaishnav.a@ti.com>, <r-donadkar@ti.com>,
	<devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>, <jai.luthra@linux.dev>,
	<linux-kernel@vger.kernel.org>, <u-kumar1@ti.com>
Subject: Re: [PATCH v2 2/4] arm64: dts: ti: j722s-evm: Add MUX to control CSI2RX
Date: Fri, 9 May 2025 13:18:29 +0530	[thread overview]
Message-ID: <fed0d761-2793-4204-aff5-f65ba7dbc4bd@ti.com> (raw)
In-Reply-To: <20250508155134.2026300-3-y-abhilashchandra@ti.com>


On 5/8/2025 9:21 PM, Yemike Abhilash Chandra wrote:
> J722S EVM has the CSI2RX routed to a MIPI CSI connector and to 22-pin RPi
> camera connector through an analog mux with GPIO control, model that so
> that an overlay can control the mux state according to connected cameras.

In case you are another version,

consider to change in commit message "model that so that" to "model mux 
so that".

Reviewed-by: Udit Kumar <u-kumar1@ti.com>


>
> Signed-off-by: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>
> ---
>   arch/arm64/boot/dts/ti/k3-j722s-evm.dts | 14 ++++++++++++++
>   1 file changed, 14 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-j722s-evm.dts b/arch/arm64/boot/dts/ti/k3-j722s-evm.dts
> index 0f18fe710929..43256c71a19c 100644
> --- a/arch/arm64/boot/dts/ti/k3-j722s-evm.dts
> +++ b/arch/arm64/boot/dts/ti/k3-j722s-evm.dts
> @@ -266,6 +266,20 @@ transceiver2: can-phy2 {
>   		max-bitrate = <5000000>;
>   		standby-gpios = <&exp1 17 GPIO_ACTIVE_HIGH>;
>   	};
> +
> +	csi01_mux: mux-controller-0 {
> +		compatible = "gpio-mux";
> +		#mux-state-cells = <1>;
> +		mux-gpios = <&exp1 6 GPIO_ACTIVE_HIGH>;
> +		idle-state = <0>;
> +	};
> +
> +	csi23_mux: mux-controller-1 {
> +		compatible = "gpio-mux";
> +		#mux-state-cells = <1>;
> +		mux-gpios = <&exp1 7 GPIO_ACTIVE_HIGH>;
> +		idle-state = <0>;
> +	};
>   };
>   
>   &main_pmx0 {


  reply	other threads:[~2025-05-09  8:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08 15:51 [PATCH v2 0/4] Add overlays for IMX219 and OV5640 on J722S Yemike Abhilash Chandra
2025-05-08 15:51 ` [PATCH v2 1/4] arm64: dts: ti: j722s-evm: Add DT nodes for power regulators Yemike Abhilash Chandra
2025-05-09  7:44   ` Kumar, Udit
2025-05-08 15:51 ` [PATCH v2 2/4] arm64: dts: ti: j722s-evm: Add MUX to control CSI2RX Yemike Abhilash Chandra
2025-05-09  7:48   ` Kumar, Udit [this message]
2025-05-08 15:51 ` [PATCH v2 3/4] arm64: dts: ti: k3-j722s-evm: Add overlay for quad IMX219 Yemike Abhilash Chandra
2025-05-09  2:22   ` Nishanth Menon
2025-05-09  7:50   ` Kumar, Udit
2025-05-08 15:51 ` [PATCH v2 4/4] arm64: dts: ti: k3-j722s-evm: Add overlay for TEVI OV5640 Yemike Abhilash Chandra
2025-05-09  2:23   ` Nishanth Menon
2025-05-09  7:52   ` Kumar, Udit

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=fed0d761-2793-4204-aff5-f65ba7dbc4bd@ti.com \
    --to=u-kumar1@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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=r-donadkar@ti.com \
    --cc=robh@kernel.org \
    --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