From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: broonie@kernel.org, brgl@bgdev.pl, linus.walleij@linaro.org,
andy@kernel.org, p.zabel@pengutronix.de,
linux-gpio@vger.kernel.org, linux-spi@vger.kernel.org,
bartosz.golaszewski@linaro.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH] spi: cs42l43: Use actual ACPI firmware node for chip selects
Date: Wed, 19 Nov 2025 17:04:07 +0000 [thread overview]
Message-ID: <aR34h1H+isZQLEdk@opensource.cirrus.com> (raw)
In-Reply-To: <CAHp75VcjhdBXps+VmPNNUucA4LQwiZnReDMbQVpxHROcVsMurw@mail.gmail.com>
On Wed, Nov 19, 2025 at 06:49:57PM +0200, Andy Shevchenko wrote:
> On Wed, Nov 19, 2025 at 6:40 PM Charles Keepax
> <ckeepax@opensource.cirrus.com> wrote:
> >
> > On some systems the cs42l43 has amplifiers attached to its SPI
> > controller that are not properly defined in ACPI. Currently software
> > nodes are added to support this case, however, the chip selects
> > for these devices are specified using a bit of a hack. A software
> > node is added with the same name as the pinctrl driver, as the look
> > up was name based this caused the GPIO looks to return the pinctrl
> > driver even though the swnode is not associated with the pinctrl
> > driver. This was necessary as the swnodes did not support directly
> > linking to real firmware nodes.
> >
> > Since commit e5d527be7e69 ("gpio: swnode: don't use the
> > swnode's name as the key for GPIO lookup") changed the lookup to
> > be fwnode based this hack will no longer find the pinctrl driver,
> > resulting in the driver not probing. But other patches also add support
> > for linking a swnode to a real fwnode node [1]. As such switch over to
> > just passing the real fwnode for the pinctrl property to avoid any
> > issues.
>
> > [1] https://lore.kernel.org/linux-gpio/20251106-reset-gpios-swnodes-v6-0-69aa852de9e4@linaro.org/
> >
>
> This can be
>
> Link: ... [1]
>
> actually.
Thanks will fixup for v2.
> > Signed-off-by: Charles Keepax <ckeepax@opensource.cirrus.com>
> > ---
> >
> > Ok here is what I would propose to fix this one, IMPORTANT NOTE: this
> > does depend on the first four patches of the linked chain which I don't
> > think are merged yet. But I would argue if we are removing the name
> > based look up, we should add support for fwnodes at the same time.
>
> You mean it has functional dependency and not a compile-time one?
Apologies that wasn't clear, both.
> > + args[0].fwnode = fwnode;
>
> You can assign entries directly here as
>
> args = devm_kmalloc_array(...);
> ...
> args[0] = SOFTWARE_NODE_REFERENCE(...);
> args[1] = SOFTWARE_NODE_REFERENCE(&swnode_gpio_undefined),
Yes thank you I will fix that up for v2 as well, I was a little
rushing this one out.
Thanks,
Charles
next prev parent reply other threads:[~2025-11-19 17:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 16:40 [PATCH] spi: cs42l43: Use actual ACPI firmware node for chip selects Charles Keepax
2025-11-19 16:45 ` Charles Keepax
2025-11-19 16:51 ` Andy Shevchenko
2025-11-19 16:49 ` Andy Shevchenko
2025-11-19 17:04 ` Charles Keepax [this message]
2025-11-20 9:23 ` kernel test robot
2025-11-20 9:29 ` Bartosz Golaszewski
2025-11-20 10:06 ` Charles Keepax
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=aR34h1H+isZQLEdk@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=patches@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;
as well as URLs for NNTP newsgroup(s).