On Fri, Jan 16, 2026 at 08:40:21AM +0000, Lee Jones wrote:

On Thu, 15 Jan 2026, Vladimir Oltean wrote:

quoted

On Thu, Jan 15, 2026 at 04:14:07PM +0000, Lee Jones wrote:

quoted

quoted

quoted

My plan, when and if I manage to find a few spare cycles, is to remove
MFD use from outside drivers/mfd.  That's been my rule since forever.
Having this in place ensures that the other rules are kept and (mild)
chaos doesn't ensue.  The MFD API is trivial to abuse.  You wouldn't
believe some of things I've seen over the years.  Each value I have is
there for a historical reason.

If you're also of the opinion that MFD is a Linux-specific
implementation detail and a figment of our imagination as developers,
then I certainly don't understand why Documentation/devicetree/bindings/mfd/
exists for this separate device class that is MFD, and why you don't
liberalize access to mfd_add_devices() instead.

The first point is a good one.  It mostly exists for historical
reasons and for want of a better place to locate the documentation.

I've explained why liberalising the mfd_*() API is a bad idea.  "Clever"
developers like to do some pretty crazy stuff involving the use of
multiple device registration APIs simultaneously.  I've also seen some
bonkers methods of dynamically populating MFD cells [*ahem* Patch 8
=;-)] and various other things.  Keeping the API in-house allows me to
keep things simple, easily readable and maintainable.

The only thing that's crazy to me is how the MFD documentation (+ my
intuition as engineer to fill in the gaps where the documentation was
lacking, aka in a lot of places) could be so far off from what you lay
out as your maintainer expectations here.

MFD has documentation?  =;-)

/me `find . | grep -i mfd`s

Okay, the only "MFD documentation" I can find is:

  Documentation/devicetree/bindings/mfd/mfd.txt

Exactly my point!

The first paragraph reflects the point I've been trying to make:

 "These devices comprise a nexus for HETEROGENEOUS hardware blocks
  containing more than one non-unique yet VARYING HARDWARE FUNCTIONALITY.

2 MDIO controllers are homogeneous to each other and are not varying.

I get the impression you didn't look at patch 14, where I also added the
ethernet-pcs blocks to MFD children.

How is the documentation and what I say "so far off"?

Well, it's far off because I got the genuine impression that I'm making
legitimate use of the MFD API.

Okay, so these are the MDIO bus controllers - that's clear now, thank you.

I was confused by the t1 and tx parts.  Are these different types of
MDIO controllers or are they the same, but vary only in support / role?

But again, if these are "both MDIO controllers", then they are _same_.

Their register map (i.e. way of accessing the underlying MDIO devices,
aka internal PHYs) is different. They have different drivers, one is
added by patch 3 and the other by patch 4.
Here is the link to the entire set:
https://lore.kernel.org/netdev/20251118190530.580267-1-vladimir.oltean@nxp.com/ (local)

quoted

quoted

quoted

Let me reframe what I think you are saying.

If the aesthetics of the dt-bindings of my SPI device were like this (1):

(...)

then you wouldn't have had any issue about this not being MFD, correct?

Right.  This is more in-line with what I would expect to see.

quoted

I think this is an important base fact to establish.
It looks fairly similar to Colin Foster's bindings for VSC7512, save for
the fact that the sub-devices are slightly more varied (which is inconsequential,
as Andrew seems to agree).

However, the same physical reality is being described in these _actual_
dt-bindings (2):

(...)

Your issue is that, when looking at these real dt-bindings,
superficially the MDIO buses don't "look" like MFD.

To which, yes, I have no objection, they don't look like MFD because
they were written as additions on top of the DSA schema structure, not
according to the MFD schema.

In reality it doesn't matter much where the MDIO bus nodes are (they
could have been under "regs" as well, or under "mfd@0"), because DSA
ports get references to their children using phandles. It's just that
they are _already_ where they are, and moving them would be an avoidable
breaking change.

Right.  I think this is highly related to one of my previous comments.

I can't find it right now, but it was to the tune of; if a single driver
provides lots of functionality that _could_ be split-up, spread across
multiple different subsystems which all enumerate as completely
separate device-drivers, but isn't, then it still shouldn't meet the
criteria.

Any arbitrary set of distinct functions can be grouped into a new
monolithic driver. Are you saying that grouping them together is fine,
but never split them back up, at least not using MFD? What's the logic?

No, the opposite I think?

I'm saying that when they are grouped into a monolithic driver, they do
not match the criteria of an MFD, but if the _varying_ functionality was
split-up and probed individually, they would.  Take this example:

# Bad
static struct mfd_cell cells[] = {
	MFD_CELL_NAME("abc-monolithic")
};

