From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Bjorn Helgaas <helgaas@kernel.org>, Marc Zyngier <maz@kernel.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
"R.T.Dickinson" <rtd2@xtra.co.nz>,
Matthew Leaman <matthew@a-eon.biz>,
Darren Stevens <darren@stevens-zone.net>,
mad skateman <madskateman@gmail.com>
Subject: Re: [PATCH] of/irq: Don't ignore interrupt-controller when interrupt-map failed
Date: Fri, 12 Nov 2021 16:43:12 +0100 [thread overview]
Message-ID: <aae33774-a09b-9585-abc7-57cfee5c84af@xenosoft.de> (raw)
In-Reply-To: <20211112150415.GA1401861@bhelgaas>
On 12 November 2021 at 04:04 pm, Bjorn Helgaas wrote:
> On Fri, Nov 12, 2021 at 02:36:44PM +0000, Marc Zyngier wrote:
>> Since 041284181226 ("of/irq: Allow matching of an interrupt-map local
>> to an interrupt controller"), the irq code favors using an interrupt-map
>> over a interrupt-controller property if both are available, while the
>> earlier behaviour was to ignore the interrupt-map altogether.
>>
>> However, we now end-up with the opposite behaviour, which is to
>> ignore the interrupt-controller property even if the interrupt-map
>> fails to match its input. This new behaviour breaks the AmigaOne
>> X1000 machine, which ships with an extremely "creative" (read:
>> broken) device tree.
>>
>> Fix this by allowing the interrupt-controller property to be selected
>> when interrupt-map fails to match anything.
>>
>> Fixes: 041284181226 ("of/irq: Allow matching of an interrupt-map local to an interrupt controller")
>> Reported-by: Christian Zigotzky <chzigotzky@xenosoft.de>
>> Signed-off-by: Marc Zyngier <maz@kernel.org>
>> Link: https://lore.kernel.org/r/78308692-02e6-9544-4035-3171a8e1e6d4@xenosoft.de
>> Cc: Rob Herring <robh@kernel.org>
>> Cc: Bjorn Helgaas <bhelgaas@google.com>
> I'm not qualified to review this, but since 041284181226 was merged
> via my tree along with the rest of the Apple stuff, let me know if
> you'd like me to merge this.
>
> I see Rob has a comment, so if you want to take care merging it
> yourself, that's certainly fine with me.
>
>> ---
>> drivers/of/irq.c | 13 ++++++++++---
>> 1 file changed, 10 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/of/irq.c b/drivers/of/irq.c
>> index 32be5a03951f..508fb1717de3 100644
>> --- a/drivers/of/irq.c
>> +++ b/drivers/of/irq.c
>> @@ -161,9 +161,10 @@ int of_irq_parse_raw(const __be32 *addr, struct of_phandle_args *out_irq)
>> * if it is then we are done, unless there is an
>> * interrupt-map which takes precedence.
>> */
>> + bool intc = of_property_read_bool(ipar, "interrupt-controller");
>> +
>> imap = of_get_property(ipar, "interrupt-map", &imaplen);
>> - if (imap == NULL &&
>> - of_property_read_bool(ipar, "interrupt-controller")) {
>> + if (imap == NULL && intc) {
>> pr_debug(" -> got it !\n");
>> return 0;
>> }
>> @@ -244,8 +245,14 @@ int of_irq_parse_raw(const __be32 *addr, struct of_phandle_args *out_irq)
>>
>> pr_debug(" -> imaplen=%d\n", imaplen);
>> }
>> - if (!match)
>> + if (!match) {
>> + if (intc) {
>> + pr_debug("%pOF interrupt-map failed, using interrupt-controller\n", ipar);
>> + return 0;
>> + }
>> +
>> goto fail;
>> + }
>>
>> /*
>> * Successfully parsed an interrrupt-map translation; copy new
>> --
>> 2.30.2
>>
Could you please merge it asap for the RC1? Then we can compile the RC1
without these patches.
Thanks to all for your help and sorry for bother you with all these
mails. I do this work alongside my main job and actually I don't have
time for bisecting.
-- Christian
next prev parent reply other threads:[~2021-11-12 15:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 14:36 [PATCH] of/irq: Don't ignore interrupt-controller when interrupt-map failed Marc Zyngier
2021-11-12 14:57 ` Rob Herring
2021-11-12 15:26 ` Marc Zyngier
2021-11-12 15:04 ` Bjorn Helgaas
2021-11-12 15:28 ` Marc Zyngier
2021-11-12 15:55 ` Rob Herring
2021-11-12 15:43 ` Christian Zigotzky [this message]
2021-11-12 16:01 ` 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=aae33774-a09b-9585-abc7-57cfee5c84af@xenosoft.de \
--to=chzigotzky@xenosoft.de \
--cc=bhelgaas@google.com \
--cc=darren@stevens-zone.net \
--cc=devicetree@vger.kernel.org \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madskateman@gmail.com \
--cc=matthew@a-eon.biz \
--cc=maz@kernel.org \
--cc=robh@kernel.org \
--cc=rtd2@xtra.co.nz \
/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).