Re: [PATCH RFT/RFC] mfd: cs42l43: setup true links with software nodes

From: Bartosz Golaszewski

Date: Wed Nov 19 2025 - 05:50:22 EST


On Wed, Nov 19, 2025 at 11:47 AM Charles Keepax
<ckeepax@xxxxxxxxxxxxxxxxxxxxx> wrote:
>
> On Wed, Nov 19, 2025 at 11:38:35AM +0100, Bartosz Golaszewski wrote:
> > On Wed, Nov 19, 2025 at 10:58 AM Charles Keepax
> > <ckeepax@xxxxxxxxxxxxxxxxxxxxx> wrote:
> > >
> > > > > > Hi Charles!
> > > > > >
> > > > > > Please give this a try. It's only build-tested so far. I hope I
> > > > > > understood correctly that it's the SPI driver that needs the "cs" GPIO
> > > > > > from the pinctrl.
> > > > >
> > > > > Unfortunately it fails with an -EBUSY on adding the MFD children.
> > > > > I will investigate a little more and report back.
> > > >
> > > > Does it fail in device_add_software_node() in MFD core? Is it possible
> > > > that the device already has a software node for some reason?
> > >
> > > Yeah it seems there is already a software node, although somewhat
> > > at a loss as to why, the only ones we add are inside the SPI
> > > driver. I will poke further and see if I can find out how it
> > > acquires that node.
> > >
> >
> > Let me know if you figure it out, I'll submit a v2 that doesn't drop
> > the undefined swnode.
>
> Cool, thanks for all your help here. Might take me a couple hours
> but I will get to the bottom of the EBUSY thing, and report back.
>

Sure. Could you just post the stack trace down to where the EBUSY is
returned in drivers/base/swnode.c? I'd like to analyze the logic
myself too if that's not too much work for you.

Bart