[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231127-undying-sauciness-a5c1a2e7c89b@wendy>
Date: Mon, 27 Nov 2023 09:20:41 +0000
From: Conor Dooley <conor.dooley@...rochip.com>
To: Krzysztof Kozlowski <krzk@...nel.org>
CC: Sia Jee Heng <jeeheng.sia@...rfivetech.com>,
<paul.walmsley@...ive.com>, <palmer@...belt.com>,
<aou@...s.berkeley.edu>, <conor@...nel.org>, <kernel@...il.dk>,
<robh+dt@...nel.org>, <emil.renner.berthing@...onical.com>,
<linux-riscv@...ts.infradead.org>, <linux-kernel@...r.kernel.org>,
<leyfoon.tan@...rfivetech.com>
Subject: Re: [PATCH 7/7] riscv: dts: starfive: Add initial StarFive JH8100
device tree
On Mon, Nov 27, 2023 at 09:50:35AM +0100, Krzysztof Kozlowski wrote:
> On 27/11/2023 02:36, Sia Jee Heng wrote:
> > + chosen {
> > + stdout-path = "serial0:115200n8";
> > + };
> > +
> > + cpus {
> > + timebase-frequency = <4000000>;
>
> This was fixed recently on the mailing lists.
Actually, I only fixed this for the microchip stuff, as I don't know
whether or not having this in $board.dts is valid for other cases.
As far as I understand it, this works just like regular clock nodes, so
if the clock is provided by an off-chip crystal it is okay to have it in
$board.dts, but otherwise it should go in $soc.dts.
The same applies to the jh7100/jh7110, so if you could clarify it for
that platform too, that'd be great. Doing it in response to
https://lore.kernel.org/all/20231126-attractor-swampland-b1b95bd1322b@spud/
would be great.
Thanks,
Conor.
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists