From: Rob Herring <robh@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: clock: tegra124-dfll: Convert to json-schema
Date: Mon, 14 Nov 2022 19:43:41 -0600 [thread overview]
Message-ID: <20221115014341.GA3956095-robh@kernel.org> (raw)
In-Reply-To: <20221111152843.627286-1-thierry.reding@gmail.com>
On Fri, Nov 11, 2022 at 04:28:42PM +0100, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> Convert the Tegra124 (and later) DFLL bindings from the free-form text
> format to json-schema.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> .../bindings/clock/nvidia,tegra124-dfll.txt | 155 ----------
> .../bindings/clock/nvidia,tegra124-dfll.yaml | 277 ++++++++++++++++++
> 2 files changed, 277 insertions(+), 155 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/clock/nvidia,tegra124-dfll.txt
> create mode 100644 Documentation/devicetree/bindings/clock/nvidia,tegra124-dfll.yaml
Looks fine, but you either have to convert the pinctrl binding first or
drop it from the example.
Rob
next prev parent reply other threads:[~2022-11-15 1:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 15:28 [PATCH 1/2] dt-bindings: clock: tegra124-dfll: Convert to json-schema Thierry Reding
2022-11-11 15:28 ` [PATCH 2/2] dt-bindings: clock: tegra: Document Tegra132 compatible Thierry Reding
2022-11-11 18:35 ` [PATCH 1/2] dt-bindings: clock: tegra124-dfll: Convert to json-schema Rob Herring
2022-11-15 1:43 ` Rob Herring [this message]
2022-11-17 17:39 ` 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=20221115014341.GA3956095-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.