From: Rob Herring <robh@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Marc Zyngier <maz@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Android Kernel Team <kernel-team@android.com>,
John Crispin <john@phrozen.org>, Biwen Li <biwen.li@nxp.com>,
Chris Brandt <chris.brandt@renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Sander Vanheule <sander@svanheule.net>
Subject: Re: [PATCH v2] of/irq: Add a quirk for controllers with their own definition of interrupt-map
Date: Fri, 3 Dec 2021 11:17:35 -0600 [thread overview]
Message-ID: <YapRL+2gQBjNyK4p@robh.at.kernel.org> (raw)
In-Reply-To: <CAMuHMdXM34nNz1nfowNqDvdsdg+d69Bo3_ufs6fbcq65iYd5-A@mail.gmail.com>
On Thu, Dec 02, 2021 at 04:06:21PM +0100, Geert Uytterhoeven wrote:
> Hi Marc,
>
> On Wed, Dec 1, 2021 at 12:41 PM Marc Zyngier <maz@kernel.org> 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>
> > Cc: Sander Vanheule <sander@svanheule.net>
> > Signed-off-by: Marc Zyngier <maz@kernel.org>
> > ---
> >
> > Notes:
> > v2: Switched over to of_device_compatible_match() as per Rob's
> > request.
>
> Thanks for the update!
>
> > --- a/drivers/of/irq.c
> > +++ b/drivers/of/irq.c
>
> > @@ -159,12 +179,16 @@ int of_irq_parse_raw(const __be32 *addr, struct of_phandle_args *out_irq)
> > /*
> > * Now check if cursor is an interrupt-controller and
> > * if it is then we are done, unless there is an
> > - * interrupt-map which takes precedence.
> > + * interrupt-map which takes precedence if we're not
> > + * in presence of once of these broken platform that
>
> one
and 'platforms'. Will fixup.
>
> > + * want to parse interrupt-map themselves for $reason.
> > */
> > bool intc = of_property_read_bool(ipar, "interrupt-controller");
> > + bool imap_abuse;
> >
> > imap = of_get_property(ipar, "interrupt-map", &imaplen);
> > - if (imap == NULL && intc) {
> > + imap_abuse = imap && of_device_compatible_match(ipar, of_irq_imap_abusers);
>
> ... = intc && imap && of_device_compatible_match(...)
Why? Then we are comparing intc twice because we still need it for the
intc && !imap case.
>
> > + if (intc && (imap == NULL || imap_abuse)) {
> > pr_debug(" -> got it !\n");
> > return 0;
> > }
>
> Still working fine on RZ/A1, so
> Tested-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
next prev parent reply other threads:[~2021-12-03 17:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 11:41 [PATCH v2] of/irq: Add a quirk for controllers with their own definition of interrupt-map Marc Zyngier
2021-12-02 15:06 ` Geert Uytterhoeven
2021-12-03 17:17 ` Rob Herring [this message]
2021-12-03 17:29 ` Rob Herring
2021-12-03 17:17 ` Rob Herring
2021-12-13 19:59 ` Vladimir Oltean
2021-12-13 20:27 ` Marc Zyngier
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=YapRL+2gQBjNyK4p@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=biwen.li@nxp.com \
--cc=chris.brandt@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=john@phrozen.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.