From: Rob Herring <robh@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-tegra@vger.kernel.org, Jon Hunter <jonathanh@nvidia.com>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH 15/15] dt-bindings: serial: Document Tegra234 TCU
Date: Fri, 12 Nov 2021 09:01:59 -0600 [thread overview]
Message-ID: <1636729319.995745.2842418.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <20211112120518.3679793-16-thierry.reding@gmail.com>
On Fri, 12 Nov 2021 13:05:18 +0100, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> Add the compatible string for the TCU found on the Tegra234 SoC.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> .../devicetree/bindings/serial/nvidia,tegra194-tcu.yaml | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
Running 'make dtbs_check' with the schema in this patch gives the
following warnings. Consider if they are expected or the schema is
incorrect. These may not be new warnings.
Note that it is not yet a requirement to have 0 warnings for dtbs_check.
This will change in the future.
Full log is available here: https://patchwork.ozlabs.org/patch/1554322
tcu: $nodename:0: 'tcu' does not match '^serial(@.*)?$'
arch/arm64/boot/dts/nvidia/tegra194-p2972-0000.dt.yaml
arch/arm64/boot/dts/nvidia/tegra194-p3509-0000+p3668-0000.dt.yaml
arch/arm64/boot/dts/nvidia/tegra194-p3509-0000+p3668-0001.dt.yaml
prev parent reply other threads:[~2021-11-12 15:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 12:05 [PATCH 00/15] dt-bindings: Convert Tegra DT bindings to json-schema Thierry Reding
2021-11-12 12:05 ` [PATCH 01/15] dt-bindings: misc: Convert Tegra MISC " Thierry Reding
2021-11-12 12:05 ` [PATCH 02/15] dt-bindings: mmc: tegra: Convert " Thierry Reding
2021-11-12 13:48 ` Rob Herring
2021-11-12 12:05 ` [PATCH 03/15] dt-bindings: mailbox: " Thierry Reding
2021-11-12 13:48 ` Rob Herring
2021-11-12 12:05 ` [PATCH 04/15] dt-bindings: mailbox: tegra: Document Tegra234 HSP Thierry Reding
2021-11-12 12:05 ` [PATCH 05/15] dt-bindings: rtc: tegra: Convert to json-schema Thierry Reding
2021-11-12 13:48 ` Rob Herring
2021-11-12 12:05 ` [PATCH 06/15] dt-bindings: rtc: tegra: Document Tegra234 RTC Thierry Reding
2021-11-12 12:05 ` [PATCH 07/15] dt-bindings: fuse: tegra: Convert to json-schema Thierry Reding
2021-11-12 12:05 ` [PATCH 08/15] dt-bindings: fuse: tegra: Document Tegra234 FUSE Thierry Reding
2021-11-12 12:05 ` [PATCH 09/15] dt-bindings: mmc: tegra: Document Tegra234 SDHCI Thierry Reding
2021-11-12 12:05 ` [PATCH 10/15] dt-bindings: serial: 8250: Document Tegra234 UART Thierry Reding
2021-11-12 15:01 ` Rob Herring
2021-11-12 12:05 ` [PATCH 11/15] dt-bindings: tegra: pmc: Convert to json-schema Thierry Reding
2021-11-12 15:01 ` Rob Herring
2021-11-12 12:05 ` [PATCH 12/15] dt-bindings: firmware: tegra: " Thierry Reding
2021-11-12 15:01 ` Rob Herring
2021-11-12 12:05 ` [PATCH 13/15] dt-bindings: i2c: tegra-bpmp: " Thierry Reding
2021-11-12 15:01 ` Rob Herring
2021-11-12 12:05 ` [PATCH 14/15] dt-bindings: serial: tegra-tcu: " Thierry Reding
2021-11-12 15:01 ` Rob Herring
2021-11-12 12:05 ` [PATCH 15/15] dt-bindings: serial: Document Tegra234 TCU Thierry Reding
2021-11-12 15:01 ` 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=1636729319.995745.2842418.nullmailer@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@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 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).