public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Marc Zyngier <maz@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Christopher Obbard <chris.obbard@collabora.com>,
	Benjamin Gaignard <benjamin.gaignard@collabora.com>,
	linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCHv6 0/7] Initial rk3588 DT
Date: Thu, 15 Dec 2022 11:18:28 -0600	[thread overview]
Message-ID: <20221215171828.GA153741-robh@kernel.org> (raw)
In-Reply-To: <20221214182247.79824-1-sebastian.reichel@collabora.com>

On Wed, Dec 14, 2022 at 07:22:40PM +0100, Sebastian Reichel wrote:
> Hi,
> 
> This adds initial rk3588(s) DT including two different board
> devicetrees. All required driver changes have been merged into
> the respective maintainer trees. There is one warning from the
> DT check:
> 
> $ make CHECK_DTBS=y rockchip/rk3588-evb1-v10.dtb rockchip/rk3588s-rock-5a.dtb
>   DTC_CHK arch/arm64/boot/dts/rockchip/rk3588-evb1-v10.dtb
> /home/sre/src/collabora/rode/linux-rockchip-upstream/arch/arm64/boot/dts/rockchip/rk3588-evb1-v10.dtb:
>     ethernet@fe1c0000: Unevaluated properties are not allowed ('interrupt-names', 'interrupts', 'mdio',
>     'power-domains', 'reg', 'reset-names', 'resets', 'rx-queues-config', 'snps,axi-config', 'snps,mixed-burst',
>     'snps,mtl-rx-config', 'snps,mtl-tx-config', 'snps,tso', 'stmmac-axi-config', 'tx-queues-config' were unexpected)
> 	From schema: /home/sre/src/collabora/rode/linux-rockchip-upstream/Documentation/devicetree/bindings/net/rockchip-dwmac.yaml
> 
> This is for gmac1. gmac0 has the same properties and there is no warning. Also
> rk3588s (and thus the Rock 5A) has only gmac1 and there is no warning for the
> Rock 5A. It looks like for some reason the referenced "snps,dwmac.yaml#"
> is only checked for the first node. I think it's a bug in dt-validate.
> Also the same issue can be seen with rk356x.

I believe the issue is fixed in v2022.12. I didn't reproduce it. The 
problem is with disabled nodes. In some cases 'required' failing in turn 
triggers unevaluated property failures. So we now filter out both 
errors. But that's still not enough in some cases, so the only thing 
that works is just removing disabled nodes before validation. That's not 
great if it is something where the bootloader enables the node and also 
means whomever enables a block for a board gets to fix the issues.

BTW, I do also see this warning:

arch/arm64/boot/dts/rockchip/rk3588-evb1-v10.dtb:0:0: /i2c@feaa0000/rtc@51: failed to match any schema with compatible: ['haoyu,hym8563']

Rob

  parent reply	other threads:[~2022-12-15 17:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14 18:22 [PATCHv6 0/7] Initial rk3588 DT Sebastian Reichel
2022-12-14 18:22 ` [PATCHv6 1/7] dt-bindings: soc: rockchip: add initial rk3588 syscon compatibles Sebastian Reichel
2022-12-14 18:22 ` [PATCHv6 2/7] arm64: dts: rockchip: Add rk3588 pinctrl data Sebastian Reichel
2022-12-14 18:22 ` [PATCHv6 3/7] arm64: dts: rockchip: Add base DT for rk3588 SoC Sebastian Reichel
2022-12-15  9:22   ` Marc Zyngier
2022-12-15 14:00     ` Sebastian Reichel
2022-12-15 10:45   ` Jagan Teki
2022-12-15 10:50     ` Marc Zyngier
2022-12-15 10:55       ` Jagan Teki
2022-12-14 18:22 ` [PATCHv6 4/7] dt-bindings: arm: rockchip: add initial rk3588 boards Sebastian Reichel
2023-01-05 19:20   ` Christopher Obbard
2023-01-07  0:28     ` Sebastian Reichel
2023-01-09 14:27       ` Christopher Obbard
2022-12-14 18:22 ` [PATCHv6 5/7] arm64: dts: rockchip: Add rk3588-evb1 board Sebastian Reichel
2022-12-15 13:07   ` Jagan Teki
2022-12-15 13:56     ` Sebastian Reichel
2022-12-14 18:22 ` [PATCHv6 6/7] arm64: dts: rockchip: Add rock-5a board Sebastian Reichel
2022-12-14 18:22 ` [PATCHv6 7/7] arm64: dts: rockchip: Add rock-5b board Sebastian Reichel
2022-12-15 17:18 ` Rob Herring [this message]
2022-12-15 18:17   ` [PATCHv6 0/7] Initial rk3588 DT Sebastian Reichel

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=20221215171828.GA153741-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=benjamin.gaignard@collabora.com \
    --cc=chris.obbard@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=kernel@collabora.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=maz@kernel.org \
    --cc=sebastian.reichel@collabora.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