From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: <Conor.Dooley@microchip.com>
Cc: kettenis@openbsd.org, kernel@esmil.dk, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: dts: startfive: currect number of external interrupts
Date: Mon, 6 Jun 2022 20:47:35 +0200 (CEST) [thread overview]
Message-ID: <d3cdaa88f562dcda@bloch.sibelius.xs4all.nl> (raw)
In-Reply-To: <6acff7ab-6f97-b17a-ce9a-a526aac81181@microchip.com> (Conor.Dooley@microchip.com)
> From: <Conor.Dooley@microchip.com>
> Date: Mon, 6 Jun 2022 16:45:44 +0000
>
> On 06/06/2022 17:29, Mark Kettenis wrote:
> > [PATCH] riscv: dts: startfive: currect number of external interrupts
>
> Just as a nit: s/startfive/starfive
I keep making that typo...
> > The PLIC integrated on the Vic_U7_Core integrated on the StarFive
> > JH7100 SoC actually supports 133 external interrupts. 127 of these
> > are exposed to the outside world; the remainder are used by other
> > devices that are part of the core-complex such as the L2 cache
> > controller. But all 133 interrupts are external interrupts as far
> > as the PLIC is concerned. Fixing the property that specifies the
> > number of external interrupts allows the driver to manage these
> > additional interrupts, whch is important since the interrupts for
> > the L2 cache controller are enabled by default.
>
> This sentence is a little hard to follow, maybe:
> Fix the property so that the driver can manage these additional
> external interrupts, which is important...
Thanks, yes, that is better.
> Also, I suppose:
> Fixes: ec85362fb121 ("RISC-V: Add initial StarFive JH7100 device tree")
Sure.
I'll send out a V2 with a fixed commit message in a week or so.
> > ---
> > arch/riscv/boot/dts/starfive/jh7100.dtsi | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/arch/riscv/boot/dts/starfive/jh7100.dtsi b/arch/riscv/boot/dts/starfive/jh7100.dtsi
> > index 69f22f9aad9d..f48e232a72a7 100644
> > --- a/arch/riscv/boot/dts/starfive/jh7100.dtsi
> > +++ b/arch/riscv/boot/dts/starfive/jh7100.dtsi
> > @@ -118,7 +118,7 @@ plic: interrupt-controller@c000000 {
> > interrupt-controller;
> > #address-cells = <0>;
> > #interrupt-cells = <1>;
> > - riscv,ndev = <127>;
> > + riscv,ndev = <133>;
> > };
> >
> > clkgen: clock-controller@11800000 {
> > --
> > 2.36.0
> >
> >
> > _______________________________________________
> > linux-riscv mailing list
> > linux-riscv@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-riscv
>
prev parent reply other threads:[~2022-06-06 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 16:29 Mark Kettenis
2022-06-06 16:45 ` Conor.Dooley
2022-06-06 18:47 ` Mark Kettenis [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=d3cdaa88f562dcda@bloch.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=Conor.Dooley@microchip.com \
--cc=aou@eecs.berkeley.edu \
--cc=devicetree@vger.kernel.org \
--cc=kernel@esmil.dk \
--cc=kettenis@openbsd.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®