[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ce3f0f1a-9cb3-4721-9774-0b73f461a6e9@bootlin.com>
Date: Tue, 28 Oct 2025 11:22:28 +0100
From: Thomas Richard <thomas.richard@...tlin.com>
To: Peter Rosin <peda@...ntia.se>, Jonas Jelonek <jelonek.jonas@...il.com>,
Linus Walleij <linus.walleij@...aro.org>, Bartosz Golaszewski
<brgl@...ev.pl>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Geert Uytterhoeven <geert+renesas@...der.be>
Cc: linux-gpio@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/2] gpio: add gpio-line-mux driver
Hi Peter,
On 10/28/25 11:09 AM, Peter Rosin wrote:
> Hi!
>
> 2025-10-28 at 10:45, Thomas Richard wrote:
>> On 10/27/25 12:17 AM, Jonas Jelonek wrote:
>>> + ret = mux_control_select(glm->mux, glm->gpio_mux_states[offset]);
>>> + if (ret < 0)
>>> + return ret;
>>> +
>>> + ret = gpiod_get_raw_value_cansleep(glm->shared_gpio);
>>
>> Why ignoring ACTIVE_LOW status ?
>> And cansleep depends on your shared_gpio line, maybe it is not the case.
>>
>>> + mux_control_deselect(glm->mux);
>
> *snip*
>
>>> + glm->gc.can_sleep = true;
>>
>> depends on your shared_gpio line.
>
> Does it? In this case, the gpio will always need to be able to
> sleep, since mux_control_select() may sleep. Or, what am I
> missing?
Oh yes you're right, I forgot the mux part.
Best Regards,
Thomas
Powered by blists - more mailing lists