From: Aswath Govindraju <a-govindraju@ti.com>
To: Vignesh Raghavendra <vigneshr@ti.com>, Nishanth Menon <nm@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Grygorii Strashko <grygorii.strashko@ti.com>
Subject: Re: [PATCH] arm64: dts: ti: k3-am625-sk: Add ECAP APWM nodes
Date: Wed, 27 Apr 2022 16:36:23 +0530 [thread overview]
Message-ID: <919c9e7c-3c7b-23e9-758e-8ace5affe369@ti.com> (raw)
In-Reply-To: <20220419062902.196526-1-vigneshr@ti.com>
On 19/04/22 11:59, Vignesh Raghavendra wrote:
> AM62 has 3 ECAP instances with 1 APWM each. Add DT nodes for the same.
> Keep them disabled in am625-sk dts as these pins can be repurposed in
> user exp connector.
>
> Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
> ---
Reviewed-by: Aswath Govindraju <a-govindraju@ti.com>
Thanks,
Aswath
> arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 27 ++++++++++++++++++++++++
> arch/arm64/boot/dts/ti/k3-am625-sk.dts | 12 +++++++++++
> 2 files changed, 39 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
> index 4b6ba98dd0a2..dd972fcdaedb 100644
> --- a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
> @@ -530,4 +530,31 @@ mailbox0_cluster0: mailbox@29000000 {
> ti,mbox-num-users = <4>;
> ti,mbox-num-fifos = <16>;
> };
> +
> + ecap0: pwm@23100000 {
> + compatible = "ti,am3352-ecap";
> + #pwm-cells = <3>;
> + reg = <0x00 0x23100000 0x00 0x100>;
> + power-domains = <&k3_pds 51 TI_SCI_PD_EXCLUSIVE>;
> + clocks = <&k3_clks 51 0>;
> + clock-names = "fck";
> + };
> +
> + ecap1: pwm@23110000 {
> + compatible = "ti,am3352-ecap";
> + #pwm-cells = <3>;
> + reg = <0x00 0x23110000 0x00 0x100>;
> + power-domains = <&k3_pds 52 TI_SCI_PD_EXCLUSIVE>;
> + clocks = <&k3_clks 52 0>;
> + clock-names = "fck";
> + };
> +
> + ecap2: pwm@23120000 {
> + compatible = "ti,am3352-ecap";
> + #pwm-cells = <3>;
> + reg = <0x00 0x23120000 0x00 0x100>;
> + power-domains = <&k3_pds 53 TI_SCI_PD_EXCLUSIVE>;
> + clocks = <&k3_clks 53 0>;
> + clock-names = "fck";
> + };
> };
> diff --git a/arch/arm64/boot/dts/ti/k3-am625-sk.dts b/arch/arm64/boot/dts/ti/k3-am625-sk.dts
> index 5fc35898a1e2..2c5e0e5b826b 100644
> --- a/arch/arm64/boot/dts/ti/k3-am625-sk.dts
> +++ b/arch/arm64/boot/dts/ti/k3-am625-sk.dts
> @@ -477,3 +477,15 @@ partition@3fc0000 {
> };
> };
> };
> +
> +&ecap0 {
> + status = "disabled";
> +};
> +
> +&ecap1 {
> + status = "disabled";
> +};
> +
> +&ecap2 {
> + status = "disabled";
> +};
next prev parent reply other threads:[~2022-04-27 11:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 6:29 [PATCH] arm64: dts: ti: k3-am625-sk: Add ECAP APWM nodes Vignesh Raghavendra
2022-04-27 11:06 ` Aswath Govindraju [this message]
2022-04-27 15:20 ` Vignesh Raghavendra
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=919c9e7c-3c7b-23e9-758e-8ace5affe369@ti.com \
--to=a-govindraju@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--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).