From: <Conor.Dooley@microchip.com>
To: <palmer@dabbelt.com>, <maz@kernel.org>, <davidlt@rivosinc.com>
Cc: <samuel@sholland.org>, <prabhakar.mahadev-lad.rj@bp.renesas.com>,
<prabhakar.csengg@gmail.com>, <sagar.kadam@sifive.com>,
<paul.walmsley@sifive.com>, <guoren@kernel.org>,
<tglx@linutronix.de>, <geert+renesas@glider.be>,
<linux-renesas-soc@vger.kernel.org>, <biju.das.jz@bp.renesas.com>,
<krzysztof.kozlowski+dt@linaro.org>, <robh+dt@kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-riscv@lists.infradead.org>
Subject: Re: [PATCH v3 0/4] Add PLIC support for Renesas RZ/Five SoC / Fix T-HEAD PLIC edge flow
Date: Wed, 13 Jul 2022 07:00:49 +0000 [thread overview]
Message-ID: <6807a6ea-9b3e-cb9f-cb6d-1e9c5590aff1@microchip.com> (raw)
In-Reply-To: <mhng-60d46fe7-e88d-43b0-9cea-a4ae865baeb4@palmer-mbp2014>
On 13/07/2022 04:19, Palmer Dabbelt wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Fri, 01 Jul 2022 07:28:48 PDT (-0700), Marc Zyngier wrote:
>> On 2022-06-30 11:02, Samuel Holland wrote:
>>> This patch series adds PLIC support for Renesas RZ/Five SoC.
>>>
>>> Since the T-HEAD C900 PLIC has the same behavior, it also applies the
>>> fix for that variant.
>>>
>>> This series is an update of v2 of the RZ/Five series[0], and replaces
>>> the separate T-HEAD series[1].
>>>
>>> [0]:
>>> https://lore.kernel.org/linux-riscv/20220626004326.8548-1-prabhakar.mahadev-lad.rj@bp.renesas.com/
>>> [1]:
>>> https://lore.kernel.org/linux-riscv/20220627051257.38543-1-samuel@sholland.org/
>>>
>>> Changes in v3:
>>> - Add a more detailed explanation for why #interrupt-cells differs
>>> - Add andestech,nceplic100 as a fallback compatible
>>> - Separate the conditional part of the binding into two blocks (one
>>> for
>>> the PLIC implementation and the other for the SoC integration)
>>> - Use a quirk bit for selecting the flow instead of a variant ID
>>> - Use the andestech,nceplic100 compatible to select the new behavior
>>> - Use handle_edge_irq instead of handle_fasteoi_ack_irq so .irq_ack
>>> always gets called
>>> - Do not set the handler name, as RISC-V selects
>>> GENERIC_IRQ_SHOW_LEVEL
>>> - Use the same name for plic_edge_chip as plic_chip
>>>
>>> Changes in v2:
>>> - Fixed review comments pointed by Marc and Krzysztof.
>>>
>>> Changes in v1:
>>> - Fixed review comments pointed by Rob and Geert.
>>> - Changed implementation for EDGE interrupt handling on Renesas
>>> RZ/Five
>>> SoC.
>>>
>>> Lad Prabhakar (2):
>>> dt-bindings: interrupt-controller: sifive,plic: Document Renesas
>>> RZ/Five SoC
>>> irqchip/sifive-plic: Add support for Renesas RZ/Five SoC
>>>
>>> Samuel Holland (2):
>>> dt-bindings: interrupt-controller: Require trigger type for T-HEAD
>>> PLIC
>>> irqchip/sifive-plic: Fix T-HEAD PLIC edge trigger handling
>>>
>>> .../sifive,plic-1.0.0.yaml | 65 +++++++++++++--
>>> drivers/irqchip/irq-sifive-plic.c | 80 +++++++++++++++++--
>>> 2 files changed, 135 insertions(+), 10 deletions(-)
>>
>> I'm going to provisionally queue this into -next so that it
>> can get some testing. I'd still want the DT changes to be
>> Ack'ed before the next merge window though.
>
> +David, as IIRC he still tests on SiFive hardware.
Not David, but FWIW:
I have not done any specific testing, but I've been running various
-next revisions since this was put in there (on PolarFire & u540)
and have not noticed anything obviously wrong.
Thanks,
Conor.
>
> Acked-by: Palmer Dabbelt <palmer@rivosinc.com>
>
> Though I also wait for Rob on DT stuff (I saw the other thread), so not
> sure that helps any.
>
> Thanks!
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2022-07-13 7:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 10:02 [PATCH v3 0/4] Add PLIC support for Renesas RZ/Five SoC / Fix T-HEAD PLIC edge flow Samuel Holland
2022-06-30 10:02 ` [PATCH v3 1/4] dt-bindings: interrupt-controller: sifive,plic: Document Renesas RZ/Five SoC Samuel Holland
2022-06-30 10:02 ` [PATCH v3 2/4] irqchip/sifive-plic: Add support for " Samuel Holland
2022-06-30 10:02 ` [PATCH v3 3/4] dt-bindings: interrupt-controller: Require trigger type for T-HEAD PLIC Samuel Holland
2022-06-30 10:02 ` [PATCH v3 4/4] irqchip/sifive-plic: Fix T-HEAD PLIC edge trigger handling Samuel Holland
2022-06-30 23:43 ` Guo Ren
2022-07-01 14:28 ` [PATCH v3 0/4] Add PLIC support for Renesas RZ/Five SoC / Fix T-HEAD PLIC edge flow Marc Zyngier
2022-07-13 3:19 ` Palmer Dabbelt
2022-07-13 7:00 ` Conor.Dooley [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=6807a6ea-9b3e-cb9f-cb6d-1e9c5590aff1@microchip.com \
--to=conor.dooley@microchip.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=davidlt@rivosinc.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=guoren@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maz@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh+dt@kernel.org \
--cc=sagar.kadam@sifive.com \
--cc=samuel@sholland.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).