devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Jon Hunter <jonathanh@nvidia.com>,
	devicetree@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v2 00/16] dt-bindings: Convert Tegra DT bindings to json-schema
Date: Thu, 9 Dec 2021 18:05:17 +0100	[thread overview]
Message-ID: <YbI3TUt7+n5RFc45@orome> (raw)
In-Reply-To: <20211119143839.1950739-1-thierry.reding@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2167 bytes --]

On Fri, Nov 19, 2021 at 03:38:23PM +0100, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
> 
> Hi,
> 
> this set of patches converts some Tegra-specific DT bindings to
> json-schema and, where appropriate, adds Tegra234 compatible strings.
> The goal is to prepare existing schemas to allow validation of the
> existing Tegra234 device tree files.
> 
> I've got a follow-up series that adds more Tegra234 support and will
> extend/convert bindings along the way to keep things validatable.
> 
> Rob, since all of these are Tegra-specific and given that I have some
> follow-up work based on these, I think it'd be best if I picked these
> up into the Tegra tree once you're happy with them.
> 
> Changes in v2:
> - address various linting and validation warnings
> - add patch for BPMP thermal bindings
> 
> Thierry
> 
> Thierry Reding (16):
>   dt-bindings: misc: Convert Tegra MISC to json-schema
>   dt-bindings: mmc: tegra: Convert to json-schema
>   dt-bindings: mailbox: tegra: Convert to json-schema
>   dt-bindings: mailbox: tegra: Document Tegra234 HSP
>   dt-bindings: rtc: tegra: Convert to json-schema
>   dt-bindings: rtc: tegra: Document Tegra234 RTC
>   dt-bindings: fuse: tegra: Convert to json-schema
>   dt-bindings: fuse: tegra: Document Tegra234 FUSE
>   dt-bindings: mmc: tegra: Document Tegra234 SDHCI
>   dt-bindings: serial: 8250: Document Tegra234 UART
>   dt-bindings: tegra: pmc: Convert to json-schema
>   dt-bindings: firmware: tegra: Convert to json-schema
>   dt-bindings: i2c: tegra-bpmp: Convert to json-schema
>   dt-bindings: thermal: tegra186-bpmp: Convert to json-schema
>   dt-bindings: serial: tegra-tcu: Convert to json-schema
>   dt-bindings: serial: Document Tegra234 TCU

Hi Rob,

you applied v3 of patch 13 in this series that I sent separately but had
reviewed or acked all the others. Do you want to pick these up yourself,
or should I take them in via the Tegra tree? If you'd rather pick them
up yourself I can resend the remainder of the series.

Sorry, splitting up the patches like that was probably more confusing
than it was worth it.

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2021-12-09 17:05 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-19 14:38 [PATCH v2 00/16] dt-bindings: Convert Tegra DT bindings to json-schema Thierry Reding
2021-11-19 14:38 ` [PATCH v2 01/16] dt-bindings: misc: Convert Tegra MISC " Thierry Reding
2021-11-30  1:29   ` Rob Herring
2021-11-19 14:38 ` [PATCH v2 02/16] dt-bindings: mmc: tegra: Convert " Thierry Reding
2021-11-30  1:31   ` Rob Herring
2021-11-19 14:38 ` [PATCH v2 03/16] dt-bindings: mailbox: " Thierry Reding
2021-11-30  1:32   ` Rob Herring
2021-11-19 14:38 ` [PATCH v2 04/16] dt-bindings: mailbox: tegra: Document Tegra234 HSP Thierry Reding
2021-11-30  1:32   ` Rob Herring
2021-11-19 14:38 ` [PATCH v2 05/16] dt-bindings: rtc: tegra: Convert to json-schema Thierry Reding
2021-11-30  1:33   ` Rob Herring
2021-11-19 14:38 ` [PATCH v2 06/16] dt-bindings: rtc: tegra: Document Tegra234 RTC Thierry Reding
2021-11-30  1:33   ` Rob Herring
2021-11-19 14:38 ` [PATCH v2 07/16] dt-bindings: fuse: tegra: Convert to json-schema Thierry Reding
2021-11-30  1:35   ` Rob Herring
2021-11-19 14:38 ` [PATCH v2 08/16] dt-bindings: fuse: tegra: Document Tegra234 FUSE Thierry Reding
2021-11-30  1:35   ` Rob Herring
2021-11-19 14:38 ` [PATCH v2 09/16] dt-bindings: mmc: tegra: Document Tegra234 SDHCI Thierry Reding
2021-11-30  1:35   ` Rob Herring
2021-11-19 14:38 ` [PATCH v2 10/16] dt-bindings: serial: 8250: Document Tegra234 UART Thierry Reding
2021-11-30  1:36   ` Rob Herring
2021-11-19 14:38 ` [PATCH v2 11/16] dt-bindings: tegra: pmc: Convert to json-schema Thierry Reding
2021-11-30  1:41   ` Rob Herring
2021-11-19 14:38 ` [PATCH v2 12/16] dt-bindings: firmware: tegra: " Thierry Reding
2021-11-30  1:43   ` Rob Herring
2021-11-19 14:38 ` [PATCH v2 13/16] dt-bindings: i2c: tegra-bpmp: " Thierry Reding
2021-11-23 16:34   ` Rob Herring
2021-11-30  1:44   ` Rob Herring
2021-12-01 17:42     ` Thierry Reding
2021-12-01 18:42       ` Rob Herring
2021-12-02 17:55         ` Thierry Reding
2021-12-02 21:08           ` Rob Herring
2021-12-02 22:38             ` Rob Herring
2021-11-19 14:38 ` [PATCH v2 14/16] dt-bindings: thermal: tegra186-bpmp: " Thierry Reding
2021-11-30  1:44   ` Rob Herring
2021-11-19 14:38 ` [PATCH v2 15/16] dt-bindings: serial: tegra-tcu: " Thierry Reding
2021-11-23 16:34   ` Rob Herring
2021-11-30  1:45   ` Rob Herring
2021-11-19 14:38 ` [PATCH v2 16/16] dt-bindings: serial: Document Tegra234 TCU Thierry Reding
2021-11-23 16:34   ` Rob Herring
2021-11-30  1:45   ` Rob Herring
2021-12-09 17:05 ` Thierry Reding [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=YbI3TUt7+n5RFc45@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;
as well as URLs for NNTP newsgroup(s).