From: Niklas Cassel <cassel@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: frank-w@public-files.de, Andrew Lunn <andrew@lunn.ch>,
Frank Wunderlich <linux@fw-web.de>,
Damien Le Moal <dlemoal@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Gregory Clement <gregory.clement@bootlin.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Hans de Goede <hdegoede@redhat.com>, Jens Axboe <axboe@kernel.dk>,
linux-ide@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1 1/3] arm64: dts: marvell: Fix anyOf conditional failed
Date: Tue, 12 Nov 2024 13:46:07 +0100 [thread overview]
Message-ID: <ZzNOD_dpK0e4WFLL@ryzen> (raw)
In-Reply-To: <ZzNL4_dFxHfMmMcR@ryzen>
On Tue, Nov 12, 2024 at 01:36:51PM +0100, Niklas Cassel wrote:
> On Mon, Nov 11, 2024 at 10:25:12AM -0600, Rob Herring wrote:
> > > >
> > > >I don't know the yaml too well, but it is not obvious how adding a few
> > > >status = "disabled"; status = "okay"; fixes a "'anyOf' conditional failed".
> > > >
> > > >Maybe you can expand the explanation a bit?
> > > >
> > > > Andrew
> > >
> > > Hi angelo,
> > >
> > > I guess the dtbs_check only checks required properties from yaml if the node is enabled.
> >
> > Yes, that is exactly how it works.
> >
> > Rob
>
> Hello Rob,
>
> If we look at e.g. this binding:
> Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml
>
> We can see that it does not define iommu-map in the binding,
> likewise the binding does have:
> unevaluatedProperties: false
>
>
> If I apply my patch that adds iommu-map for e.g. the pcie2x1l0 node:
> (the patch does not add anything to the binding above):
> https://lore.kernel.org/linux-rockchip/20241107123732.1160063-2-cassel@kernel.org/
>
>
> If look at the pcie2x1l0 node, it is marked as status = "disabled"
> in arch/arm64/boot/dts/rockchip/rk3588-extra.dtsi
>
> but is marked as status = "enabled"
> in arch/arm64/boot/dts/rockchip/rk3588-rock-5b.dts
>
> If I run CHECK_DTBS for this dts/dtb:
> $ ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- make CHECK_DTBS=y rockchip/rk3588-rock-5b.dtb
> DTC [C] arch/arm64/boot/dts/rockchip/rk3588-rock-5b.dtb
> $
>
> No warnings.
>
> What am I missing?
>
> Considering the warning in this series where the binding also
> had unevaluatedProperties: false
> I would have expected the same error for the pcie2x1l0 node.
>
> (And if I look at most PCI controler bindings, they actually do define
> iommu-map, so it seems a requirement for it to be defined if used.)
>
Or perhaps the question should have been, if iommu-map is an exception,
why isn't iommus also an exception?
Kind regards,
Niklas
next prev parent reply other threads:[~2024-11-12 12:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-09 9:46 [PATCH v1 0/3] fix some binding check errors for marvell Frank Wunderlich
2024-11-09 9:46 ` [PATCH v1 1/3] arm64: dts: marvell: Fix anyOf conditional failed Frank Wunderlich
2024-11-09 17:29 ` Andrew Lunn
2024-11-10 9:25 ` Frank Wunderlich
2024-11-10 10:20 ` Aw: " Frank Wunderlich
2024-11-11 16:25 ` Rob Herring
2024-11-11 17:15 ` Andrew Lunn
2024-11-11 18:50 ` Aw: " Frank Wunderlich
2024-11-11 20:31 ` Rob Herring
2024-11-12 12:36 ` Niklas Cassel
2024-11-12 12:46 ` Niklas Cassel [this message]
2024-11-11 20:36 ` Rob Herring
2024-11-11 21:38 ` Aw: " Frank Wunderlich
2024-12-02 11:19 ` Frank Wunderlich
2025-01-02 18:44 ` Aw: " Frank Wunderlich
2025-01-02 18:57 ` Niklas Cassel
2025-01-02 19:46 ` Rob Herring
2025-01-02 19:55 ` Frank Wunderlich
2025-01-06 15:28 ` Aw: " Gregory CLEMENT
2025-01-06 15:45 ` Frank Wunderlich
2024-11-09 9:46 ` [PATCH v1 2/3] arm64: dts: marvell: drop additional phy-names for sata Frank Wunderlich
2024-11-09 17:32 ` Andrew Lunn
2024-11-11 0:05 ` Damien Le Moal
2024-11-11 6:14 ` Frank Wunderlich
2024-11-09 9:46 ` [PATCH v1 3/3] dt-bindings: ata: ahci-platform: add missing iommus property Frank Wunderlich
2024-11-09 17:36 ` Andrew Lunn
2024-11-11 19:46 ` Conor Dooley
2024-11-12 11:24 ` (subset) [PATCH v1 0/3] fix some binding check errors for marvell Niklas Cassel
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=ZzNOD_dpK0e4WFLL@ryzen \
--to=cassel@kernel.org \
--cc=andrew@lunn.ch \
--cc=axboe@kernel.dk \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlemoal@kernel.org \
--cc=frank-w@public-files.de \
--cc=gregory.clement@bootlin.com \
--cc=hdegoede@redhat.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linux@fw-web.de \
--cc=robh@kernel.org \
--cc=sebastian.hesselbarth@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).