From: Rob Herring <robh@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: devicetree@vger.kernel.org,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Thierry Reding" <thierry.reding@gmail.com>,
linux-renesas-soc@vger.kernel.org,
"Yoshinori Sato" <ysato@users.sourceforge.jp>,
linux-kernel@vger.kernel.org,
"Thomas Gleixner" <tglx@linutronix.de>,
linux-pwm@vger.kernel.org,
"Laurent Pinchart" <laurent.pinchart+renesas@ideasonboard.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Daniel Lezcano" <daniel.lezcano@linaro.org>,
"Lee Jones" <lee.jones@linaro.org>
Subject: Re: [PATCH v2 2/2] dt-bindings: timer: renesas,tpu: Convert to json-schema
Date: Wed, 12 May 2021 21:35:17 -0500 [thread overview]
Message-ID: <20210513023517.GA918693@robh.at.kernel.org> (raw)
In-Reply-To: <1c33e62c3a74979c3ca9580176e6cf89384caea9.1620648868.git.geert+renesas@glider.be>
On Mon, 10 May 2021 14:18:35 +0200, Geert Uytterhoeven wrote:
> Convert the Renesas H8/300 Timer Pulse Unit Device Tree binding
> documentation to json-schema.
>
> Correct clock-names, as "peripheral_clk" is the name of the supplier,
> and all users use "fck".
>
> Note that there are two different bindings for the TPU, both using
> "renesas,tpu": this one for using the TPU as a clock source (used on
> H8/300), and a second use for using the TPU as a PWM controller (used on
> ARM). To avoid conflicts, both bindings are marked with the appropriate
> "select" logic, to check for the absence respectively presence of the
> "#pwm-cells" property.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Reviewed-by: Rob Herring <robh@kernel.org>
> ---
> v2:
> - Drop unneeded "'#pwm-cells': true" from "select" section in
> renesas,tpu-pwm.yaml,
> - Add Reviewed-by.
>
> I have listed Sato-san as the maintainer, as he wrote the original
> driver and bindings.
> Sato-san: Please scream if this is inappropriate ;-)
> ---
> .../bindings/pwm/renesas,tpu-pwm.yaml | 9 +++
> .../devicetree/bindings/timer/renesas,tpu.txt | 21 -------
> .../bindings/timer/renesas,tpu.yaml | 56 +++++++++++++++++++
> 3 files changed, 65 insertions(+), 21 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/timer/renesas,tpu.txt
> create mode 100644 Documentation/devicetree/bindings/timer/renesas,tpu.yaml
>
Applied, thanks!
prev parent reply other threads:[~2021-05-13 2:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 12:18 [PATCH v2 0/2] dt-bindings: renesas,tpu: Improve and json-schema conversion Geert Uytterhoeven
2021-05-10 12:18 ` [PATCH v2 1/2] dt-bindings: pwm: renesas,tpu-pwm: Improve json-schema Geert Uytterhoeven
2021-05-12 10:00 ` Yoshinori Sato
2021-05-13 2:33 ` Rob Herring
2021-05-10 12:18 ` [PATCH v2 2/2] dt-bindings: timer: renesas,tpu: Convert to json-schema Geert Uytterhoeven
2021-05-12 10:00 ` Yoshinori Sato
2021-05-13 2:35 ` Rob Herring [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=20210513023517.GA918693@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=ysato@users.sourceforge.jp \
/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).