[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD++jLnVR1CbW9LCW3YPeytidWcjWEUbAAUD0z7LBS83x3ik3w@mail.gmail.com>
Date: Wed, 21 Jan 2026 13:09:57 +0100
From: Linus Walleij <linusw@...nel.org>
To: Bartosz Golaszewski <bartosz.golaszewski@....qualcomm.com>
Cc: Bartosz Golaszewski <brgl@...nel.org>, Srinivas Kandagatla <srini@...nel.org>, linux-gpio@...r.kernel.org,
linux-kernel@...r.kernel.org, Mohammad Rafi Shaik <mohs@....qualcomm.com>,
Ravi Hothi <raviravi@....qualcomm.com>
Subject: Re: [PATCH] gpio: shared: propagate configuration to pinctrl
On Tue, Jan 20, 2026 at 4:49 PM Bartosz Golaszewski
<bartosz.golaszewski@....qualcomm.com> wrote:
> Just toggling the descriptor's "requested" flag is not enough. We need
> to properly request it in order to potentially propagate any
> configuration to pinctrl via the .request() callback.
>
> We must not take the reference to the device at this point (the device
> is not ready but we're also requesting the device's own descriptor) so
> make the _commit() variants of request and free functions available to
> GPIO core in order to use them instead of their regular counterparts.
>
> This fixes an audio issue reported on one of the Qualcomm platforms.
>
> Fixes: a060b8c511ab ("gpiolib: implement low-level, shared GPIO support")
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@....qualcomm.com>
I don't quite understand all semantics but I guess it works
like this: gpiod_request_commit() is only called once, during
proxy device creation.
If I understand it correct:
Reviewed-by: Linus Walleij <linusw@...nel.org>
Yours,
Linus Walleij
Powered by blists - more mailing lists