Re: [PATCH v2 3/5] irqchip: RISC-V Local Interrupt Controller Driver
From: Anup Patel
Date: Mon Sep 10 2018 - 23:57:50 EST
On Tue, Sep 11, 2018 at 3:49 AM, Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote:
> On Mon, Sep 10, 2018 at 09:37:59PM +0200, Thomas Gleixner wrote:
>> Processor local interrupts really should be architected and there are
>> really not that many of them.
> And that is what they are.
>> But well, RISC-V decided obvsiouly not to learn from mistakes made by
> I don't think that is the case. I think Atup misreads what reserved
> means - if you look at section 2.3 of the RISC-V privileged spec
> it clearly states that reserved fields are for future use and not
> for vendor specific use.
I think I understood what reserved means here. If reserved bits are
not for vendor specific or implementation specific stuff then it should
be mentioned clearly which is not the case.
The list of currently defined RISC-V local interrupts will definitely grow
based on my experience from ARM/ARM64 world.
Like Thomas mentioned, we will definitely end-up having separate
irqchip and irq_domain for RISC-V local interrupts for flexibility. Better
do it now with separate RISC-V INTC driver.