[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
<PN0PR01MB103937D1C23820E0FC43BEA33FECF2@PN0PR01MB10393.INDPRD01.PROD.OUTLOOK.COM>
Date: Sat, 1 Mar 2025 09:58:24 +0800
From: Chen Wang <unicorn_wang@...look.com>
To: Conor Dooley <conor@...nel.org>, Zixian Zeng <sycamoremoon376@...il.com>
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Paul Walmsley
<paul.walmsley@...ive.com>, Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>, Inochi Amaoto <inochiama@...look.com>,
Alexandre Ghiti <alex@...ti.fr>, devicetree@...r.kernel.org,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
sophgo@...ts.linux.dev, chao.wei@...hgo.com, xiaoguang.xing@...hgo.com
Subject: Re: [PATCH v2] riscv: sophgo: dts: Add spi controller for SG2042
On 2025/3/1 2:22, Conor Dooley wrote:
[......]
>> +
>> + spi0: spi@...0004000 {
>> + compatible = "snps,dw-apb-ssi";
> I thought were were dropping the use of "snps,dw-abp-ssi" in isolation,
> and starting to require soc-specific compatibles now.
>
> Rob, Krzysztof?
I'm also very interested to know why we can't just use
"snps,dw-abp-ssi", maybe I missed some discussion ...
I googled examples of soc-specific defined in the code, and it doesn't
seem to be much, only arch/mips/boot/dts/mscc/ocelot.dtsi and
arch/riscv/boot/dts/thead/th1520.dtsi.
Specially, I looked at the commits for th1520 and saw this
https://lore.kernel.org/linux-riscv/20240703-garbage-explicit-bd95f8deb716@wendy/.
It tells if the fallback works identically, then the specific compatible
is not needed.
This makes me more confused :)
Regards,
Chen
Powered by blists - more mailing lists