From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Ioana Ciornei <ioana.ciornei@nxp.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Johan Hovold <johan+linaro@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Rob Herring (Arm)" <robh@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] irqchip/ls-extirq: convert to a platform driver
Date: Fri, 12 Dec 2025 15:54:42 +0100 [thread overview]
Message-ID: <6251595.lOV4Wx5bFT@steina-w> (raw)
In-Reply-To: <aakkyfa3wqmguzodxbtckhozkvcgr3buka6k4fpjhlfzlvchzr@f76yf2rp3gff>
[-- Attachment #1: Type: text/plain, Size: 2310 bytes --]
Hi,
Am Freitag, 12. Dezember 2025, 15:17:05 CET schrieb Ioana Ciornei:
> On Fri, Dec 12, 2025 at 10:51:12AM +0100, Alexander Stein wrote:
> > Hi,
> >
> > thanks for bringing this to me.
> >
> > Am Freitag, 12. Dezember 2025, 02:24:19 CET schrieb Thomas Gleixner:
> > > On Fri, Dec 05 2025 at 17:57, Ioana Ciornei wrote:
> > > > Since there is no need for ls-extirq to be initialized early, convert it
> > > > to a proper platform driver. Instead of using IRQCHIP_DECLARE, add an
> > > > of_device_id array with the same compatible strings as before. Also
> > > > change the prototype and name of the probe function and adjust it to a
> > > > platform_device structure.
> > > >
> > > > With this change we also have the added advantage of avoiding the
> > > > irqchip_init() -> of_irq_init() code path which imposes dt checks that
> > > > the ls-extirq does not comply with because of its improper use of the
> > > > interrupt-map property.
> > > >
> > > > Fixes: 1b1f04d8271e ("of/irq: Ignore interrupt parent for nodes without interrupts")
> > >
> > > I'm not seeing how that Fixes tag is related. Your changelog clearly
> > > lacks a proper explanation.
> > >
> > > Aside of that there is this series:
> > >
> > > https://lore.kernel.org/20251201105144.539450-1-alexander.stein@ew.tq-group.com
> > >
> > > which is way more complete and cleans up the thing nicely instead of
> > > just converting it to a platform driver with minimal effort.
> >
> > There is still one open question: How to deal with the scfg/isc nodes?
> > Use patch 2/2 of this series to make them additional pm-busses or move the
> > ls-ext-irq nodes outside of it?
>
> To move the ls-extirq nodes outside of syscon means that we break
> compatibility with the old device trees which I don't like.
Yep, me too.
> I would much more prefer to use the approach in patch 2/2 of making the
> scfg/isc nodes pm-busses.
To be honest I'm not fond of it, but if this is the way to keep
compatiblity, why not?
Let's see what maintainers comment on that.
Best regards,
Alexander
--
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-12-12 14:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 15:57 [PATCH v2 0/2] irqchip: convert ls-extirq to a platform driver Ioana Ciornei
2025-12-05 15:57 ` [PATCH v2 1/2] irqchip/ls-extirq: convert " Ioana Ciornei
2025-12-12 1:24 ` Thomas Gleixner
2025-12-12 9:51 ` Alexander Stein
2025-12-12 14:17 ` Ioana Ciornei
2025-12-12 14:54 ` Alexander Stein [this message]
2025-12-12 14:13 ` Ioana Ciornei
2025-12-05 15:57 ` [PATCH v2 2/2] bus: simple-pm-bus: probe the Layerscape SCFG node Ioana Ciornei
2026-01-13 15:33 ` [PATCH v2 0/2] irqchip: convert ls-extirq to a platform driver Vladimir Oltean
2026-01-13 18:36 ` Thomas Gleixner
2026-01-13 18:43 ` Vladimir Oltean
2026-01-13 20:20 ` Thomas Gleixner
2026-01-14 12:00 ` Ioana Ciornei
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=6251595.lOV4Wx5bFT@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=ioana.ciornei@nxp.com \
--cc=johan+linaro@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
--cc=ulf.hansson@linaro.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