From: "Rob Herring (Arm)" <robh@kernel.org>
To: Svyatoslav Ryhel <clamor95@gmail.com>
Cc: Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
devicetree@vger.kernel.org, Thierry Reding <treding@nvidia.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v2 0/3] ARM: tegra: complete Tegra 4 and Tegra K1 device trees
Date: Fri, 07 Mar 2025 07:25:57 -0600 [thread overview]
Message-ID: <174135385223.4031140.10808514258285152164.robh@kernel.org> (raw)
In-Reply-To: <20250307081047.13724-1-clamor95@gmail.com>
On Fri, 07 Mar 2025 10:10:44 +0200, Svyatoslav Ryhel wrote:
> Complete T114 and T124 device trees.
>
> ---
> Changes in v2:
> - dropped accepted commits
> - added EPP, MPE and ISP compatibility for T114 and T124
> - added TSEC schema
> ---
>
> Svyatoslav Ryhel (3):
> dt-bindings: display: tegra: document EPP, ISP, MPE and TSEC for
> Tegra114 and Tegra124
> ARM: tegra114: complete HOST1X devices binding
> ARM: tegra124: complete HOST1X devices binding
>
> .../display/tegra/nvidia,tegra114-tsec.yaml | 70 +++++++++++++++++++
> .../display/tegra/nvidia,tegra20-epp.yaml | 12 ++--
> .../display/tegra/nvidia,tegra20-isp.yaml | 16 +++--
> .../display/tegra/nvidia,tegra20-mpe.yaml | 30 ++++++--
> arch/arm/boot/dts/nvidia/tegra114.dtsi | 65 +++++++++++++++++
> arch/arm/boot/dts/nvidia/tegra124.dtsi | 65 +++++++++++++++++
> 6 files changed, 244 insertions(+), 14 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra114-tsec.yaml
>
> --
> 2.43.0
>
>
>
My bot found new DTB warnings on the .dts files added or changed in this
series.
Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
are fixed by another series. Ultimately, it is up to the platform
maintainer whether these warnings are acceptable or not. No need to reply
unless the platform maintainer has comments.
If you already ran DT checks and didn't see these error(s), then
make sure dt-schema is up to date:
pip3 install dtschema --upgrade
New warnings running 'make CHECK_DTBS=y for arch/arm/boot/dts/nvidia/' for 20250307081047.13724-1-clamor95@gmail.com:
arch/arm/boot/dts/nvidia/tegra124-apalis-v1.2-eval.dtb: isp@54680000: reset-names:0: 'isp' was expected
from schema $id: http://devicetree.org/schemas/display/tegra/nvidia,tegra20-isp.yaml#
arch/arm/boot/dts/nvidia/tegra124-nyan-blaze.dtb: isp@54680000: reset-names:0: 'isp' was expected
from schema $id: http://devicetree.org/schemas/display/tegra/nvidia,tegra20-isp.yaml#
arch/arm/boot/dts/nvidia/tegra124-apalis-eval.dtb: isp@54680000: reset-names:0: 'isp' was expected
from schema $id: http://devicetree.org/schemas/display/tegra/nvidia,tegra20-isp.yaml#
arch/arm/boot/dts/nvidia/tegra124-nyan-big.dtb: isp@54680000: reset-names:0: 'isp' was expected
from schema $id: http://devicetree.org/schemas/display/tegra/nvidia,tegra20-isp.yaml#
arch/arm/boot/dts/nvidia/tegra124-venice2.dtb: isp@54680000: reset-names:0: 'isp' was expected
from schema $id: http://devicetree.org/schemas/display/tegra/nvidia,tegra20-isp.yaml#
arch/arm/boot/dts/nvidia/tegra124-nyan-big-fhd.dtb: isp@54680000: reset-names:0: 'isp' was expected
from schema $id: http://devicetree.org/schemas/display/tegra/nvidia,tegra20-isp.yaml#
arch/arm/boot/dts/nvidia/tegra124-jetson-tk1.dtb: isp@54680000: reset-names:0: 'isp' was expected
from schema $id: http://devicetree.org/schemas/display/tegra/nvidia,tegra20-isp.yaml#
prev parent reply other threads:[~2025-03-07 13:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 8:10 Svyatoslav Ryhel
2025-03-07 8:10 ` [PATCH v2 1/3] dt-bindings: display: tegra: document EPP, ISP, MPE and TSEC for Tegra114 and Tegra124 Svyatoslav Ryhel
2025-03-07 14:06 ` Krzysztof Kozlowski
2025-03-07 8:10 ` [PATCH v2 2/3] ARM: tegra114: complete HOST1X devices binding Svyatoslav Ryhel
2025-03-07 8:10 ` [PATCH v2 3/3] ARM: tegra124: " Svyatoslav Ryhel
2025-03-07 14:05 ` Svyatoslav Ryhel
2025-03-07 13:25 ` Rob Herring (Arm) [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=174135385223.4031140.10808514258285152164.robh@kernel.org \
--to=robh@kernel.org \
--cc=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=treding@nvidia.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
all inboxes | Powered by JetHome®