[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251120195941.qumgpiwvkxvfjkug@skbuf>
Date: Thu, 20 Nov 2025 21:59:41 +0200
From: Vladimir Oltean <vladimir.oltean@....com>
To: Lee Jones <lee@...nel.org>
Cc: netdev@...r.kernel.org, Andrew Lunn <andrew@...n.ch>,
Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 08/15] net: dsa: sja1105: transition OF-based
MDIO drivers to standalone
On Thu, Nov 20, 2025 at 04:36:03PM +0000, Lee Jones wrote:
> The canonical answer goes 3 ways: If you want to use the MFD API, move
> the handling to drivers/mfd.
Wait, so now it's negotiable? What about "this device is not an MFD"
from the other patch? Move it to another folder and suddenly it's an MFD?
https://lore.kernel.org/netdev/20251120153622.p6sy77coa3de6srw@skbuf/
> If it's possible, use one of the predetermined helpers like
> of_platform_populate() (and I think we authored another one that
> worked around some of its issues, but I forget where we put it!).
yay...
I don't need the code necessarily, just the overall idea if you remember it.
> Or if all else fails, you have to register the device the old
> fashioned way with the platform_device_*() API.
Do you realize that by this, you are inviting me to waste time until the
next reviewer rightfully asks, why didn't you use MFD, then I'll point
them towards this discussion, but you didn't really answer?
Powered by blists - more mailing lists