public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Sean Anderson <sean.anderson@seco.com>
Cc: Sean Anderson <seanga2@gmail.com>,
	David Abdurachmanov <david.abdurachmanov@gmail.com>,
	Yanhong Wang <yanhong.wang@starfivetech.com>,
	u-boot@lists.denx.de, Rick Chen <rick@andestech.com>,
	Leo <ycliang@andestech.com>, Lukasz Majewski <lukma@denx.de>,
	Lee Kuan Lim <kuanlim.lee@starfivetech.com>,
	Jianlong Huang <jianlong.huang@starfivetech.com>,
	Emil Renner Berthing <kernel@esmil.dk>
Subject: Re: [PATCH v2 14/17] riscv: dts: jh7110: Add initial StarFive JH7110 device tree
Date: Thu, 19 Jan 2023 19:25:56 +0000	[thread overview]
Message-ID: <Y8mZRFuZu/r3RFeR@spud> (raw)
In-Reply-To: <f128e47d-b8a7-aca9-253c-59d6f5c496d6@seco.com>

[-- Attachment #1: Type: text/plain, Size: 2649 bytes --]

On Thu, Jan 19, 2023 at 02:16:51PM -0500, Sean Anderson wrote:
> On 1/19/23 13:30, Conor Dooley wrote:
> > Hey Seán, David,
> > 
> > On Thu, Jan 19, 2023 at 01:26:52AM -0500, Sean Anderson wrote:
> >> On 1/19/23 01:18, David Abdurachmanov wrote:
> >> > On Wed, Jan 18, 2023 at 10:19 AM Yanhong Wang
> >> > <yanhong.wang@starfivetech.com> wrote:
> > 
> >> > > +               U74_4: cpu@4 {
> >> > > +                       compatible = "sifive,u74-mc", "riscv";
> >> > > +                       reg = <4>;
> >> > > +                       d-cache-block-size = <64>;
> >> > > +                       d-cache-sets = <64>;
> >> > > +                       d-cache-size = <32768>;
> >> > > +                       d-tlb-sets = <1>;
> >> > > +                       d-tlb-size = <40>;
> >> > > +                       device_type = "cpu";
> >> > > +                       i-cache-block-size = <64>;
> >> > > +                       i-cache-sets = <64>;
> >> > > +                       i-cache-size = <32768>;
> >> > > +                       i-tlb-sets = <1>;
> >> > > +                       i-tlb-size = <40>;
> >> > > +                       mmu-type = "riscv,sv39";
> >> > > +                       next-level-cache = <&ccache>;
> >> > > +                       riscv,isa = "rv64imafdcbsu";
> >> > 
> >> > Looking at SiFive U74 manuals, shouldn't this be RV64GC_Zba_Zbb_Sscofpmf?
> >> > U74 only supports Zba and Zbb bit manip extensions.
> >> > This is from the 21G3.02.00 release manual.
> >> > 
> >> > Looking more, S76 core is listed in the manual as supporting up to:
> >> > RV64IMAC_Zicsr_Zifencei_Zba_Zbb_Sscofpmf.
> >> > 
> >> > I almost forgot about _Zicsr_Zifencei (which are part of G). Shouldn't
> >> > those be listed too in riscv,isa?
> > 
> > AFAIU, Linux just assumes them since they weren't their own thing prior
> > to ISA spec 20191213. I think in- & ex- cluding them are both valid...
> > Yeah.
> > 
> >> AFAIK we don't support Z/X in U-Boot.
> > 
> > Does the U-Boot ISA string parsing not just ignore un-implemented
> > extensions? If it does ignore things you don't implement, then I think
> > including the Z extensions should be no harm.
> > IMO, it'd be nice to have this string match whatever the hardware can
> > support so that same Devicetree can be used for U-Boot & whatever OS it
> > is booting.
> 
> We use strchr on it; so something like Zicsr is parsed as 5 extensions.

oof, that's rough :(

Just waiting until someone comes along that *needs* one of these
extensions to be functional?

> See supports_extension for details

Will do, thanks!
Conor.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-01-19 19:26 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18  8:11 [PATCH v2 00/17] Basic StarFive JH7110 RISC-V SoC support Yanhong Wang
2023-01-18  8:11 ` [PATCH v2 01/17] riscv: cpu: jh7110: Add support for jh7110 SoC Yanhong Wang
2023-01-18  8:11 ` [PATCH v2 02/17] cache: starfive: Add StarFive JH7110 support Yanhong Wang
2023-01-18  8:11 ` [PATCH v2 03/17] dt-bindings: reset: Add StarFive JH7110 reset definitions Yanhong Wang
2023-01-18  8:11 ` [PATCH v2 04/17] reset: starfive: jh7110: Add reset driver for StarFive JH7110 SoC Yanhong Wang
2023-01-18  8:11 ` [PATCH v2 05/17] dt-bindings: clock: Add StarFive JH7110 clock definitions Yanhong Wang
2023-01-21 18:37   ` Sean Anderson
2023-01-18  8:11 ` [PATCH v2 06/17] clk: starfive: Add StarFive JH7110 clock driver Yanhong Wang
2023-01-21 18:56   ` Sean Anderson
2023-02-16  3:16     ` yanhong wang
2023-01-18  8:11 ` [PATCH v2 07/17] dt-bindings: pinctrl: Add StarFive JH7110 pinctrl definitions Yanhong Wang
2023-01-18  8:11 ` [PATCH v2 08/17] pinctrl: starfive: Add StarFive JH7110 driver Yanhong Wang
2023-01-18  8:11 ` [PATCH v2 09/17] ram: starfive: add ddr driver Yanhong Wang
2023-01-18  8:11 ` [PATCH v2 10/17] board: starfive: add StarFive VisionFive v2 board support Yanhong Wang
2023-01-21 17:38   ` Sean Anderson
2023-01-18  8:11 ` [PATCH v2 11/17] riscv: cpu: jh7110: Add Kconfig for StarFive JH7110 SoC Yanhong Wang
2023-01-18  8:11 ` [PATCH v2 13/17] board: starfive: Add TARGET_STARFIVE_VISIONFIVE2 to Kconfig Yanhong Wang
2023-01-18  8:11 ` [PATCH v2 14/17] riscv: dts: jh7110: Add initial StarFive JH7110 device tree Yanhong Wang
2023-01-19  6:18   ` David Abdurachmanov
2023-01-19  6:26     ` Sean Anderson
2023-01-19 18:30       ` Conor Dooley
2023-01-19 19:16         ` Sean Anderson
2023-01-19 19:25           ` Conor Dooley [this message]
2023-01-20  1:37             ` Sean Anderson
2023-02-16  5:50         ` yanhong wang
2023-01-18  8:11 ` [PATCH v2 15/17] riscv: dts: jh7110: Add initial u-boot " Yanhong Wang
2023-01-18  8:11 ` [PATCH v2 16/17] riscv: dts: jh7110: Add initial StarFive VisionFive v2 board " Yanhong Wang
2023-01-21 18:46   ` Sean Anderson
2023-02-16  6:20     ` yanhong wang
2023-01-18  8:11 ` [PATCH v2 17/17] configs: starfive: add starfive_visionfive2_defconfig Yanhong Wang
2023-01-23 14:53   ` Andreas Schwab
2023-02-16  7:28     ` yanhong wang
2023-02-16 14:17   ` Heinrich Schuchardt
2023-01-21 21:36 ` [PATCH v2 00/17] Basic StarFive JH7110 RISC-V SoC support Conor Dooley
2023-01-21 21:56   ` Sean Anderson
2023-01-21 22:05     ` Conor Dooley
2023-01-22 18:42       ` Conor Dooley
2023-02-10 17:41         ` Conor Dooley
2023-02-16  7:39     ` yanhong wang
2023-01-24  0:28 ` Heinrich Schuchardt
2023-02-16  9:01   ` yanhong wang
2023-01-24 14:46 ` Andreas Schwab
2023-02-06  7:38 ` Jan Kiszka
2023-02-07 15:46   ` Bin Meng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y8mZRFuZu/r3RFeR@spud \
    --to=conor@kernel.org \
    --cc=david.abdurachmanov@gmail.com \
    --cc=jianlong.huang@starfivetech.com \
    --cc=kernel@esmil.dk \
    --cc=kuanlim.lee@starfivetech.com \
    --cc=lukma@denx.de \
    --cc=rick@andestech.com \
    --cc=sean.anderson@seco.com \
    --cc=seanga2@gmail.com \
    --cc=u-boot@lists.denx.de \
    --cc=yanhong.wang@starfivetech.com \
    --cc=ycliang@andestech.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox