[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260115093538.o5ghqb6j6dzledyw@skbuf>
Date: Thu, 15 Jan 2026 11:35:38 +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 07/15] mfd: core: add ability for cells to probe
on a custom parent OF node
Hi Lee,
On Fri, Jan 09, 2026 at 02:14:32PM +0200, Vladimir Oltean wrote:
> > When I've thought about replacing the existing occurrences of the MFD
> > API being used outside of drivers/mfd, I have often thought of a
> > platform_add_device_simple() call which I believe would do what most
> > people of these use-cases actually want.
>
> Would this platform_add_device_simple() share or duplicate code with
> mfd_add_devices()? Why not just liberalize mfd_add_devices() (the
> simplest solution)?
Sorry to nag you, but I would like to have a clear image of which way
this patch set needs to be heading for v2. My understanding is that
you're pushing for platform_device_add() while not completely rejecting
that MFD could be the correct model for this switch's sub-devices.
Powered by blists - more mailing lists