[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <75563ad3f6bf6b6c8b151ab0cc26b490@manjaro.org>
Date: Tue, 04 Jun 2024 22:48:30 +0200
From: Dragan Simic <dsimic@...jaro.org>
To: Alexey Charkov <alchark@...il.com>
Cc: linux-rockchip@...ts.infradead.org, heiko@...ech.de,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
robh+dt@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
linux-kernel@...r.kernel.org, quentin.schulz@...rry.de, wens@...nel.org,
daniel.lezcano@...aro.org, didi.debian@...ow.org,
krzysztof.kozlowski+dt@...aro.org, viresh.kumar@...aro.org
Subject: Re: [RFC PATCH] arm64: dts: rockchip: Make preparations for
per-RK3588-variant OPPs
Hello Alexey,
On 2024-05-30 21:31, Dragan Simic wrote:
> I'm sorry for my delayed response, had some "IRL stuff" to take care
> of.
[...]
> On 2024-05-29 16:05, Alexey Charkov wrote:
>> The problem I have with -common is that there are several layers of
>> "common" even among just the three of these chip revisions, and a
>> clear inheritance hierarchy between them (i.e. RK3588j and RK3588 also
>> have a sizeable chunk of their IP blocks that is "common" between
>> these two variants, in addition to those shared among all three
>> variants)
>
> Hmm, I see, that's a rather valid concern. How about using "-base"
> for what I called "-common", and "-extra" for what I called "-fullfat",
> for the lack of a better term? Using "-extra" takes inspiration from
> the way Linux distribution package repositories are commonly named, so
> it should be rather familiar to nearly everyone.
>
> Also, "-base" and "-extra" are rather short, so their shortness would
> also make them stand out in the directory listing as something that
> isn't
> just another board .dts or .dtsi file, which can only help.
[...]
Since there were no complaints, I'll move forward with sending a "real"
patch that uses "-base" and "-extra".
Powered by blists - more mailing lists