From: Sander Vanheule <sander@svanheule.net>
To: Krzysztof Kozlowski <krzk@kernel.org>,
kernel test robot <lkp@intel.com>, Lee Jones <lee@kernel.org>,
Pavel Machek <pavel@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Michael Walle <mwalle@kernel.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Mark Brown <broonie@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Randy Dunlap <rdunlap@infradead.org>
Cc: Paul Gazzillo <paul@pgazz.com>,
Necip Fazil Yildiran <fazilyildiran@gmail.com>,
oe-kbuild-all@lists.linux.dev, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org, netdev@vger.kernel.org,
Rob Herring <robh@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH v9 3/6] mfd: Add RTL8231 core device
Date: Fri, 26 Dec 2025 15:52:25 +0100 [thread overview]
Message-ID: <a844934b105136f576ab46a5779cf57ef0cc7bbb.camel@svanheule.net> (raw)
In-Reply-To: <a26a5397-7597-49f6-9e73-3eb853915166@kernel.org>
Hi Krzysztof,
On Fri, 2025-12-26 at 13:19 +0100, Krzysztof Kozlowski wrote:
> On 26/12/2025 12:59, Sander Vanheule wrote:
> > > kismet warnings: (new ones prefixed by >>)
> > > > > kismet: WARNING: unmet direct dependencies detected for MDIO_BUS when
> > > > > selected by REGMAP_MDIO
> > > WARNING: unmet direct dependencies detected for MDIO_BUS
> > > Depends on [n]: NETDEVICES [=n]
> > > Selected by [y]:
> > > - REGMAP_MDIO [=y]
> >
> > I'm a bit puzzled on how to solve this one. The issue detected here is that
> > my
> > driver (MFD_RTL8231) selects REGMAP_MDIO, which in turn selects MDIO_BUS.
> > The
> > latter is dependent on NETDEVICES, which is not selected in this test.
> > The kernel does not yet have any other consumers of REGMAP_MDIO, which is
> > probably the reason the dependency issue has gone undetected until now.
> >
> > REGMAP_MDIO is not a visible symbol, so it must be selected by drivers.
>
> Reminds me old problem, probably the same:
>
> https://lore.kernel.org/all/20250515140555.325601-2-krzysztof.kozlowski@linaro.org/
>
> https://lore.kernel.org/all/20250516141722.13772-1-afd@ti.com/
>
> Exactly the same MDIO here and there.
> > [...]
> Rather fix the same way Andrew did it. Or maybe his patch was not merged?
Andrew's patch was merged, that's the code I'm seeing now. I think by
placing the dependency under REGMAP_MDIO (or REGMAP_IRQ) instead of
REGMAP, it just made the circular dependency less visible.
Making PINCTRL_RTL8231 "depends on GPIOLIB", like the GPIO drivers, only
shortens the circular dependency loop:
error: recursive dependency detected!
symbol IRQ_DOMAIN is selected by MFD_CORE
symbol MFD_CORE is selected by MFD_RTL8231
symbol MFD_RTL8231 depends on MDIO_BUS
symbol MDIO_BUS is selected by PHYLIB
symbol PHYLIB is selected by ARC_EMAC_CORE
symbol ARC_EMAC_CORE is selected by EMAC_ROCKCHIP
symbol EMAC_ROCKCHIP depends on OF_IRQ
symbol OF_IRQ depends on IRQ_DOMAIN
Of these symbols, IRQ_DOMAIN and OF_IRQ are hidden symbols, so they must be
selected by another symbol to be used. As shown above, OF_IRQ *depends* on
IRQ_DOMAIN, which means some other symbol *must* select it for the dependency to
be satisfied, as IRQ_DOMAIN also cannot be selected directly by the user. OF_IRQ
also appears to be the only symbol in the kernel to depend on, rather than
select, IRQ_DOMAIN.
Turning the dependency of OF_IRQ on IRQ_DOMAIN around resolves the dependency
loop here, and ensures the hidden IRQ_DOMAIN symbol is selected whenever any
other symbol selects OF_IRQ.
The same reasoning was actually used in 2023 to suggest this change as well:
https://lore.kernel.org/lkml/20230213041535.12083-3-rdunlap@infradead.org/
I found some follow-up, but it didn't look like it actually got wrapped up:
https://lore.kernel.org/lkml/20230313023935.31037-1-rdunlap@infradead.org/
Randy, do you happen to recall if/why this stalled? Should we just try to invert
the dependency again if there is no pressing need for the "proper" clean-up?
Best,
Sander
next prev parent reply other threads:[~2025-12-26 14:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 17:51 [PATCH v9 0/6] RTL8231 GPIO expander support Sander Vanheule
2025-12-15 17:51 ` [PATCH v9 1/6] dt-bindings: leds: Binding for RTL8231 scan matrix Sander Vanheule
2025-12-15 17:51 ` [PATCH v9 2/6] dt-bindings: mfd: Binding for RTL8231 Sander Vanheule
2025-12-15 17:51 ` [PATCH v9 3/6] mfd: Add RTL8231 core device Sander Vanheule
2025-12-22 8:43 ` kernel test robot
2025-12-26 11:59 ` Sander Vanheule
2025-12-26 12:19 ` Krzysztof Kozlowski
2025-12-26 14:52 ` Sander Vanheule [this message]
2025-12-15 17:51 ` [PATCH v9 4/6] pinctrl: Add RTL8231 pin control and GPIO support Sander Vanheule
2025-12-18 9:15 ` Bartosz Golaszewski
2025-12-19 13:52 ` Sander Vanheule
2025-12-15 17:51 ` [PATCH v9 5/6] leds: Add support for RTL8231 LED scan matrix Sander Vanheule
2025-12-15 17:51 ` [PATCH v9 6/6] MAINTAINERS: Add RTL8231 MFD driver Sander Vanheule
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=a844934b105136f576ab46a5779cf57ef0cc7bbb.camel@svanheule.net \
--to=sander@svanheule.net \
--cc=andrew@lunn.ch \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=fazilyildiran@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lkp@intel.com \
--cc=mwalle@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=paul@pgazz.com \
--cc=pavel@kernel.org \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®