From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: David Rhodes <david.rhodes@cirrus.com>,
Richard Fitzgerald <rf@opensource.cirrus.com>,
Lee Jones <lee@kernel.org>, Mark Brown <broonie@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Linus Walleij <linus.walleij@linaro.org>,
Maciej Strozek <mstrozek@opensource.cirrus.com>,
Andy Shevchenko <andy@kernel.org>,
linux-sound@vger.kernel.org, patches@opensource.cirrus.com,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH RFT/RFC] mfd: cs42l43: setup true links with software nodes
Date: Wed, 19 Nov 2025 10:47:51 +0000 [thread overview]
Message-ID: <aR2gVzKhfN38MHAR@opensource.cirrus.com> (raw)
In-Reply-To: <CAMRc=MdFDAmqcJ3PMsTbeZUb9imM+fzHzQ_9mQ1T=syDoCcQJw@mail.gmail.com>
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@opensource.cirrus.com> 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.
Thanks,
Charles
next prev parent reply other threads:[~2025-11-19 10:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 9:10 [PATCH RFT/RFC] mfd: cs42l43: setup true links with software nodes Bartosz Golaszewski
2025-11-19 9:30 ` Charles Keepax
2025-11-19 9:35 ` Andy Shevchenko
2025-11-19 9:40 ` Bartosz Golaszewski
2025-11-19 9:57 ` Charles Keepax
2025-11-19 10:20 ` Bartosz Golaszewski
2025-11-19 10:38 ` Bartosz Golaszewski
2025-11-19 10:47 ` Charles Keepax [this message]
2025-11-19 10:50 ` Bartosz Golaszewski
2025-11-19 10:58 ` Andy Shevchenko
2025-11-19 11:06 ` Bartosz Golaszewski
2025-11-19 11:24 ` Charles Keepax
2025-11-19 11:53 ` Andy Shevchenko
2025-11-19 12:08 ` Bartosz Golaszewski
2025-11-19 11:58 ` Bartosz Golaszewski
2025-11-19 12:53 ` Charles Keepax
2025-11-19 13:07 ` Bartosz Golaszewski
2025-11-19 13:26 ` Charles Keepax
2025-11-19 13:34 ` Bartosz Golaszewski
2025-11-19 14:11 ` Andy Shevchenko
2025-11-19 14:15 ` Bartosz Golaszewski
2025-11-19 14:23 ` Andy Shevchenko
2025-11-19 14:30 ` Bartosz Golaszewski
2025-11-19 20:38 ` Andy Shevchenko
2025-11-20 9:12 ` Bartosz Golaszewski
2025-11-20 9:56 ` Andy Shevchenko
2025-11-20 12:33 ` Bartosz Golaszewski
2025-11-19 14:09 ` Bartosz Golaszewski
2025-11-19 14:45 ` Bartosz Golaszewski
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=aR2gVzKhfN38MHAR@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=david.rhodes@cirrus.com \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mstrozek@opensource.cirrus.com \
--cc=p.zabel@pengutronix.de \
--cc=patches@opensource.cirrus.com \
--cc=rf@opensource.cirrus.com \
/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