devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dhruva Gole <d-gole@ti.com>
To: Andrew Davis <afd@ti.com>, Nishanth Menon <nm@ti.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 12/13] arm64: dts: ti: k3-am65: Enable TSCADC nodes at the board level
Date: Mon, 7 Aug 2023 11:21:25 +0530	[thread overview]
Message-ID: <cd8352a9-6ab4-dbcc-1bee-8ad76e6b3004@ti.com> (raw)
In-Reply-To: <20230802205309.257392-13-afd@ti.com>

Andrew,

On 03/08/23 02:23, Andrew Davis wrote:
> TSCADC nodes defined in the top-level AM65 SoC dtsi files are incomplete
> and may not be functional unless they are extended with pinmux and/or
> device information.
> 
> Disable the TSCADC nodes in the dtsi files and only enable the ones that
> are actually pinned out on a given board.
> 
> Signed-off-by: Andrew Davis <afd@ti.com>
> ---
>   arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi | 5 +----
>   arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi            | 2 ++
>   arch/arm64/boot/dts/ti/k3-am654-base-board.dts     | 2 ++
>   3 files changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi b/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi
> index 6041862d5aa75..ba1c14a54acf4 100644
> --- a/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi
> @@ -582,11 +582,8 @@ &mcu_spi0 {
>   	ti,pindir-d0-out-d1-in;
>   };
>   
> -&tscadc0 {
> -	status = "disabled";
> -};
> -
>   &tscadc1 {
> +	status = "okay";

The commit body says,
"Disable the TSCADC nodes in the dtsi files"

Please can we also provide some explanation on why
tscadc1 was left as okay here in a dtsi file?

>   	adc {
>   		ti,adc-channels = <0 1 2 3 4 5>;
>   	};
> diff --git a/arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi b/arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi
> index 2c9c20a9d9179..4defde540fe0b 100644
> --- a/arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi
> @@ -112,6 +112,7 @@ tscadc0: tscadc@40200000 {
>   		dmas = <&mcu_udmap 0x7100>,
>   			<&mcu_udmap 0x7101 >;
>   		dma-names = "fifo0", "fifo1";
> +		status = "disabled";
>   
>   		adc {
>   			#io-channel-cells = <1>;
> @@ -130,6 +131,7 @@ tscadc1: tscadc@40210000 {
>   		dmas = <&mcu_udmap 0x7102>,
>   			<&mcu_udmap 0x7103>;
>   		dma-names = "fifo0", "fifo1";
> +		status = "disabled";
>   
>   		adc {
>   			#io-channel-cells = <1>;
> diff --git a/arch/arm64/boot/dts/ti/k3-am654-base-board.dts b/arch/arm64/boot/dts/ti/k3-am654-base-board.dts
> index 43de7c132d343..17f45a9f7b146 100644
> --- a/arch/arm64/boot/dts/ti/k3-am654-base-board.dts
> +++ b/arch/arm64/boot/dts/ti/k3-am654-base-board.dts
> @@ -478,12 +478,14 @@ &usb0_phy {
>   };
>   
>   &tscadc0 {
> +	status = "okay";
>   	adc {
>   		ti,adc-channels = <0 1 2 3 4 5 6 7>;
>   	};
>   };
>   
>   &tscadc1 {
> +	status = "okay";
>   	adc {
>   		ti,adc-channels = <0 1 2 3 4 5 6 7>;
>   	};

-- 
Thanks and Regards,
Dhruva Gole

  reply	other threads:[~2023-08-07  5:51 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02 20:52 [PATCH 00/13] Another round of K3 DTSI disables Andrew Davis
2023-08-02 20:52 ` [PATCH 01/13] arm64: dts: ti: k3-j721e: Enable SDHCI nodes at the board level Andrew Davis
2023-08-07  5:22   ` Dhruva Gole
2023-08-02 20:52 ` [PATCH 02/13] arm64: dts: ti: k3-j7200: " Andrew Davis
2023-08-02 20:52 ` [PATCH 03/13] arm64: dts: ti: k3-j721s2: " Andrew Davis
2023-08-02 20:53 ` [PATCH 04/13] arm64: dts: ti: k3-am65: Enable OSPI " Andrew Davis
2023-08-07  6:16   ` Dhruva Gole
2023-08-07 15:18     ` Andrew Davis
2023-08-08  5:27       ` Jan Kiszka
2023-08-08 13:16         ` Andrew Davis
2023-08-02 20:53 ` [PATCH 05/13] arm64: dts: ti: k3-j721e: " Andrew Davis
2023-08-02 20:53 ` [PATCH 06/13] arm64: dts: ti: k3-j7200: " Andrew Davis
2023-08-07  5:19   ` Dhruva Gole
2023-08-02 20:53 ` [PATCH 07/13] arm64: dts: ti: k3-am64: " Andrew Davis
2023-08-07  5:18   ` Dhruva Gole
2023-08-02 20:53 ` [PATCH 08/13] arm64: dts: ti: k3-j721e: Enable GPIO " Andrew Davis
2023-08-07  5:34   ` Dhruva Gole
2023-08-02 20:53 ` [PATCH 09/13] arm64: dts: ti: k3-j721s2: " Andrew Davis
2023-08-07  5:34   ` Dhruva Gole
2023-08-02 20:53 ` [PATCH 10/13] arm64: dts: ti: k3-j7200: " Andrew Davis
2023-08-07  5:38   ` Dhruva Gole
2023-08-07 15:28     ` Andrew Davis
2023-08-07 15:42       ` Nishanth Menon
2023-08-07 16:16         ` Andrew Davis
2023-08-02 20:53 ` [PATCH 11/13] arm64: dts: ti: k3-j721e: Enable TSCADC " Andrew Davis
2023-08-02 20:53 ` [PATCH 12/13] arm64: dts: ti: k3-am65: " Andrew Davis
2023-08-07  5:51   ` Dhruva Gole [this message]
2023-08-07 15:34     ` Andrew Davis
2023-08-02 20:53 ` [PATCH 13/13] arm64: dts: ti: k3-am64: " Andrew Davis
2023-08-07  5:41   ` Dhruva Gole

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=cd8352a9-6ab4-dbcc-1bee-8ad76e6b3004@ti.com \
    --to=d-gole@ti.com \
    --cc=afd@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kristo@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=vigneshr@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).