From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Charles Keepax <ckeepax@opensource.cirrus.com>,
David Rhodes <david.rhodes@cirrus.com>,
Richard Fitzgerald <rf@opensource.cirrus.com>,
Lee Jones <lee@kernel.org>, Mark Brown <broonie@kernel.org>,
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 12:58:50 +0200 [thread overview]
Message-ID: <aR2i6lNNWEbQk0fx@smile.fi.intel.com> (raw)
In-Reply-To: <CAMRc=Mck8MiAm_nxY_L6Zw4cH-vYf24zSkPp=bhnUw68Q6FV=g@mail.gmail.com>
On Wed, Nov 19, 2025 at 11:50:09AM +0100, Bartosz Golaszewski wrote:
> On Wed, Nov 19, 2025 at 11:47 AM Charles Keepax
> <ckeepax@opensource.cirrus.com> wrote:
> > On Wed, Nov 19, 2025 at 11:38:35AM +0100, Bartosz Golaszewski wrote:
...
> > 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.
FWIW, there is also an interesting debug technique. Put in your driver where
you get this error code something like this (after all #include directives):
#undef EBUSY
#define EBUSY __LINE__
And then you get some error code which is line number in some C file. You can
narrow down grepping of the EBUSY in the suspected files and get the one.
git grep -n -w EBUSY -- ...files of interest...
Hope this saves some minutes for you.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-11-19 10:58 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
2025-11-19 10:50 ` Bartosz Golaszewski
2025-11-19 10:58 ` Andy Shevchenko [this message]
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=aR2i6lNNWEbQk0fx@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andy@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--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