linux-kernel - Re: [PATCH] of/irq: Add a quirk for controllers with their own definition of interrupt-map

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87bl21mqwk.wl-maz@kernel.org>
Date:   Tue, 30 Nov 2021 18:36:59 +0000
From:   Marc Zyngier <maz@...nel.org>
To:     "Lad, Prabhakar" <prabhakar.csengg@...il.com>
Cc:     Rob Herring <robh@...nel.org>,
        Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@...renesas.com>,
        Geert Uytterhoeven <geert@...ux-m68k.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "kernel-team@...roid.com" <kernel-team@...roid.com>,
        John Crispin <john@...ozen.org>, Biwen Li <biwen.li@....com>,
        Chris Brandt <Chris.Brandt@...esas.com>,
        "linux-renesas-soc@...r.kernel.org" 
        <linux-renesas-soc@...r.kernel.org>
Subject: Re: [PATCH] of/irq: Add a quirk for controllers with their own definition of interrupt-map

On Tue, 30 Nov 2021 12:52:21 +0000,
"Lad, Prabhakar" <prabhakar.csengg@...il.com> wrote:
> 
> On Mon, Nov 29, 2021 at 6:33 PM Rob Herring <robh@...nel.org> wrote:
> >
> > interrupts would work just fine here:
> >
> > interrupts = <GIC_SPI 4 IRQ_TYPE_LEVEL_HIGH>,
> >   <GIC_SPI 5 IRQ_TYPE_LEVEL_HIGH>,
> >   <GIC_SPI 6 IRQ_TYPE_LEVEL_HIGH>,
> >   <GIC_SPI 7 IRQ_TYPE_LEVEL_HIGH>,
> >   <GIC_SPI 8 IRQ_TYPE_LEVEL_HIGH>,
> >   <GIC_SPI 9 IRQ_TYPE_LEVEL_HIGH>,
> >   <GIC_SPI 10 IRQ_TYPE_LEVEL_HIGH>,
> >   <GIC_SPI 11 IRQ_TYPE_LEVEL_HIGH>;
> >
> > We don't need a different solution for N:1 interrupts from N:M. Sure,
> > that could become unweldy if there are a lot of interrupts (just like
> > interrupt-map), but is that an immediate problem?
> >
> It's just that with this approach the driver will have to index the
> interrupts instead of reading from DT.
> 
> Marc - is it OK with the above approach?

Anything that uses standard properties in a standard way works for me.

	M.

-- 
Without deviation from the norm, progress is not possible.