From: Krzysztof Kozlowski <krzk@kernel.org>
To: Mark Brown <broonie@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Rob Herring <robh@kernel.org>,
Saravana Kannan <saravanak@google.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Samuel Holland <samuel@sholland.org>,
Marc Zyngier <maz@kernel.org>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Magnus Damm <magnus.damm@gmail.com>,
devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [PATCH v2] of/irq: Ignore interrupt parent for nodes without interrupts
Date: Tue, 18 Nov 2025 20:55:14 +0100 [thread overview]
Message-ID: <1a4d2276-75e1-4aa0-8ff2-c932ce5d6edc@kernel.org> (raw)
In-Reply-To: <b037f67a-b241-4689-9914-57ff578c1454@sirena.org.uk>
On 18/11/2025 20:34, Mark Brown wrote:
> On Fri, Nov 14, 2025 at 11:47:54AM +0100, Geert Uytterhoeven wrote:
>> The Devicetree Specification states:
>>
>> The root of the interrupt tree is determined when traversal of the
>> interrupt tree reaches an interrupt controller node without an
>> interrupts property and thus no explicit interrupt parent.
>>
>> However, of_irq_init() gratuitously assumes that a node without
>> interrupts has an actual interrupt parent if it finds an
>> interrupt-parent property higher up in the device tree. Hence when such
>> a property is present (e.g. in the root node), the root interrupt
>> controller may not be detected as such, causing a panic:
>
> I'm seeing a boot regression on the TI x15 platform in -next which
> bisects to this patch in -next, unfortunately even with earlycon (though
> just earlycon, I don't know the platform specific runes) the board just
> dies with no output:
>
> https://validation.linaro.org/scheduler/job/4252918#L409
>
> It does seem like a plausible patch for this sort of issue though, and
> the bisect converges smoothly:
All Samsung platforms fail as well. I was waiting with bisection but
Marek was as usually very fast:
https://lore.kernel.org/all/20251118115037.1866871-1-m.szyprowski@samsung.com/
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-11-18 19:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 10:47 Geert Uytterhoeven
2025-11-17 17:27 ` Rob Herring (Arm)
2025-11-18 19:34 ` Mark Brown
2025-11-18 19:55 ` Krzysztof Kozlowski [this message]
2025-11-19 8:53 ` Geert Uytterhoeven
2025-11-19 9:55 ` Marek Szyprowski
2025-11-19 10:59 ` Geert Uytterhoeven
2025-11-20 10:11 ` Jon Hunter
2025-11-28 16:42 ` Ioana Ciornei
2025-11-28 17:09 ` Ioana Ciornei
2025-12-01 12:09 ` Rob Herring
2025-12-01 12:50 ` Geert Uytterhoeven
2025-12-01 14:34 ` Rob Herring
2025-12-02 16:36 ` Ioana Ciornei
2025-12-02 21:19 ` Rob Herring
2025-12-03 9:48 ` Ioana Ciornei
2025-12-03 9:57 ` Geert Uytterhoeven
2025-12-03 14:55 ` Rob Herring
2025-12-19 8:10 ` patchwork-bot+linux-riscv
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=1a4d2276-75e1-4aa0-8ff2-c932ce5d6edc@kernel.org \
--to=krzk@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=m.szyprowski@samsung.com \
--cc=magnus.damm@gmail.com \
--cc=maz@kernel.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@kernel.org \
--cc=samuel@sholland.org \
--cc=saravanak@google.com \
/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
Powered by JetHome