[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240613185902.GB2286020-robh@kernel.org>
Date: Thu, 13 Jun 2024 12:59:02 -0600
From: Rob Herring <robh@...nel.org>
To: Jiaxun Yang <jiaxun.yang@...goat.com>
Cc: Conor Dooley <conor@...nel.org>, Lee Jones <lee@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
"paulburton@...nel.org" <paulburton@...nel.org>,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
"linux-mips@...r.kernel.org" <linux-mips@...r.kernel.org>
Subject: Re: [PATCH v2 7/8] du-bindings: mips: cpu: Add img,mips compatible
On Wed, Jun 12, 2024 at 05:59:24PM +0100, Jiaxun Yang wrote:
>
>
> 在2024年6月12日六月 下午5:39,Conor Dooley写道:
> > On Wed, Jun 12, 2024 at 12:56:26PM +0100, Jiaxun Yang wrote:
> >> This compatible is used by boston.dts.
> >>
> >> Signed-off-by: Jiaxun Yang <jiaxun.yang@...goat.com>
> >> ---
> >> note: This is a wildcard compatible for all MIPS CPUs,
> >> I think we should use something like "riscv" for riscv.
> >
> > riscv systems, other than simulators etc are not meant to use the
> > "riscv" compatible. All of the real CPUs use "vendor,cpu", "riscv".
> > I'd suggest you add specific compatibles for your CPUs.
>
> Boston can be combined with many different CPUs, thus we need to have
> such compatibles.
Then you'll need different DTs. Different h/w, different DT.
No way we're taking a generic compatible like this.
Rob
Powered by blists - more mailing lists