From: Dragan Simic <dsimic@manjaro.org>
To: Alexey Charkov <alchark@gmail.com>
Cc: linux-rockchip@lists.infradead.org, heiko@sntech.de,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
robh+dt@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
linux-kernel@vger.kernel.org, quentin.schulz@cherry.de,
wens@kernel.org, daniel.lezcano@linaro.org,
didi.debian@cknow.org, krzysztof.kozlowski+dt@linaro.org,
viresh.kumar@linaro.org
Subject: Re: [RFC PATCH] arm64: dts: rockchip: Make preparations for per-RK3588-variant OPPs
Date: Tue, 04 Jun 2024 22:48:30 +0200 [thread overview]
Message-ID: <75563ad3f6bf6b6c8b151ab0cc26b490@manjaro.org> (raw)
In-Reply-To: <82db817a908b761d8c3d73ea04714314@manjaro.org>
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".
next prev parent reply other threads:[~2024-06-04 20:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 2:13 [RFC PATCH] arm64: dts: rockchip: Make preparations for per-RK3588-variant OPPs Dragan Simic
2024-05-29 9:57 ` Alexey Charkov
2024-05-29 10:45 ` Dragan Simic
2024-05-29 12:04 ` Alexey Charkov
2024-05-29 12:22 ` Dragan Simic
2024-05-29 14:05 ` Alexey Charkov
2024-05-30 19:31 ` Dragan Simic
2024-05-31 11:27 ` Jonas Karlman
2024-05-31 11:44 ` Alexey Charkov
2024-05-31 23:32 ` Jonas Karlman
2024-05-31 21:24 ` Dragan Simic
2024-05-31 23:15 ` Jonas Karlman
2024-05-31 23:39 ` Dragan Simic
2024-06-04 20:48 ` Dragan Simic [this message]
2024-05-29 11:09 ` Diederik de Haas
2024-05-29 11:33 ` Dragan Simic
2024-05-31 2:45 ` Dragan Simic
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=75563ad3f6bf6b6c8b151ab0cc26b490@manjaro.org \
--to=dsimic@manjaro.org \
--cc=alchark@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=didi.debian@cknow.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=quentin.schulz@cherry.de \
--cc=robh+dt@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=wens@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).