# Bad
static struct mfd_cell cells[] = {
	MFD_CELL_NAME("abc-function-a")
	MFD_CELL_NAME("abc-function-a")
};

# Good
static struct mfd_cell cells[] = {
	MFD_CELL_NAME("abc-function-a")
	MFD_CELL_NAME("abc-function-b")
};

At the moment, from what I see in front of me, you are the middle one.

I think you are missing patch 14.
Although for SJA1105R/S, I am indeed in the middle position (it has to
do with the multi-generational aspect I was telling you about).

quoted

quoted

quoted

Exactly. DSA drivers get more developed with new each new hardware
generation, and you wouldn't want to see an MFD driver + its bindings
"just in case" new sub-devices will appear, when currently the DSA
switch is the only component supported by Linux (and maybe its internal
MDIO bus).

If only one device is currently supported, then again, it doesn't meet
the criteria.  I've had a bunch of developers attempt to upstream
support for a single device and insist that more sub-devices are coming
which would make it an MFD, but that's not how it works.  Devices must
meet the criteria _now_.  So I usually ask them go take the time to get
at least one more device ready before attempting to upstream.

sja1105 is a multi-generational DSA driver. Gen 1 SJA1105E/T has 0
sub-devices, Gen 2 SJA1105R/S have 1 sub-device (XPCS) and Gen3 SJA1110
have 5+ sub-devices.

The driver was written for Gen 1, then was expanded for the later
generations as the silicon was released (multiple years in between these
events).

You are effectively saying:
- MAX77540 wouldn't have been accepted as MFD on its own, it was
  effectively carried in by MAX77541 support.
- A driver that doesn't have sufficiently varied subfunctions doesn't
  qualify as MFD.
- A monolithic driver whose subfunctions can be split up doesn't meet
  the MFD criteria.

If it "can", but isn't, then it doesn't, that's correct.

But if it _is_ split-up then it does.

quoted

So in your rule system, a multi-generational driver which evolves into
having multiple sub-devices has no chance of ever using MFD, unless it
is written after the evolution has stopped, and the old generations
become obsolete.

I'm really not.  I'm saying that if the driver were to be spit-up, then
it _would_ match the criteria and it would be free to use MFD to
register those split-up sub-devices.

I don't know what you meant to say, but I quote what you actually said,
and how I interpreted it:

"if a single driver provides lots of functionality that _could_ be
split-up, (...), but isn't [ split up ], then it still shouldn't meet
the criteria [ for using the MFD API ]."

quoted

Unless you're of the opinion that it's my fault for not predicting the
future and waiting until the SJA1110 came out in order to write an MFD
driver, I suggest you could reconsider your rules so that they're less
focused on your comfort as maintainer, at the expense of fairness and
coherency for other developers.

This isn't what I've said at all.

What I have said is that even though you've split this up, you have only
split it up into 2 homogeneous devices / controllers, which still does
not qualify.

If you have plans to split out another varying function, other than an
MDIO controller, then do so and you can then easily qualify.

Ok, so we're getting close, you just need to take a look at patch 14.

quoted

quoted

Is there any reason not to put mdio_cbt and mdio_cbt1 resources into the
device tree

That ship has sailed and there are device trees in circulation with
existing mdio_cbtx/mdio_cbt1 bindings.

quoted

