From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: sashiko-reviews@lists.linux.dev
Cc: imx@lists.linux.dev, conor+dt@kernel.org,
devicetree@vger.kernel.org, robh@kernel.org, Frank.Li@kernel.org
Subject: Re: [PATCH 1/2] ARM: dts: mba6ulx: Add Ethernet PHY interrupt support
Date: Thu, 13 Aug 2026 15:28:06 +0200 [thread overview]
Message-ID: <6338721.44csPzL39Z@steina-w> (raw)
In-Reply-To: <20260813125131.A76481F000E9@smtp.kernel.org>
Am Donnerstag, 13. August 2026, 14:51:31 CEST schrieb sashiko-bot@kernel.org:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] Leftover `gpio-hog` nodes (`enet1_int-hog` and `enet2_int-hog`) for Ethernet PHY interrupt pins double-book GPIO resources.
> --
>
> --- Patch [1]: [PATCH 1/2] ARM: dts: mba6ulx: Add Ethernet PHY interrupt support ---
> commit b452753cee9dad50d404387319c21ed7231c45d2
> Author: Alexander Stein <alexander.stein@ew.tq-group.com>
>
> ARM: dts: mba6ulx: Add Ethernet PHY interrupt support
>
> This commit adds interrupt-parent and interrupts properties to the ethphy0
> and ethphy1 nodes in the device tree. It configures the Ethernet PHYs to
> use level-low interrupts provided by the GPIO expander.
>
> > diff --git a/arch/arm/boot/dts/nxp/imx/mba6ulx.dtsi b/arch/arm/boot/dts/nxp/imx/mba6ulx.dtsi
> > --- a/arch/arm/boot/dts/nxp/imx/mba6ulx.dtsi
> > +++ b/arch/arm/boot/dts/nxp/imx/mba6ulx.dtsi
> > @@ -214,6 +214,8 @@ ethphy0: ethernet-phy@0 {
> > clocks = <&clks IMX6UL_CLK_ENET_REF>;
> > reg = <0>;
> > max-speed = <100>;
> > + interrupt-parent = <&expander_in0>;
> > + interrupts = <6 IRQ_TYPE_LEVEL_LOW>;
>
> [Severity: Medium]
> Will this conflict with the existing enet1_int-hog in the expander_in0 node?
>
> Further down in this file, expander_in0 still defines these pins as
> gpio-hogs:
>
> enet1_int-hog {
> gpio-hog;
> gpios = <6 0>;
> input;
> };
>
> enet2_int-hog {
> gpio-hog;
> gpios = <7 0>;
> input;
> };
>
> Does leaving these redundant gpio-hog nodes in place cause the device tree
> to claim the same hardware resource twice? This might result in a resource
> ownership conflict between the GPIO and IRQ subsystems, potentially causing
> the IRQ request to fail and fall back to polling.
Because drivers/gpio/gpio-pca953x.c does use GPIOCHIP_IRQ_RESOURCE_HELPERS
these hogs are actually redundant. Will remove in v2.
Best regards
Alexander
> > };
> >
> > ethphy1: ethernet-phy@1 {
> > compatible = "ethernet-phy-ieee802.3-c22";
> > clocks = <&clks IMX6UL_CLK_ENET2_REF_125M>;
> > reg = <1>;
> > max-speed = <100>;
> > + interrupt-parent = <&expander_in0>;
> > + interrupts = <7 IRQ_TYPE_LEVEL_LOW>;
> > };
> > };
> > };
>
>
--
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/
next prev parent reply other threads:[~2026-08-13 13:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 12:12 [PATCH 0/2] TQMa6UL[L]x[L] DT improvements Alexander Stein
2026-08-13 12:12 ` [PATCH 1/2] ARM: dts: mba6ulx: Add Ethernet PHY interrupt support Alexander Stein
2026-08-13 12:51 ` sashiko-bot
2026-08-13 13:28 ` Alexander Stein [this message]
2026-08-13 12:12 ` [PATCH 2/2] ARM: dts: mba6ulx: Add USB hub node Alexander Stein
2026-08-13 12:52 ` sashiko-bot
2026-08-13 14:00 ` Alexander Stein
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=6338721.44csPzL39Z@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=Frank.Li@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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