From: Rob Herring <robh@kernel.org>
To: Lokesh Vutla <lokeshvutla@ti.com>
Cc: linux-pwm@vger.kernel.org, thierry.reding@gmail.com,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
tony@atomide.com, lee.jones@linaro.org,
Device Tree Mailing List <devicetree@vger.kernel.org>,
Grygorii Strashko <grygorii.strashko@ti.com>,
u.kleine-koenig@pengutronix.de, Nishanth Menon <nm@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
Vignesh R <vigneshr@ti.com>
Subject: Re: [PATCH v3 2/2] dt-bindings: pwm: pwm-tiehrpwm: Add compatible string for AM64 SoC
Date: Wed, 2 Jun 2021 14:35:40 -0500 [thread overview]
Message-ID: <20210602193540.GA3845460@robh.at.kernel.org> (raw)
In-Reply-To: <20210601054402.2223-3-lokeshvutla@ti.com>
On Tue, 01 Jun 2021 11:14:02 +0530, Lokesh Vutla wrote:
> Add compatible string for AM64 SoC in device tree binding.
> EPWM IP in AM64 does not support High resolution, so named epwm instead
> of ehrpwm in compatible. However IP is till compatible with features
> supported by driver with ti,am3352-ehrpwm compatible.
>
> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
> ---
> Documentation/devicetree/bindings/pwm/pwm-tiehrpwm.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-06-02 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 5:44 [PATCH v3 0/2] dt-bindings: pwm: pwm-tiehrpwm: Convert to json schema Lokesh Vutla
2021-06-01 5:44 ` [PATCH v3 1/2] " Lokesh Vutla
2021-06-02 19:35 ` Rob Herring
2021-06-01 5:44 ` [PATCH v3 2/2] dt-bindings: pwm: pwm-tiehrpwm: Add compatible string for AM64 SoC Lokesh Vutla
2021-06-02 19:35 ` Rob Herring [this message]
2021-06-04 9:48 ` [PATCH v3 0/2] dt-bindings: pwm: pwm-tiehrpwm: Convert to json schema Thierry Reding
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=20210602193540.GA3845460@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=tony@atomide.com \
--cc=u.kleine-koenig@pengutronix.de \
--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).