From: Akhil R <akhilrajeev@nvidia.com>
To: <devicetree@vger.kernel.org>, <digetx@gmail.com>,
<jonathanh@nvidia.com>, <ldewangan@nvidia.com>,
<linux-i2c@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, <mperttunen@nvidia.com>,
<robh+dt@kernel.org>, <thierry.reding@gmail.com>
Cc: <akhilrajeev@nvidia.com>
Subject: [PATCH v2 4/4] arm64: tegra: Add Tegra234 PWM devicetree nodes
Date: Sat, 22 Jan 2022 16:53:27 +0530 [thread overview]
Message-ID: <1642850607-20664-5-git-send-email-akhilrajeev@nvidia.com> (raw)
In-Reply-To: <1642850607-20664-1-git-send-email-akhilrajeev@nvidia.com>
Add device tree nodes for Tegra234 PWM
Signed-off-by: Akhil R <akhilrajeev@nvidia.com>
---
arch/arm64/boot/dts/nvidia/tegra234.dtsi | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/arch/arm64/boot/dts/nvidia/tegra234.dtsi b/arch/arm64/boot/dts/nvidia/tegra234.dtsi
index c686827..cbebf1e 100644
--- a/arch/arm64/boot/dts/nvidia/tegra234.dtsi
+++ b/arch/arm64/boot/dts/nvidia/tegra234.dtsi
@@ -234,6 +234,18 @@
reset-names = "i2c";
};
+ pwm1: pwm@3280000 {
+ compatible = "nvidia,tegra194-pwm",
+ "nvidia,tegra186-pwm";
+ reg = <0x3280000 0x10000>;
+ clocks = <&bpmp TEGRA234_CLK_PWM1>;
+ clock-names = "pwm";
+ resets = <&bpmp TEGRA234_RESET_PWM1>;
+ reset-names = "pwm";
+ status = "disabled";
+ #pwm-cells = <2>;
+ };
+
mmc@3460000 {
compatible = "nvidia,tegra234-sdhci", "nvidia,tegra186-sdhci";
reg = <0x03460000 0x20000>;
--
2.7.4
prev parent reply other threads:[~2022-01-22 11:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 11:23 [PATCH v2 0/4] Add I2C and PWM support for T234 Akhil R
2022-01-22 11:23 ` [PATCH v2 1/4] dt-bindings: Add headers for Tegra234 I2C Akhil R
2022-01-22 18:35 ` Dmitry Osipenko
2022-01-23 16:56 ` Akhil R
2022-01-23 21:07 ` Dmitry Osipenko
2022-01-22 11:23 ` [PATCH v2 2/4] arm64: tegra: Add Tegra234 I2C devicetree nodes Akhil R
2022-01-22 11:23 ` [PATCH v2 3/4] dt-bindings: Add headers for Tegra234 PWM Akhil R
2022-01-22 11:23 ` Akhil R [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=1642850607-20664-5-git-send-email-akhilrajeev@nvidia.com \
--to=akhilrajeev@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--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).