From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Lokesh Vutla <lokeshvutla@ti.com>, Nishanth Menon <nm@ti.com>,
<kristo@kernel.org>
Cc: Device Tree Mailing List <devicetree@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, Vignesh R <vigneshr@ti.com>
Subject: Re: [PATCH v2 3/4] arm64: dts: ti: k3-am642-evm: Add pwm nodes
Date: Wed, 21 Jul 2021 21:27:28 +0300 [thread overview]
Message-ID: <5f07d2a6-2b35-5222-cec4-dba083f23c9c@ti.com> (raw)
In-Reply-To: <20210721113625.17299-4-lokeshvutla@ti.com>
On 21/07/2021 14:36, Lokesh Vutla wrote:
> ecap0 can be configured to use pad ECAP0_IN_APWM_OUT (D18) which has a
> signal connected to Pin 1 of J12 on EVM. Add support for adding this
> pinmux so that pwm can be observed on pin 1 of Header J12
>
> Also mark all un-used epwm and ecap pwm nodes as disabled.
>
> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
> ---
> arch/arm64/boot/dts/ti/k3-am642-evm.dts | 56 +++++++++++++++++++++++++
> 1 file changed, 56 insertions(+)
>
Reviewed-by: Grygorii Strashko <grygorii.strashko@ti.com>
--
Best regards,
grygorii
next prev parent reply other threads:[~2021-07-21 18:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 11:36 [PATCH v2 0/4] arm64: dts: ti: k3-am64: Add PWM nodes Lokesh Vutla
2021-07-21 11:36 ` [PATCH v2 1/4] arm64: dts: ti: k3-am64-main: Add epwm nodes Lokesh Vutla
2021-07-21 18:26 ` Grygorii Strashko
2021-07-21 11:36 ` [PATCH v2 2/4] arm64: dts: ti: k3-am64-main: Add ecap pwm nodes Lokesh Vutla
2021-07-21 18:27 ` Grygorii Strashko
2021-07-21 11:36 ` [PATCH v2 3/4] arm64: dts: ti: k3-am642-evm: Add " Lokesh Vutla
2021-07-21 18:27 ` Grygorii Strashko [this message]
2021-07-21 11:36 ` [PATCH v2 4/4] arm64: dts: ti: k3-am642-sk: " Lokesh Vutla
2021-07-21 18:27 ` Grygorii Strashko
2021-07-30 15:46 ` [PATCH v2 0/4] arm64: dts: ti: k3-am64: Add PWM nodes 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=5f07d2a6-2b35-5222-cec4-dba083f23c9c@ti.com \
--to=grygorii.strashko@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--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
all inboxes | Powered by JetHome®