From: Rob Herring <robh@kernel.org>
To: Lokesh Vutla <lokeshvutla@ti.com>
Cc: linux-pwm@vger.kernel.org,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Vignesh R <vigneshr@ti.com>,
tony@atomide.com,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
Nishanth Menon <nm@ti.com>, Rob Herring <robh+dt@kernel.org>,
Device Tree Mailing List <devicetree@vger.kernel.org>,
Sekhar Nori <nsekhar@ti.com>,
lee.jones@linaro.org, u.kleine-koenig@pengutronix.de,
thierry.reding@gmail.com
Subject: Re: [PATCH v2 2/4] dt-bindings: pwm: tiehrpwm: Make clock and clock-names as required properties
Date: Fri, 4 Jun 2021 15:57:47 -0500 [thread overview]
Message-ID: <20210604205747.GA3904064@robh.at.kernel.org> (raw)
In-Reply-To: <20210528045817.16618-3-lokeshvutla@ti.com>
On Fri, 28 May 2021 10:28:15 +0530, Lokesh Vutla wrote:
> Driver fails to probe when 'clock' and 'clock-names' properties are not
> populated in DT. But the binding documentation says these properties are
> optional. Fix this by making 'clock' and 'clock-names' properties as
> required.
>
> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
> ---
> Documentation/devicetree/bindings/pwm/pwm-tiehrpwm.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-06-04 20:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 4:58 [PATCH v2 0/4] dt-bindings: pwm: pwm-tiehrpwm: Convert to json schema Lokesh Vutla
2021-05-28 4:58 ` [PATCH v2 1/4] arm: dts: ti: drop usage of redundant compatible Lokesh Vutla
2021-06-04 20:57 ` Rob Herring
2021-05-28 4:58 ` [PATCH v2 2/4] dt-bindings: pwm: tiehrpwm: Make clock and clock-names as required properties Lokesh Vutla
2021-06-04 20:57 ` Rob Herring [this message]
2021-05-28 4:58 ` [PATCH v2 3/4] dt-bindings: pwm: pwm-tiehrpwm: Convert to json schema Lokesh Vutla
2021-05-28 4:58 ` [PATCH v2 4/4] dt-bindings: pwm: pwm-tiehrpwm: Add compatible string for AM64 SoC Lokesh Vutla
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=20210604205747.GA3904064@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=nsekhar@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).