OpenSBI Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jisheng Zhang <jszhang@kernel.org>
To: opensbi@lists.infradead.org
Subject: [PATCH] lib: utils/irqchip: plic: support T-HEAD C910 PLIC
Date: Tue, 9 May 2023 00:02:56 +0800	[thread overview]
Message-ID: <ZFkdMHZGuy+h815/@xhacker> (raw)
In-Reply-To: <CAJF2gTSroV7DDD7Z-QP6=kZeqaVy2xW_LO-Fkpe5dkEeEFVVFg@mail.gmail.com>

On Mon, May 08, 2023 at 02:29:16PM +0800, Guo Ren wrote:
> On Mon, May 8, 2023 at 2:39?AM Jisheng Zhang <jszhang@kernel.org> wrote:
> >
> > T-HEAD's C910 PLIC still needs the delegation bit setting to allow
> > access from S-mode, but it doesn't need the edge quirk. To distinguish
> > it from C906, add C910 binding.

Hi all,

This patch isn't needed any more, plz ignore it.
> >
> > Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
> > ---
> >  lib/utils/irqchip/fdt_irqchip_plic.c | 2 ++
> >  1 file changed, 2 insertions(+)
> >
> > diff --git a/lib/utils/irqchip/fdt_irqchip_plic.c b/lib/utils/irqchip/fdt_irqchip_plic.c
> > index 1aadf91..ed572f7 100644
> > --- a/lib/utils/irqchip/fdt_irqchip_plic.c
> > +++ b/lib/utils/irqchip/fdt_irqchip_plic.c
> > @@ -165,6 +165,8 @@ static const struct fdt_match irqchip_plic_match[] = {
> >         { .compatible = "sifive,plic-1.0.0" },
> >         { .compatible = "thead,c900-plic",
> c900 means c906, c908, c910. There is no c900 model, it's a series name.

I knew C900 is the series name, I made a mistake when understanding
the PLIC edge quirk.

> 
> But still, thx for the patch. If you want to join T-HEAD SoC
> maintenance work, please contact Wei Fu.
> Contributions of any are welcome.
> 

hhh, I'm a riscv enthusiast, and got a Lichee Pi 4A board, just want
to mainline its support.


      reply	other threads:[~2023-05-08 16:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-07 18:28 [PATCH] lib: utils/irqchip: plic: support T-HEAD C910 PLIC Jisheng Zhang
2023-05-08  6:29 ` Guo Ren
2023-05-08 16:02   ` Jisheng Zhang [this message]

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=ZFkdMHZGuy+h815/@xhacker \
    --to=jszhang@kernel.org \
    --cc=opensbi@lists.infradead.org \
    /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