From: Jonas Jelonek <jelonek.jonas@gmail.com>
To: Peter Rosin <peda@axentia.se>, Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Thomas Richard <thomas.richard@bootlin.com>
Subject: Re: [PATCH v4 2/2] gpio: add gpio-line-mux driver
Date: Wed, 5 Nov 2025 15:37:24 +0100 [thread overview]
Message-ID: <f589ef1b-4347-4771-802f-992dd0928bc3@gmail.com> (raw)
In-Reply-To: <74603667-c77a-e791-d692-34d0201e5968@axentia.se>
Hi,
On 05.11.25 15:19, Peter Rosin wrote:
> Hi!
>
> 2025-11-05 at 14:24, Bartosz Golaszewski wrote:
>> Yes, "muxed-gpio" is good. I can change it myself when applying.
>>
>> Bartosz
> Isn't that the name in the device tree?
>
> Is
>
> muxed-gpio-gpios = <&gpio0 2 GPIO_ACTIVE_HIGH>;
This would be quite odd and not what I had in mind when I suggested this.
But I probably didn't express myself good enough.
> really satisfactory? Can you really make that change as you apply
> w/o a re-review of the binding?
>
> Or, are we talking about
>
> glm->shared_gpio = devm_gpiod_get(dev, "muxed", GPIOD_ASIS);
>
> and
>
> muxed-gpios = <&gpio0 2 GPIO_ACTIVE_HIGH>;
>
> ?
I'd be fine with this, but as you mentioned, it needs a re-review of the bindings.
If it's just about the label being used upon GPIO request, I might switch to
devm_fwnode_gpiod_get_index to explicitly set a different label and keep
"shared" in the bindings and device tree property?
>
> Cheers,
> Peter
Best,
Jonas
next prev parent reply other threads:[~2025-11-05 14:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 10:36 [PATCH v4 0/2] add gpio-line-mux Jonas Jelonek
2025-11-05 10:36 ` [PATCH v4 1/2] dt-bindings: gpio: add gpio-line-mux controller Jonas Jelonek
2025-11-05 10:36 ` [PATCH v4 2/2] gpio: add gpio-line-mux driver Jonas Jelonek
2025-11-05 13:15 ` Bartosz Golaszewski
2025-11-05 13:23 ` Jonas Jelonek
2025-11-05 13:24 ` Bartosz Golaszewski
2025-11-05 14:19 ` Peter Rosin
2025-11-05 14:37 ` Jonas Jelonek [this message]
2025-11-05 15:37 ` Bartosz Golaszewski
2025-11-05 15:49 ` Jonas Jelonek
2025-11-05 13:28 ` Jonas Jelonek
2025-11-05 13:26 ` Thomas Richard
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=f589ef1b-4347-4771-802f-992dd0928bc3@gmail.com \
--to=jelonek.jonas@gmail.com \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=robh@kernel.org \
--cc=thomas.richard@bootlin.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).