Re: [PATCH] spi: cs42l43: Workaround for wrong speaker ID on Dell XPS 13 DX13260

[Richard Fitzgerald]

On 25/9/26 15:51, Mark Brown wrote:
> On Fri, Sep 25, 2026 at 02:14:34PM +0100, Richard Fitzgerald wrote:
> > On 20/9/26 16:14, Mark Brown wrote:
>
> > > Could we see an -EBUSY if there's something else using another GPIO from
> > > the same provider?
>
> > I'm not sure what you mean by "another GPIO from the same provider".
> > If you mean can the codec driver also try to read the same GPIOs:
>
> I mean we're looping over all the GPIOs from the provider, what if
> something else already requested one of the others?

This is only done for ACPI. We're looping over all the pins in the
consumer's GPIO request.

In DT the "x-gpios" property points at the GPIO provider.

In ACPI the "x-gpios" property is a Linux-specific compatibility fudge
that points to the consumer's *real* ACPI-syntax GPIO request.

Take a look at Documentation/firmware-guide/acpi/gpio-properties.rst

GpioIo() is the ACPI way to request GPIOs. The numbers inside the brace
list are the pin numbers being requested from the provider. The loop
is walking through that list trying to get each requested pin.