devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Davis <afd@ti.com>
To: 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>,
	Bryan Brattlof <bb@ti.com>, Le Jin <le.jin@siemens.com>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	<linux-arm-kernel@lists.infradead.org>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Andrew Davis <afd@ti.com>
Subject: [PATCH 05/11] arm64: dts: ti: k3-am65: Enable ECAP nodes at the board level
Date: Fri, 28 Oct 2022 09:24:11 -0500	[thread overview]
Message-ID: <20221028142417.10642-6-afd@ti.com> (raw)
In-Reply-To: <20221028142417.10642-1-afd@ti.com>

ECAP nodes defined in the top-level AM65x SoC dtsi files are incomplete
and will not be functional unless they are extended with pinmux
information. (These and the EPWM nodes could be used to trigger internal
actions but they are not used like that currently)

As the pinmux is only known at the board integration level, these
nodes should only be enabled when provided with this information.

Disable the ECAP 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 | 1 +
 arch/arm64/boot/dts/ti/k3-am65-main.dtsi           | 1 +
 arch/arm64/boot/dts/ti/k3-am654-base-board.dts     | 1 +
 3 files changed, 3 insertions(+)

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 fa4b6eb02fa57..56562081a8e52 100644
--- a/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi
@@ -550,6 +550,7 @@ &mcu_cpsw {
 };
 
 &ecap0 {
+	status = "okay";
 	pinctrl-names = "default";
 	pinctrl-0 = <&ecap0_pins_default>;
 };
diff --git a/arch/arm64/boot/dts/ti/k3-am65-main.dtsi b/arch/arm64/boot/dts/ti/k3-am65-main.dtsi
index 49287f8493aea..fbb631c7664d2 100644
--- a/arch/arm64/boot/dts/ti/k3-am65-main.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am65-main.dtsi
@@ -205,6 +205,7 @@ ecap0: pwm@3100000 {
 		power-domains = <&k3_pds 39 TI_SCI_PD_EXCLUSIVE>;
 		clocks = <&k3_clks 39 0>;
 		clock-names = "fck";
+		status = "disabled";
 	};
 
 	main_spi0: spi@2100000 {
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 3f5a5ebfc8f3c..f4b8747ebaef6 100644
--- a/arch/arm64/boot/dts/ti/k3-am654-base-board.dts
+++ b/arch/arm64/boot/dts/ti/k3-am654-base-board.dts
@@ -337,6 +337,7 @@ &main_i2c2 {
 };
 
 &ecap0 {
+	status = "okay";
 	pinctrl-names = "default";
 	pinctrl-0 = <&ecap0_pins_default>;
 };
-- 
2.37.3


  parent reply	other threads:[~2022-10-28 14:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-28 14:24 [PATCH 00/11] AM65x Disable Incomplete DT Nodes Andrew Davis
2022-10-28 14:24 ` [PATCH 01/11] arm64: dts: ti: k3-am65: Enable UART nodes at the board level Andrew Davis
2022-10-28 14:24 ` [PATCH 02/11] arm64: dts: ti: k3-am65: Enable I2C " Andrew Davis
2022-10-28 14:24 ` [PATCH 03/11] arm64: dts: ti: k3-am65: Enable SPI " Andrew Davis
2022-10-28 14:24 ` [PATCH 04/11] arm64: dts: ti: k3-am65: Enable EPWM " Andrew Davis
2022-10-28 14:24 ` Andrew Davis [this message]
2022-10-28 14:24 ` [PATCH 06/11] arm64: dts: ti: k3-am65: MDIO pinmux should belong to the MDIO node Andrew Davis
2022-10-28 14:24 ` [PATCH 07/11] arm64: dts: ti: k3-am65: Enable MDIO nodes at the board level Andrew Davis
2022-10-28 14:24 ` [PATCH 08/11] arm64: dts: ti: k3-am65: Enable MCAN " Andrew Davis
2022-10-28 14:24 ` [PATCH 09/11] arm64: dts: ti: k3-am65: Enable PCIe " Andrew Davis
2022-10-28 14:24 ` [PATCH 10/11] arm64: dts: ti: k3-am65: Enable Mailbox " Andrew Davis
2022-10-28 14:24 ` [PATCH 11/11] arm64: dts: ti: k3-am65: Enable McASP " Andrew Davis
2022-10-31 14:54 ` [PATCH 00/11] AM65x Disable Incomplete DT Nodes Bryan Brattlof
2022-11-03 13:20 ` Jan Kiszka
2022-11-04  2:57 ` Nishanth Menon

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=20221028142417.10642-6-afd@ti.com \
    --to=afd@ti.com \
    --cc=bb@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jan.kiszka@siemens.com \
    --cc=kristo@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=le.jin@siemens.com \
    --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).