public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	Christian Zigotzky <chzigotzky@xenosoft.de>,
	Rob Herring <robh@kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH] of/irq: Don't ignore interrupt-controller when interrupt-map failed
Date: Fri, 12 Nov 2021 15:28:46 +0000	[thread overview]
Message-ID: <87fss18kb5.wl-maz@kernel.org> (raw)
In-Reply-To: <20211112150415.GA1401861@bhelgaas>

On Fri, 12 Nov 2021 15:04:15 +0000,
Bjorn Helgaas <helgaas@kernel.org> 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.

I have a couple of IRQ patches that need to go in, so happy to route
it via the irqchip tree if Rob gives his blessing.

	M.

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

  reply	other threads:[~2021-11-12 15:28 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 [this message]
2021-11-12 15:55     ` Rob Herring
2021-11-12 15:43   ` Christian Zigotzky
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=87fss18kb5.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=chzigotzky@xenosoft.de \
    --cc=devicetree@vger.kernel.org \
    --cc=helgaas@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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