From: Srinivas Kandagatla <srini@kernel.org>
To: Andrea Tomassetti <andrea.tomassetti@sipearl.com>, linusw@kernel.org
Cc: johan+linaro@kernel.org, krzk@kernel.org,
linux-kernel@vger.kernel.org, peda@axentia.se, srini@kernel.org
Subject: Re: [PATCH v2] mux: gpio-mux: add support for 4:1 2-channels mux
Date: Fri, 19 Jun 2026 18:23:37 +0100 [thread overview]
Message-ID: <87032e28-9527-4513-a5ef-38afe0006480@kernel.org> (raw)
In-Reply-To: <20260506123350.310564-1-andrea.tomassetti@sipearl.com>
"mux: gpio-mux: add support for multiple mux controls" would be more
reflective of what is done in the patch.
On 5/6/26 1:33 PM, Andrea Tomassetti wrote:
> Some gpio multiplexers, like TMUX1209, offer differential 4:1
> or dual 4:1 single-ended channels. No binding changes are needed
> because the DT binding already supports #mux-control-cells
> with values 0 and 1. So, similarly to what was already done by the
> adg792a driver, the gpio-mux driver has to take into account
I guess adg792a does not have same issue(described below) as gpio mux
> the #mux-control-cells property and allocate as many controllers as
> advised by it.>
drivers/mux/gpio.c | 24 +++++++++++++++++++-----
> 1 file changed, 19 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/mux/gpio.c b/drivers/mux/gpio.c
> index 4cc3202c58f3..ab3ed5247d2c 100644
> --- a/drivers/mux/gpio.c
> +++ b/drivers/mux/gpio.c
> @@ -52,12 +52,23 @@ static int mux_gpio_probe(struct platform_device *pdev)
> int pins;
> s32 idle_state;
> int ret;
> + u32 cells;
> + int i;
>
> pins = gpiod_count(dev, "mux");
> if (pins < 0)
> return pins;
>
> - mux_chip = devm_mux_chip_alloc(dev, 1, sizeof(*mux_gpio));
> + ret = device_property_read_u32(dev, "#mux-control-cells", &cells);
> + if (ret < 0)
> + cells = 0;
> +
> + if (cells >= 2) {
This code snippet is duplicated once again, may its time for this to go
to as helper function, either in core or somewhere common.
> + dev_err(dev, "invalid control-cells %u, must be 0 or 1\n", cells);
mux-control-cells would give useful message to user rather than just
control-cells.
> + return -EINVAL;
> + }
> +
> + mux_chip = devm_mux_chip_alloc(dev, cells + 1, sizeof(*mux_gpio));
We are now allocating n mux_controls, however mux_gpio_set is not
protected against multiple controllers accessing the same gpio resource.
> if (IS_ERR(mux_chip))
> return PTR_ERR(mux_chip);
>
> @@ -69,7 +80,9 @@ static int mux_gpio_probe(struct platform_device *pdev)
> return dev_err_probe(dev, PTR_ERR(mux_gpio->gpios),
> "failed to get gpios\n");
> WARN_ON(pins != mux_gpio->gpios->ndescs);
> - mux_chip->mux->states = BIT(pins);
> +
> + for (i = 0; i < mux_chip->controllers; ++i)
> + mux_chip->mux[i].states = BIT(pins);
>
> ret = device_property_read_u32(dev, "idle-state", (u32 *)&idle_state);
> if (ret >= 0 && idle_state != MUX_IDLE_AS_IS) {
> @@ -78,7 +91,8 @@ static int mux_gpio_probe(struct platform_device *pdev)
> return -EINVAL;
> }
>
> - mux_chip->mux->idle_state = idle_state;
> + for (i = 0; i < mux_chip->controllers; ++i)
> + mux_chip->mux[i].idle_state = idle_state;
> }
>.
next prev parent reply other threads:[~2026-06-19 17:23 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 14:11 [PATCH RESEND] " Andrea Tomassetti
2026-05-05 8:23 ` Linus Walleij
2026-05-05 15:20 ` Andrea Tomassetti
2026-05-06 7:58 ` Linus Walleij
2026-05-06 12:33 ` [PATCH v2] " Andrea Tomassetti
2026-06-03 11:43 ` Andrea Tomassetti
2026-06-03 14:00 ` Krzysztof Kozlowski
2026-06-08 22:54 ` Linus Walleij
2026-06-17 13:09 ` Tommaso Merciai
2026-06-18 13:04 ` Linus Walleij
2026-06-18 13:27 ` Tommaso Merciai
2026-06-19 3:51 ` Krzysztof Kozlowski
2026-06-23 16:44 ` Tommaso Merciai
2026-06-24 8:59 ` Geert Uytterhoeven
2026-06-24 9:59 ` Krzysztof Kozlowski
2026-06-24 9:55 ` Krzysztof Kozlowski
2026-06-24 22:03 ` Linus Walleij
2026-06-24 22:11 ` Linus Walleij
2026-06-25 9:19 ` Nuno Sá
2026-06-29 19:27 ` Linus Walleij
2026-07-03 7:32 ` Michael Hennerich
2026-07-03 10:02 ` Miclaus, Antoniu
2026-07-03 13:19 ` Alvin Šipraga
2026-07-03 13:45 ` Lad, Prabhakar
2026-06-19 17:23 ` Srinivas Kandagatla [this message]
2026-06-30 15:08 ` Andrea Tomassetti
2026-07-03 8:10 ` Srinivas Kandagatla
2026-07-08 14:08 ` Peter Rosin
2026-06-25 9:32 Lad, Prabhakar
2026-06-25 9:43 ` Krzysztof Kozlowski
2026-06-25 9:49 ` Greg Kroah-Hartman
2026-06-25 9:59 ` Lad, Prabhakar
2026-06-29 19:24 ` Linus Walleij
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=87032e28-9527-4513-a5ef-38afe0006480@kernel.org \
--to=srini@kernel.org \
--cc=andrea.tomassetti@sipearl.com \
--cc=johan+linaro@kernel.org \
--cc=krzk@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
/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
Powered by JetHome