From: Krzysztof Kozlowski <krzk@kernel.org>
To: Antoniu Miclaus <antoniu.miclaus@analog.com>
Cc: Peter Rosin <peda@axentia.se>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Srinivas Kandagatla <srini@kernel.org>,
Johan Hovold <johan+linaro@kernel.org>,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
David Lechner <dlechner@baylibre.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/4] dt-bindings: mux: gpio-mux: add adi,adg2404 support
Date: Fri, 16 Jan 2026 09:34:22 +0100 [thread overview]
Message-ID: <1e65bcd0-54c1-41ff-8552-6ed5c56c1f70@kernel.org> (raw)
In-Reply-To: <20260116-invaluable-ambitious-piculet-dade13@quoll>
On 16/01/2026 09:29, Krzysztof Kozlowski wrote:
> On Thu, Jan 15, 2026 at 02:18:21PM +0200, Antoniu Miclaus wrote:
>> Add adi,adg2404 as a compatible string. The ADG2404 is a 4:1 analog
>> multiplexer that uses the enable-gpios feature.
>>
>> Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
>> ---
>> changes in v3:
>> * integrate with gpio-mux bindings instead of separate adi,adg2404.yaml
>> ---
>> .../devicetree/bindings/mux/gpio-mux.yaml | 19 ++++++++++++++++++-
>> 1 file changed, 18 insertions(+), 1 deletion(-)
>>
>> diff --git a/Documentation/devicetree/bindings/mux/gpio-mux.yaml b/Documentation/devicetree/bindings/mux/gpio-mux.yaml
>> index 199792d42323..f5866b9f46dd 100644
>> --- a/Documentation/devicetree/bindings/mux/gpio-mux.yaml
>> +++ b/Documentation/devicetree/bindings/mux/gpio-mux.yaml
>> @@ -19,7 +19,9 @@ description: |+
>>
>> properties:
>> compatible:
>> - const: gpio-mux
>> + enum:
>> + - gpio-mux
>> + - adi,adg2404
>
> I do not understand why this was placed in gpio-mux. You have a strictly
> defined hardware, with known muxes, not a flexible semi-software
> binding.
>
> Otherwise please explain: why do you have both 0 and 1 cells?
>
> This is supposed to be in its own binding.
After reading further patches - this patch does not make sense, but it
should not be its own binding. Rob at v2 gave you advice what should be
done.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-01-16 8:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 12:18 [PATCH v3 0/4] mux: gpio-mux: add enable GPIO support and ADG2404 Antoniu Miclaus
2026-01-15 12:18 ` [PATCH v3 1/4] dt-bindings: mux: gpio-mux: add enable-gpios support Antoniu Miclaus
2026-01-16 8:30 ` Krzysztof Kozlowski
2026-01-15 12:18 ` [PATCH v3 2/4] mux: gpio-mux: add support for enable GPIO Antoniu Miclaus
2026-01-15 12:18 ` [PATCH v3 3/4] dt-bindings: mux: gpio-mux: add adi,adg2404 support Antoniu Miclaus
2026-01-16 8:29 ` Krzysztof Kozlowski
2026-01-16 8:34 ` Krzysztof Kozlowski [this message]
2026-01-15 12:18 ` [PATCH v3 4/4] " Antoniu Miclaus
2026-01-16 8:32 ` Krzysztof Kozlowski
2026-01-16 8:34 ` Krzysztof Kozlowski
2026-01-16 9:48 ` Miclaus, Antoniu
2026-01-16 10:42 ` Krzysztof Kozlowski
2026-01-16 8:37 ` [PATCH v3 0/4] mux: gpio-mux: add enable GPIO support and ADG2404 Krzysztof Kozlowski
2026-01-16 9:00 ` Johan Hovold
2026-01-16 9:39 ` Miclaus, Antoniu
2026-01-16 10:31 ` Krzysztof Kozlowski
2026-01-16 15:26 ` Miclaus, Antoniu
2026-01-16 16:06 ` Krzysztof Kozlowski
2026-01-16 16:17 ` Miclaus, Antoniu
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=1e65bcd0-54c1-41ff-8552-6ed5c56c1f70@kernel.org \
--to=krzk@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=johan+linaro@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=robh@kernel.org \
--cc=srini@kernel.org \
/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
all inboxes | Powered by JetHome®