From: Marc Zyngier <maz@kernel.org>
To: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"kernel-team@android.com" <kernel-team@android.com>,
John Crispin <john@phrozen.org>, Biwen Li <biwen.li@nxp.com>,
Chris Brandt <Chris.Brandt@renesas.com>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] of/irq: Add a quirk for controllers with their own definition of interrupt-map
Date: Tue, 30 Nov 2021 18:36:59 +0000 [thread overview]
Message-ID: <87bl21mqwk.wl-maz@kernel.org> (raw)
In-Reply-To: <CA+V-a8sVS_1hUWJ3uM+VffGyMtdnctBOJTyHTQAoJZGOh0a1Tw@mail.gmail.com>
On Tue, 30 Nov 2021 12:52:21 +0000,
"Lad, Prabhakar" <prabhakar.csengg@gmail.com> wrote:
>
> On Mon, Nov 29, 2021 at 6:33 PM Rob Herring <robh@kernel.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.
next prev parent reply other threads:[~2021-11-30 18:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 10:30 [PATCH] of/irq: Add a quirk for controllers with their own definition of interrupt-map Marc Zyngier
2021-11-22 13:10 ` Geert Uytterhoeven
2021-11-22 13:54 ` Marc Zyngier
2021-11-22 16:58 ` Geert Uytterhoeven
2021-11-23 7:57 ` Geert Uytterhoeven
2021-11-23 8:33 ` Marc Zyngier
2021-11-23 8:44 ` Geert Uytterhoeven
2021-11-23 9:11 ` Marc Zyngier
2021-11-24 7:54 ` Geert Uytterhoeven
2021-11-24 11:14 ` Marc Zyngier
2021-11-27 0:42 ` Prabhakar Mahadev Lad
2021-11-29 10:34 ` Marc Zyngier
2021-11-29 12:13 ` Lad, Prabhakar
2021-11-29 18:33 ` Rob Herring
2021-11-30 12:52 ` Lad, Prabhakar
2021-11-30 18:36 ` Marc Zyngier [this message]
2021-12-01 13:36 ` Lad, Prabhakar
2021-12-01 14:35 ` Rob Herring
2021-12-01 16:16 ` Lad, Prabhakar
2021-12-05 22:27 ` Lad, Prabhakar
2021-12-06 10:26 ` Marc Zyngier
2021-12-06 16:55 ` Lad, Prabhakar
2021-12-06 18:59 ` Rob Herring
2021-11-23 11:02 ` Geert Uytterhoeven
2021-11-23 8:40 ` Sander Vanheule
2021-11-23 9:12 ` Marc Zyngier
2021-11-29 19:15 ` Rob Herring
2021-11-29 19:31 ` Marc Zyngier
2021-11-29 19:40 ` Rob Herring
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=87bl21mqwk.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=Chris.Brandt@renesas.com \
--cc=biwen.li@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=john@phrozen.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@kernel.org \
/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).