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: Mon, 17 Nov 2025 10:09:04 +0000 (UTC) [thread overview]
Message-ID: <ae5c3bab-69fa-42c0-8beb-e5fdf0c95251@rootcommit.com> (raw)
In-Reply-To: <e4cd11d0-463c-e707-5110-6b92899b1ba3@manjaro.org>
Hi Dragan
Oops, indeed I overlooked this message!
On 11/15/25 01:52, Dragan Simic wrote:
> Hello Michael,
>
> Thanks for the v2! Please, see some remarks below.
>
> On Friday, November 14, 2025 16:46 CET, michael.opdenacker@rootcommit.com wrote:
>> From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
> I'm sorry for not mentioning it in my earlier responses, but this
> line is redundant, because it duplicates the From value found in
> the actual email message.
>
>> Document the compatible strings for Asus Tinker Board 3 [1] and 3S [2],
>> which are SBCs based on the Rockchip 3566 SoC.
>>
>> The "3S" version ("S" for "storage") just adds a 16 GB eMMC
>> and a "mask ROM" DIP switch to the "3" version.
>>
>> [1] https://tinker-board.asus.com/series/tinker-board-3.html
>> [2] https://tinker-board.asus.com/series/tinker-board-3s.html
>>
>> Signed-off-by: Michael Opdenacker <michael.opdenacker@rootcommit.com>
>> ---
>> Documentation/devicetree/bindings/arm/rockchip.yaml | 11 +++++++++++
>> 1 file changed, 11 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/arm/rockchip.yaml b/Documentation/devicetree/bindings/arm/rockchip.yaml
>> index 6aceaa8acbb2..cd249325a4d9 100644
>> --- a/Documentation/devicetree/bindings/arm/rockchip.yaml
>> +++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
>> @@ -86,6 +86,17 @@ properties:
>> - const: asus,rk3288-tinker-s
>> - const: rockchip,rk3288
>>
>> + - 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
>> +
>> - description: Beelink A1
>> items:
>> - const: azw,beelink-a1
> 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.
Indeed, that's the way it should be, looking at the rest of the
rockchip.yaml file.
I was too hypnotized by the section for the original Tinkerboard, which
doesn't follow this either (I'll send a separate patch).
Thanks a lot!
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-17 10:09 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 [this message]
2025-11-18 5:27 ` Michael Opdenacker
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=ae5c3bab-69fa-42c0-8beb-e5fdf0c95251@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).