[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87im0xdu2a.wl-maz@kernel.org>
Date: Mon, 26 Jul 2021 15:32:45 +0100
From: Marc Zyngier <maz@...nel.org>
To: Anup Patel <anup@...infault.org>
Cc: Palmer Dabbelt <palmer@...belt.com>,
Palmer Dabbelt <palmerdabbelt@...gle.com>,
Paul Walmsley <paul.walmsley@...ive.com>,
Thomas Gleixner <tglx@...utronix.de>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Atish Patra <atish.patra@....com>,
Alistair Francis <Alistair.Francis@....com>,
linux-riscv <linux-riscv@...ts.infradead.org>,
"linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>,
DTML <devicetree@...r.kernel.org>,
Anup Patel <anup.patel@....com>
Subject: Re: [RFC PATCH v2 00/11] Linux RISC-V ACLINT Support
On Mon, 26 Jul 2021 13:45:20 +0100,
Anup Patel <anup@...infault.org> wrote:
>
> Hi Marc,
>
> I have taken the approach of IPI domains (like you suggested) in this series.
>
> What do you think ?
I have commented on the irqchip driver.
As for the RISC-V specific code, I'll let the architecture maintainers
look into it. I guess the elephant in the room is that this spec seems
to be evolving, and that there is no HW implementation (how this
driver maps on SF's CLINT is anybody's guess).
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists