[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e49bfb8f-23e9-c834-62c7-a40528a2ef06@baylibre.com>
Date: Wed, 3 Jul 2019 13:51:48 +0200
From: Neil Armstrong <narmstrong@...libre.com>
To: Martin Blumenstingl <martin.blumenstingl@...glemail.com>
Cc: jbrunet@...libre.com, khilman@...libre.com,
linux-arm-kernel@...ts.infradead.org,
linux-amlogic@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-clk@...r.kernel.org, linux-gpio@...r.kernel.org
Subject: Re: [RFC/RFT v3 09/14] arm64: dts: move common G12A & G12B modes to
meson-g12-common.dtsi
On 03/07/2019 01:54, Martin Blumenstingl wrote:
> Hi Neil,
>
> On Mon, Jul 1, 2019 at 11:13 AM Neil Armstrong <narmstrong@...libre.com> wrote:
>>
>> To simplify the representation of differences betweem the G12A and G12B
>> SoCs, move the common nodes into a meson-g12-common.dtsi file and
>> express the CPU nodes and differences in meson-g12a.dtsi and meson-g12b.dtsi.
>>
>> This separation will help for DVFS and future Amlogic SM1 Family support.
>>
>> The sd_emmc_a quirk is added in the g12a/g12b since since it's already
>> known the sd_emmc_a controller is fixed in the next SM1 SoC family.
> too bad they named the upcoming SoC family SM1
Yeah weird naming, but seems SM1 is the new "AI" oriented SoC family
>
> does it make sense to name this file "meson-g12a-g12b-sm1-common.dtsi" instead?
> do you know whether there will be a successor to G12B and what it's
> code-name will be?
meson-g12a-g12b-sm1-common seems a bit long to me...
We don't have naming of the future SoCs, since SM1 is only available on
prototypes yet.
Neil
>
>
> Martin
>
Powered by blists - more mailing lists