From: Marc Zyngier <maz@kernel.org>
To: Sander Vanheule <sander@svanheule.net>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
kernel-team@android.com, Rob Herring <robh@kernel.org>,
John Crispin <john@phrozen.org>, Biwen Li <biwen.li@nxp.com>,
Chris Brandt <chris.brandt@renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH] of/irq: Add a quirk for controllers with their own definition of interrupt-map
Date: Tue, 23 Nov 2021 09:12:01 +0000 [thread overview]
Message-ID: <87pmqrck2m.wl-maz@kernel.org> (raw)
In-Reply-To: <39e2b51913ef6049103d3cb67df9048514c12484.camel@svanheule.net>
On Tue, 23 Nov 2021 08:40:29 +0000,
Sander Vanheule <sander@svanheule.net> wrote:
>
> Hi Marc,
>
> On Mon, 2021-11-22 at 10:30 +0000, Marc Zyngier wrote:
> > Since 041284181226 ("of/irq: Allow matching of an interrupt-map local
> > to an interrupt controller"), a handful of interrupt controllers have
> > stopped working correctly. This is due to the DT exposing a non-sensical
> > interrupt-map property, and their drivers relying on the kernel ignoring
> > this property.
> >
> > Since we cannot realistically fix this terrible behaviour, add a quirk
> > for the limited set of devices that have implemented this monster,
> > and document that this is a pretty bad practice.
> >
> > Cc: Rob Herring <robh@kernel.org>
> > Cc: John Crispin <john@phrozen.org>
> > Cc: Biwen Li <biwen.li@nxp.com>
> > Cc: Chris Brandt <chris.brandt@renesas.com>
> > Cc: Geert Uytterhoeven <geert+renesas@glider.be>
> > Signed-off-by: Marc Zyngier <maz@kernel.org>
>
> Thanks for the patch. As far as I can tell, this restores the old
> behaviour from 5.15 for "realtek,rtl-intc" and things work as
> expected.
Thanks for testing. Let's see what Rob says about this approach (I bet
he won't be thrilled...).
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2021-11-23 9:12 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
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 [this message]
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=87pmqrck2m.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=biwen.li@nxp.com \
--cc=chris.brandt@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=john@phrozen.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sander@svanheule.net \
/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).