From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Dragan Simic <dsimic@manjaro.org>
Cc: michael.opdenacker@rootcommit.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, heiko@sntech.de,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: arm: rockchip: Add Asus Tinker Board 3 and 3S
Date: Tue, 18 Nov 2025 05:27:15 +0000 (UTC) [thread overview]
Message-ID: <0c224662-b3c2-4075-8b68-c0ae27421ba8@rootcommit.com> (raw)
In-Reply-To: <e4cd11d0-463c-e707-5110-6b92899b1ba3@manjaro.org>
Hi Dragan
On 11/15/25 01:52, Dragan Simic wrote:
> I'm sorry again for not mentioning it in my earlier responses,
> but shouldn't this addition be specified like below:
>
> - description: Asus Tinker Board 3/3S
> items:
> - enum:
> - asus,rk3566-tinker-board-3
> - asus,rk3566-tinker-board-3s
> - const: rockchip,rk3566
>
> ... because the introduced .dts files define the actual board DTs,
> by descending from the common .dtsi file, while they're compatible
> in the sense of the 3S board variant extending the 3 variant.
Actually, "make dtbs_check" fails if rk3566-tinker-board-3s.dts has:
compatible = "asus,rk3566-tinker-board-3s",
"asus,rk3566-tinker-board-3", "rockchip,rk3566";
The failure is:
arch/arm64/boot/dts/rockchip/rk3566-tinker-board-3s.dtb: /
(asus,rk3566-tinker-board-3s): compatible: 'oneOf' conditional failed,
one must be fixed:
['asus,rk3566-tinker-board-3s', 'asus,rk3566-tinker-board-3',
'rockchip,rk3566'] is too long
['asus,rk3566-tinker-board-3s', 'asus,rk3566-tinker-board-3',
'rockchip,rk3566'] is too short
If I understand correctly, to keep the rk3566-tinker-board-3s.dts file
as it is, you need Asus Tinker Board 3 and 3S to have two different
descriptions as in V2:
- description: Asus Tinker Board 3 items: - const:
asus,rk3566-tinker-board-3 - const: rockchip,rk3566 - description: Asus
Tinker Board 3S items: - const: asus,rk3566-tinker-board-3s - const:
asus,rk3566-tinker-board-3 - const: rockchip,rk3566
The other solution is to remove the "asus,rk3566-tinker-board-3"
compatible from rk3566-tinker-board-3s.dts, which is not a big deal in
my opinion. In addition, if some code turns out to work only on 3 but
not on 3S, though that's not expected if 3S is indeed a superset of 3,
we won't be stuck.
I can submit a V3 along these lines.
Cheers
Michael.
--
Michael Opdenacker
Root Commit
Yocto Project and OpenEmbedded Training course - Learn by doing:
https://rootcommit.com/training/yocto/
next prev parent reply other threads:[~2025-11-18 5:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-15 0:52 [PATCH v2 1/2] dt-bindings: arm: rockchip: Add Asus Tinker Board 3 and 3S Dragan Simic
2025-11-17 10:09 ` Michael Opdenacker
2025-11-18 5:27 ` Michael Opdenacker [this message]
2025-11-19 6:47 ` Dragan Simic
2025-11-19 7:25 ` Michael Opdenacker
2025-11-19 7:28 ` Dragan Simic
-- strict thread matches above, loose matches on Subject: below --
2025-11-14 15:46 [PATCH v2 0/2] arm64: dts: rockchip: add Tinker Board 3 and 3S device tree michael.opdenacker
2025-11-14 15:46 ` [PATCH v2 1/2] dt-bindings: arm: rockchip: Add Asus Tinker Board 3 and 3S michael.opdenacker
2025-11-15 11:37 ` Krzysztof Kozlowski
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=0c224662-b3c2-4075-8b68-c0ae27421ba8@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@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).