From: Thierry Reding <thierry.reding@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: "Jon Hunter" <jonathanh@nvidia.com>,
devicetree@vger.kernel.org, linux-pwm@vger.kernel.org,
linux-tegra@vger.kernel.org,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>
Subject: Re: [PATCH] dt-bindings: pwm: tegra: Convert to json-schema
Date: Thu, 3 Nov 2022 15:03:41 +0100 [thread overview]
Message-ID: <Y2PKPeEiliZNyg/a@orome> (raw)
In-Reply-To: <166747792400.2122024.7504112765764946849.robh@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
On Thu, Nov 03, 2022 at 07:35:43AM -0500, Rob Herring wrote:
>
> On Thu, 03 Nov 2022 13:01:37 +0100, Thierry Reding wrote:
> > From: Thierry Reding <treding@nvidia.com>
> >
> > Convert the Tegra PWFM bindings from the free-form text format to
> > json-schema.
> >
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
> > ---
> > .../bindings/pwm/nvidia,tegra20-pwm.txt | 77 ----------
> > .../bindings/pwm/nvidia,tegra20-pwm.yaml | 144 ++++++++++++++++++
> > 2 files changed, 144 insertions(+), 77 deletions(-)
> > delete mode 100644 Documentation/devicetree/bindings/pwm/nvidia,tegra20-pwm.txt
> > create mode 100644 Documentation/devicetree/bindings/pwm/nvidia,tegra20-pwm.yaml
> >
>
> My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
> on your patch (DT_CHECKER_FLAGS is new in v5.13):
>
> yamllint warnings/errors:
>
> dtschema/dtc warnings/errors:
> Documentation/devicetree/bindings/pwm/nvidia,tegra20-pwm.example.dtb:0:0: /example-1/pinmux@700008d4: failed to match any schema with compatible: ['nvidia,tegra210-pinmux']
Still working on the conversion of that one.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-11-03 14:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 12:01 [PATCH] dt-bindings: pwm: tegra: Convert to json-schema Thierry Reding
2022-11-03 12:35 ` Rob Herring
2022-11-03 14:03 ` Thierry Reding [this message]
2022-11-03 14:07 ` Krzysztof Kozlowski
2022-11-03 14:14 ` Krzysztof Kozlowski
2022-11-03 14:38 ` Thierry Reding
2022-11-03 14:53 ` Krzysztof Kozlowski
2022-11-07 19:58 ` Uwe Kleine-König
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=Y2PKPeEiliZNyg/a@orome \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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).