From: Andreas Kemnade <andreas@kemnade.info>
To: Roger Quadros <rogerq@kernel.org>
Cc: tony@atomide.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-omap@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
khilman@baylibre.com, aaro.koskinen@iki.fi
Subject: Re: [PATCH] ARM: dts: ti/omap: omap4-serial: fix interrupts syntax
Date: Sat, 4 Jan 2025 19:20:15 +0100 [thread overview]
Message-ID: <20250104192015.0a7a4f47@akair> (raw)
In-Reply-To: <3bde5a34-4bb8-42a3-ad5c-eeb495c6aa6d@kernel.org>
Am Sat, 4 Jan 2025 19:45:35 +0200
schrieb Roger Quadros <rogerq@kernel.org>:
> Hi Andreas,
>
> On 30/12/2024 21:55, Andreas Kemnade wrote:
> > Usually interrupts are overwritten in the board file to specify a
> > mux-dependent dedicated wakeup irq, so there is interrupts and
> > interrupts-extended property which is not allowed. That has generated a
> > lot of noise during dts changes if just a phandle involved has randomly
> > changed.
> >
> > Avoid that mess by specifying interrupts-extended in the dtsi file.
> >
> > Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
> > Reported-by: Rob Herring <robh@kernel.org>
> > Closes: https://lore.kernel.org/linux-omap/173558214240.2262575.18233884215338168789.robh@kernel.org/
> > Closes: https://lore.kernel.org/linux-omap/172784021601.525825.18405282128990798038.robh@kernel.org/
> > ---
> > arch/arm/boot/dts/ti/omap/omap4-l4.dtsi | 8 ++++----
> > 1 file changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/arch/arm/boot/dts/ti/omap/omap4-l4.dtsi b/arch/arm/boot/dts/ti/omap/omap4-l4.dtsi
> > index 3fcef3080eae..150dd84c9e0f 100644
> > --- a/arch/arm/boot/dts/ti/omap/omap4-l4.dtsi
> > +++ b/arch/arm/boot/dts/ti/omap/omap4-l4.dtsi
> > @@ -1414,7 +1414,7 @@ SYSC_OMAP2_SOFTRESET |
> > uart3: serial@0 {
> > compatible = "ti,omap4-uart";
> > reg = <0x0 0x100>;
> > - interrupts = <GIC_SPI 74 IRQ_TYPE_LEVEL_HIGH>;
> > + interrupts-extended = <&wakeupgen GIC_SPI 74 IRQ_TYPE_LEVEL_HIGH>;
>
> At this point interrupts-extended is not applicable.
>
we have it this way also in omap3. I do not understand what is the
problem with it. Do you have a pointer where it is forbidden?
At least
Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
says nothing againt using it in such cases.
> We could use
> /delete-property/ interrupts
> in the board files that needs multiple interrupt parents?
>
What is the advantage of using that more complex solution? I would then
prefer to have the same with omap3 and omap4. If we do anything about
interrupts in board file here, they will have multiple parents.
Regards,
Andreas
next prev parent reply other threads:[~2025-01-04 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 19:55 [PATCH] ARM: dts: ti/omap: omap4-serial: fix interrupts syntax Andreas Kemnade
2025-01-04 17:45 ` Roger Quadros
2025-01-04 18:20 ` Andreas Kemnade [this message]
2025-01-07 12:15 ` Roger Quadros
2025-01-07 18:56 ` Andreas Kemnade
2025-01-07 12:23 ` Roger Quadros
2025-02-06 0:37 ` Kevin Hilman
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=20250104192015.0a7a4f47@akair \
--to=andreas@kemnade.info \
--cc=aaro.koskinen@iki.fi \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).