From: Sandipan Patra <spatra@nvidia.com>
To: <thierry.reding@gmail.com>, <jonathanh@nvidia.com>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<devicetree@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <bbasu@nvidia.com>, <kyarlagadda@nvidia.com>,
Sandipan Patra <spatra@nvidia.com>
Subject: [PATCH 2/2] arm64: tegra: Add user PWM support on Jetson Orin
Date: Mon, 29 Aug 2022 17:14:32 +0530 [thread overview]
Message-ID: <20220829114432.19566-2-spatra@nvidia.com> (raw)
In-Reply-To: <20220829114432.19566-1-spatra@nvidia.com>
Enable in device tree and use it to drive the PWM controllers on
40 pin header of Orin dev-kit.
Signed-off-by: Sandipan Patra <spatra@nvidia.com>
---
V2: Overriding by node label instead of node path.
arch/arm64/boot/dts/nvidia/tegra234-p3737-0000.dtsi | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/arch/arm64/boot/dts/nvidia/tegra234-p3737-0000.dtsi b/arch/arm64/boot/dts/nvidia/tegra234-p3737-0000.dtsi
index a85993c85e45..5108013a18c6 100644
--- a/arch/arm64/boot/dts/nvidia/tegra234-p3737-0000.dtsi
+++ b/arch/arm64/boot/dts/nvidia/tegra234-p3737-0000.dtsi
@@ -3,3 +3,15 @@
/ {
compatible = "nvidia,p3737-0000";
};
+
+&pwm1 {
+ status = "okay";
+};
+
+&pwm5 {
+ status = "okay";
+};
+
+&pwm8 {
+ status = "okay";
+};
--
2.17.1
next prev parent reply other threads:[~2022-08-29 12:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 11:44 [PATCH 1/2] arm64: tegra: Add PWM controllers on Tegra234 Sandipan Patra
2022-08-29 11:44 ` Sandipan Patra [this message]
2022-08-30 9:50 ` Krzysztof Kozlowski
2022-09-06 8:47 ` Sandipan Patra
-- strict thread matches above, loose matches on Subject: below --
2022-08-26 12:17 Sandipan Patra
2022-08-26 12:17 ` [PATCH 2/2] arm64: tegra: Add user PWM support on Jetson Orin Sandipan Patra
2022-08-26 17:35 ` Krzysztof Kozlowski
2022-08-29 11:44 ` Sandipan Patra
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=20220829114432.19566-2-spatra@nvidia.com \
--to=spatra@nvidia.com \
--cc=bbasu@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kyarlagadda@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.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).