From: Dragan Simic <dsimic@manjaro.org>
To: FUKAUMI Naoki <naoki@radxa.com>
Cc: Alexey Charkov <alchark@gmail.com>,
heiko@sntech.de, robh@kernel.org, conor+dt@kernel.org,
inindev@gmail.com, liujianfeng1994@gmail.com, jonas@kwiboo.se,
dmt.yashin@gmail.com, sebastian.reichel@collabora.com,
tim@feathertop.org, kever.yang@rock-chips.com,
marcin.juszkiewicz@linaro.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
michael.riesch@wolfvision.net, macromorgan@hotmail.com,
krzk+dt@kernel.org
Subject: Re: [PATCH 0/3] arm64: dts: rockchip: Add Radxa ROCK 5B+ and rebase Radxa ROCK 5B
Date: Wed, 25 Dec 2024 11:25:41 +0100 [thread overview]
Message-ID: <28cff8b07bc271da3672076b32f13b44@manjaro.org> (raw)
In-Reply-To: <4FAC0C844CFF6787+c12ba0e7-c1da-4fe7-aa0f-79340b9ff81a@radxa.com>
Hello Naoki,
On 2024-12-25 11:09, FUKAUMI Naoki wrote:
> On 12/25/24 17:32, Alexey Charkov wrote:
>> On Wed, Dec 25, 2024 at 12:22 PM FUKAUMI Naoki <naoki@radxa.com>
>> wrote:
>>>
>>> The Radxa ROCK 5B+ is an upgraded version of the Radxa ROCK 5B.
>>>
>>> This patch series introduces a shared .dtsi that can be used on the
>>> new Radxa ROCK 5B+, the existing Radxa ROCK 5B, and the upcoming
>>> Radxa
>>> ROCK 5T.
>>>
>>> This patch series includes "arm64: dts: rockchip: Add USB-C support
>>> to
>>> ROCK 5B" by Sebastian Reichel[1].
>>>
>>> [1]
>>> https://patchwork.kernel.org/project/linux-rockchip/patch/20241210163615.120594-1-sebastian.reichel@collabora.com/
>>>
>>> FUKAUMI Naoki (3):
>>> dt-bindings: arm: rockchip: Add Radxa ROCK 5B+
>>> arm64: dts: rockchip: Add Radxa ROCK 5B+
>>> arm64: dts: rockchip: Convert Radxa ROCK 5B to use shared .dtsi
>>
>> This one doesn't look equivalent to the existing ROCK 5B device tree
>> after your changes (I've noticed in particular that fan cooling levels
>> are different - but that's just the part I remember well since I
>> modified it earlier, there might be more differences).
>
> Thanks for pointing!
>
>> Would you mind rearranging the patches so that the split of ROCK 5B
>> dts into a common .dtsi and per-board .dts additions could be made
>> one-to-one equivalent without functional changes, and then add ROCK
>> 5B+ and any other required changes on top of that?
>
> My priority goal is to add support for ROCK 5B+ and 5T. This time, I
> will not make any changes to ROCK 5B so as not to break it. Therefore,
> I will drop PATCH 3/3.
>
> (I would like to make changes to ROCK 5B at some point.)
I see, but I think that just dropping the patch 3/3 wouldn't be the
best possible option. That way you'd end up with a "dangling" dtsi
file, used by just one board dts file, which is a bit suboptimal.
I'd suggest that you actually do it the right way, so to speak, by
actually converting the ROCK 5B dts file to use the shared dtsi file
in a way that makes the transition more obvious and, as a result,
easier to review, as already suggested above.
As another option, I'm going to ask Radxa for a sample ROCK 5B+ board
soon, for my Rockchip SoC binning project, and if I actually get it,
I could take over this series, to help you that way with getting the
patch series in better shape.
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2024-12-25 10:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 21:09 [PATCH 0/3] arm64: dts: rockchip: Add Radxa ROCK 5B+ and rebase Radxa ROCK 5B FUKAUMI Naoki
2024-12-24 21:09 ` [PATCH 1/3] dt-bindings: arm: rockchip: Add Radxa ROCK 5B+ FUKAUMI Naoki
2024-12-24 21:09 ` [PATCH 2/3] arm64: dts: " FUKAUMI Naoki
2024-12-24 21:09 ` [PATCH 3/3] arm64: dts: rockchip: Convert Radxa ROCK 5B to use shared .dtsi FUKAUMI Naoki
2024-12-25 8:32 ` [PATCH 0/3] arm64: dts: rockchip: Add Radxa ROCK 5B+ and rebase Radxa ROCK 5B Alexey Charkov
2024-12-25 9:35 ` Dragan Simic
2024-12-25 10:09 ` FUKAUMI Naoki
2024-12-25 10:25 ` Dragan Simic [this message]
2024-12-26 0:41 ` FUKAUMI Naoki
2024-12-27 15:18 ` Rob Herring (Arm)
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=28cff8b07bc271da3672076b32f13b44@manjaro.org \
--to=dsimic@manjaro.org \
--cc=alchark@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmt.yashin@gmail.com \
--cc=heiko@sntech.de \
--cc=inindev@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kever.yang@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=liujianfeng1994@gmail.com \
--cc=macromorgan@hotmail.com \
--cc=marcin.juszkiewicz@linaro.org \
--cc=michael.riesch@wolfvision.net \
--cc=naoki@radxa.com \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=tim@feathertop.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