From: Thierry Reding <thierry.reding@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
Jon Hunter <jonathanh@nvidia.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v3] dt-bindings: i2c: tegra-bpmp: Convert to json-schema
Date: Wed, 8 Dec 2021 15:43:10 +0100 [thread overview]
Message-ID: <YbDEfhIp5FCTZ8rS@orome> (raw)
In-Reply-To: <20211208143306.534700-1-thierry.reding@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
On Wed, Dec 08, 2021 at 03:33:06PM +0100, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> Convert the NVIDIA Tegra186 (and later) BPMP I2C bindings from the
> free-form text format to json-schema.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> Changes in v3:
> - include i2c-controller.yaml and use unevaluatedProperties: false
>
> Changes in v2:
> - add missing additionalProperties: false
>
> .../bindings/i2c/nvidia,tegra186-bpmp-i2c.txt | 42 -----------------
> .../i2c/nvidia,tegra186-bpmp-i2c.yaml | 45 +++++++++++++++++++
> 2 files changed, 45 insertions(+), 42 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/i2c/nvidia,tegra186-bpmp-i2c.txt
> create mode 100644 Documentation/devicetree/bindings/i2c/nvidia,tegra186-bpmp-i2c.yaml
Rob, for context, I've split this one out of the 16-patch series since
you had reviewed the other 15 already. This is the updated version that
came out of the discussion we had regarding unevaluatedProperties not
working correctly because of additionalProperties: true.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-12-08 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 14:33 [PATCH v3] dt-bindings: i2c: tegra-bpmp: Convert to json-schema Thierry Reding
2021-12-08 14:43 ` Thierry Reding [this message]
2021-12-08 18:58 ` Rob Herring
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=YbDEfhIp5FCTZ8rS@orome \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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