From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>
Cc: michael.opdenacker@rootcommit.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v3 1/2] dt-bindings: arm: rockchip: Add Asus Tinker Board 3/3S
Date: Tue, 18 Nov 2025 19:57:23 +0000 (UTC) [thread overview]
Message-ID: <4e7bb5f5-30bb-4ed5-bb32-3008caa1826a@rootcommit.com> (raw)
In-Reply-To: <e134902e-e298-45d0-b94f-77748bb948c4@kernel.org>
Hi Krzysztof
Thanks for the new review!
On 11/18/25 17:31, Krzysztof Kozlowski wrote:
> On 18/11/2025 16:56, Michael Opdenacker wrote:
>> 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>
>>
>> ---
>>
>> Changes in V3:
>>
>> - Remove this Acked-by as the binding code changed substantially:
>> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Above commit msg and DTS suggests they are pretty compatible with each
> other, so I don't quite get why this changed. Your changelog says
> "unexpectedly turns out to be compatible with 3 but not 3S.", but is
> this real or are you just guessing? I think you were tricked to change
> correct code into this.
I was just guessing. The likelihood that something working on 3 doesn't
work on 3s looks very small indeed, but I'm not the manufacturer to
completely rule this out.
>
> Anyway, however odd this is, I don't care enough to stop this patchset, so:
>
> Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
Thanks again!
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 19:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 15:56 [PATCH v3 0/2] arm64: dts: rockchip: add Tinker Board 3 and 3S device tree Michael Opdenacker
2025-11-18 15:56 ` [PATCH v3 1/2] dt-bindings: arm: rockchip: Add Asus Tinker Board 3/3S Michael Opdenacker
2025-11-18 16:31 ` Krzysztof Kozlowski
2025-11-18 19:57 ` Michael Opdenacker [this message]
2025-11-19 7:00 ` Dragan Simic
2025-11-19 7:09 ` Krzysztof Kozlowski
2025-11-19 7:23 ` Dragan Simic
2025-11-19 7:31 ` Krzysztof Kozlowski
2025-11-19 7:40 ` Dragan Simic
2025-11-19 7:48 ` Krzysztof Kozlowski
2025-11-19 7:54 ` Dragan Simic
2025-11-19 7:32 ` Michael Opdenacker
2025-11-19 7:33 ` Dragan Simic
2025-11-18 15:56 ` [PATCH v3 2/2] arm64: dts: rockchip: Add Asus Tinker Board 3 and 3S device tree Michael Opdenacker
2025-11-20 22:23 ` [PATCH v3 0/2] arm64: dts: rockchip: add " Heiko Stuebner
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=4e7bb5f5-30bb-4ed5-bb32-3008caa1826a@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@linaro.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).