Interrupt chip driver maintainence
Thomas Gleixner
tglx at kernel.org
Sat Sep 5 12:12:30 PDT 2026
Nam!
On Sat, Sep 05 2026 at 04:51, Nam Cao wrote:
> Thomas Gleixner <tglx at kernel.org> writes:
>> I'm wading through my inbox full of patches for interrupt chip drivers
>> and I'm thoroughly annoyed. The way how this works today is not
>> sustainable.
>>
>> Patches end up in my and Radu's inbox and all we can do is go through
>> them mostly on a formal basis, but it's out of our scope to look at the
>> correctness vs. a particular hardware. In the past I just picked up
>> patches when I had the gut feeling they are remotely correct, but I'm
>> tired of this.
>
> I have hardware to test the SiFive PLIC. I also spent quite some time
> staring at the specification attempting to cleanse the mess we have for
> plic_irq_eoi() (which sadly yielded nothing).
>
> I can help looking at patches. Would that help moving things forward?
Help is always welcome.
But the point is that the companies who build and sell that stuff have
the responsibility to take care of it and not just dump their crap into
the kernel and then expect that someone else will take care of it for
free.
If SiFive pays you or your employer to provide that service that's fine,
but you doing it on your on [dt]ime to proliferate the carelessness of
those who profit from it is just wrong.
Thanks,
tglx
More information about the linux-riscv
mailing list