[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50f7fbdd-8592-7a47-b2d8-a1af8ed93b92@linaro.org>
Date: Wed, 6 Sep 2023 13:24:23 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>,
Macpaul Lin <macpaul.lin@...iatek.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
Frank Wunderlich <frank-w@...lic-files.de>,
Bernhard Rosenkränzer <bero@...libre.com>,
Sean Wang <sean.wang@...iatek.com>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org
Cc: Bear Wang <bear.wang@...iatek.com>,
Pablo Sun <pablo.sun@...iatek.com>,
Macpaul Lin <macpaul@...il.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: arm64: dts: mediatek: add mt8395-evk
board
On 06/09/2023 12:48, AngeloGioacchino Del Regno wrote:
>> Yes, mt8395 is fully compatible with mt8195.
>>
>> But after reading Angelo's comment, we thought it is necessary to create a new
>> compatible to avoid confusion for users.
>> https://lore.kernel.org/lkml/bf8394c6-5460-8696-f46b-0c39927aaf84@collabora.com/
>>
>> Although they are fully compatible, developers cannot arbitrarily replace the chip
>> on the board with another one. So separated bindings might be better.
>
> Sorry you've misunderstood; I was trying to explain to Krzysztof that the two
> SoCs are fully compatible... my suggestion was in like with what you're trying to
> do as in I am agreeing with your first version, Macpaul, to inherit MT8195.
>
> So,
>
> - enum
> - mediatek,mt8395-evk
> - const: mediatek,mt8195
> - const: mediatek,mt8395
The other way - mt8395 followed by mt8195 :)
Best regards,
Krzysztof
Powered by blists - more mailing lists