or make them available somewhere else (e.g. driver.of_match_table.data)
and use of_platform_populate() instead of mfd_add_devices() (I can't
remember if we've suggested that before or not).

I never got of_platform_populate() to work for a pretty fundamental
reason, so I don't have enough information to know what you're on about
with making the mdio_cbtx/mdio_cbt1 resources available to it.

quoted

Right, I think we've discussed this enough.  I've made a decision.

If the of_platform_populate() solution doesn't work for you for some
reason (although I think it should),

Quote from the discussion on patch 8:

I did already explore of_platform_populate() on this thread which asked
for advice (to which you were also copied):
https://lore.kernel.org/lkml/20221222134844.lbzyx5hz7z5n763n@skbuf/ (local)

    It looks like of_platform_populate() would be an alternative option for
    this task, but that doesn't live up to the task either. It will assume
    that the addresses of the SoC children are in the CPU's address space
    (IORESOURCE_MEM), and attempt to translate them. It simply doesn't have
    the concept of IORESOURCE_REG. The MFD drivers which call
    of_platform_populate() (simple-mfd-i2c.c) simply don't have unit
    addresses for their children, and this is why address translation isn't
    a problem for them.

    In fact, this seems to be a rather large limitation of include/linux/of_address.h.
    Even something as simple as of_address_count() will end up trying to
    translate the address into the CPU memory space, so not even open-coding
    the resource creation in the SoC driver is as simple as it appears.

    Is there a better way than completely open-coding the parsing of the OF
    addresses when turning them into IORESOURCE_REG resources (or open-coding
    mfd_cells for each child)? Would there be a desire in creating a generic
    set of helpers which create platform devices with IORESOURCE_REG resources,
    based solely on OF addresses of children? What would be the correct
    scope for these helpers?

Does this all boil down that pesky empty 'mdio' "container"?

Why do you keep calling it empty?

Or even if it doesn't: if what you have is a truly valid DT, then why
not adapt drivers/of/platform.c to cater for your use-case?  Then you
could take your pick from whatever works better for you out of
of_platform_populate(), 'simple-bus' or even 'simple-mfd'.

I asked 3 years ago whether there's any interest in expanding
of_platform_populate() for IORESOURCE_REG and there wasn't any response.
It's a big task with overreaching side effects and you don't just pick
up on this on a Friday afternoon.

quoted

quoted

given the points you've put forward, I would be content for you to
house the child device registration (via mfd_add_devices) in
drivers/mfd if you so wish.

Thanks! But I don't know how this helps me :)

Since your offer involves changing dt-bindings in order to separate the
MFD parent from the DSA switch (currently the DSA driver probes on the
spi_device, clashing with the MFD parent which wants the same thing), I
will have to pass.

I haven't taken a look at the DT bindings in close enough detail to
provide a specific solution, but _perhaps_ it would be possible to match
the MFD driver to the existing compatible, then use the MFD driver to
register the current DSA driver.

The MFD driver and the DSA driver would compete for the same OF node.
And again, you'd still return to the problem of where to attach the DSA
switch's sub-devices in the device tree (currently to the "mdios" and
"regs" child nodes, which MFD doesn't support probing on, unless we
apply the mfd_cell.parent_of_node patch).

However, after this most recent exchange, I am even less confident that
using the MFD API to register only 2 MDIO controllers is the right thing
to do.

quoted

Not because I insist on being difficult, but because I know that when I
change dt-bindings, the old ones don't just disappear and will continue
to have to be supported, likely through a separate code path that would
also increase code complexity.

Right, they have to be backwardly compatible, I get that.

quoted

quoted

Although I still don't think modifying the core to ignore bespoke empty
"container" nodes is acceptable.  It looks like this was merged without
a proper DT review.  I'm surprised that this was accepted.

There was a debate when this was accepted, but we didn't come up with
anything better to fulfill the following constraints:
- As per mdio.yaml, the $nodename has to follow the pattern:
  '^mdio(-(bus|external))?(@.+|-([0-9]+))?$'
- There are two MDIO buses. So we have to choose the variant with a
  unit-address (both MDIO buses are for internal PHYs, so we can't call
  one "mdio" and the other "mdio-external").
- Nodes with a unit address can't be hierarchical neighbours with nodes
  with no unit address (concretely: "ethernet-ports" from
  Documentation/devicetree/bindings/net/ethernet-switch.yaml, the main
  schema that the DSA switch conforms to). This is because their parent
  either has #address-cells = <0>, or #address-cells = <1>. It can't
  simultaneously have two values.

Simply put, there is no good place to attach child nodes with unit
addresses to a DT node following the DSA (or the more general
ethernet-switch) schema. The "mdios" container node serves exactly that
adaptation purpose.

I am genuinely curious how you would have handled this better, so that I
also know better next time when I'm in a similar situation.

Especially since "mdios" is not the only container node with this issue.
The "regs" node proposed in patch 14 serves exactly the same purpose
(#address-cells adaptation), and needs the exact same ".parent_of_node = regs_node"
workaround in the mfd_cell.

Please correct me if I'm wrong, but from what I have gathered, all
you're trying to do here is probe a couple of child devices
(controllers, whatever) and you've chosen to use MFD for this purpose
because the other, more generic machinery that would normally _just
work_ for simple scenarios like this, do not because you are attempting
to support a non-standard DT.  Or at least one that isn't supported.

Sorry, what makes the DT non-standard?

With that in mind, some suggestions going forward in order of preference:

- Adapt the current auto-registering infrastructure to support your DT layout
  - of_platform_populate(), simple-bus, simple-mfd, etc
- Use fundamental / generic / flexible APIs that do not have specific rules
  - platform_*()
- Move the mfd_device_add() usage into drivers/mfd
  - Although after this exchange, this is now my least preferred option

I could explore other options, but I want to be prepared to answer other
maintainers' question "why didn't you use MFD?". There is no clear
answer to that, you are not providing answers that have taken all
evidence into account, so that is why I'm being extremely pushy, sorry.

Hope that helps.  Good luck with however you decide to proceed.

-- 
Lee Jones [李琼斯]