public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Daniel Scally <djrscally@gmail.com>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Danilo Krummrich <dakr@kernel.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	David Rhodes <david.rhodes@cirrus.com>,
	Richard Fitzgerald <rf@opensource.cirrus.com>,
	Mark Brown <broonie@kernel.org>,
	Maciej Strozek <mstrozek@opensource.cirrus.com>,
	Andy Shevchenko <andy@kernel.org>,
	Bartosz Golaszewski <brgl@kernel.org>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-acpi@vger.kernel.org, linux-sound@vger.kernel.org,
	patches@opensource.cirrus.com, linux-spi@vger.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
	stable+noautosel@kernel.org
Subject: Re: [PATCH v7 4/9] spi: cs42l43: Use actual ACPI firmware node for chip selects
Date: Mon, 24 Nov 2025 16:58:11 +0000	[thread overview]
Message-ID: <aSSOo4q0sLDHqe1h@opensource.cirrus.com> (raw)
In-Reply-To: <20251120-reset-gpios-swnodes-v7-4-a100493a0f4b@linaro.org>

On Thu, Nov 20, 2025 at 02:23:59PM +0100, Bartosz Golaszewski wrote:
> From: Charles Keepax <ckeepax@opensource.cirrus.com>
> 
> 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 hack. A software
> node is added with the same name as the pinctrl driver, as the
> look up was name based, this allowed the GPIO look up to return
> the pinctrl driver even though the swnode was not owned by it.
> 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. There is no pinctrl driver
> attached to the swnode itself. But other patches did add support
> for linking a swnode to a real fwnode node [1]. As such the hack
> is no longer needed, so switch over to just passing the real
> fwnode for the pinctrl property to avoid any issues.
> 
> Link: https://lore.kernel.org/linux-gpio/20251106-reset-gpios-swnodes-v6-0-69aa852de9e4@linaro.org/ [1]
> Fixes: 439fbc97502a ("spi: cs42l43: Add bridged cs35l56 amplifiers")
> Cc: stable+noautosel@kernel.org # Don't backport, previous approach works, fix relies on swnode changes

Just wanted to check what the thinking is on backports here. I
see we have marked this as do not backport. Which I think is
sensible the changes in the preceeding patches are a bit much for
a backport. However, the patch has caused the regression has gone
to a few stable branches (v6.17, v6.12):

commit e5d527be7e69 ("gpio: swnode: don't use the swnode's name as the key for GPIO lookup")

Are you guys ok if I send a revert for that patch to the stable
branches it has gone to? It doesn't actually fix any bugs on
those kernels, and we are starting to see issues coming in that I
think are related to this:

https://github.com/thesofproject/linux/issues/5599

Thanks,
Charles

  parent reply	other threads:[~2025-11-24 16:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-20 13:23 [PATCH v7 0/9] reset: rework reset-gpios handling Bartosz Golaszewski
2025-11-20 13:23 ` [PATCH v7 1/9] software node: read the reference args via the fwnode API Bartosz Golaszewski
2025-11-20 13:25   ` Charles Keepax
2025-11-20 13:26   ` Charles Keepax
2025-11-20 14:47   ` Andy Shevchenko
2025-11-20 13:23 ` [PATCH v7 2/9] software node: increase the reference of the swnode by its fwnode Bartosz Golaszewski
2025-11-20 13:26   ` Charles Keepax
2025-11-20 14:48   ` Andy Shevchenko
2025-11-20 13:23 ` [PATCH v7 3/9] software node: allow referencing firmware nodes Bartosz Golaszewski
2025-11-20 13:27   ` Charles Keepax
2025-11-20 13:23 ` [PATCH v7 4/9] spi: cs42l43: Use actual ACPI firmware node for chip selects Bartosz Golaszewski
2025-11-20 14:53   ` Andy Shevchenko
2025-11-20 15:40   ` Mark Brown
2025-11-24 16:58   ` Charles Keepax [this message]
2025-11-24 17:48     ` Bartosz Golaszewski
2025-11-20 13:24 ` [PATCH v7 5/9] gpio: swnode: allow referencing GPIO chips by firmware nodes Bartosz Golaszewski
2025-11-20 13:24 ` [PATCH v7 6/9] reset: order includes alphabetically in reset/core.c Bartosz Golaszewski
2025-11-20 13:24 ` [PATCH v7 7/9] reset: make the provider of reset-gpios the parent of the reset device Bartosz Golaszewski
2025-11-20 13:24 ` [PATCH v7 8/9] reset: gpio: convert the driver to using the auxiliary bus Bartosz Golaszewski
2025-11-20 13:24 ` [PATCH v7 9/9] reset: gpio: use software nodes to setup the GPIO lookup Bartosz Golaszewski
2025-11-20 15:06 ` [PATCH v7 0/9] reset: rework reset-gpios handling Andy Shevchenko
2025-11-20 15:29   ` Bartosz Golaszewski
2025-11-20 16:32 ` Philipp Zabel

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=aSSOo4q0sLDHqe1h@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=brgl@kernel.org \
    --cc=broonie@kernel.org \
    --cc=dakr@kernel.org \
    --cc=david.rhodes@cirrus.com \
    --cc=djrscally@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=krzk@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.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=rafael@kernel.org \
    --cc=rf@opensource.cirrus.com \
    --cc=sakari.ailus@linux.intel.com \
    --cc=stable+noautosel@kernel.org \
    /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