From: Krzysztof Kozlowski <krzk@kernel.org>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: Parth Pancholi <parth105105@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Parth Pancholi <parth.pancholi@toradex.com>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: usb: gpio-sbu-mux: Add an entry for TMUXHS4212
Date: Mon, 20 May 2024 08:53:34 +0200 [thread overview]
Message-ID: <469be7c2-6865-40d4-bd06-15dc3a08b3e3@kernel.org> (raw)
In-Reply-To: <20240519202754.GA3334@francesco-nb>
On 19/05/2024 22:27, Francesco Dolcini wrote:
> Hello Krzysztof,
> thanks for the review.
>
> On Sun, May 19, 2024 at 07:38:07PM +0200, Krzysztof Kozlowski wrote:
>> On 17/05/2024 13:11, Parth Pancholi wrote:
>>> From: Parth Pancholi <parth.pancholi@toradex.com>
>>>
>>> Add a compatible entry for the TI TMUXHS4212 GPIO-based
>>> bidirectional 2:1 mux/1:2 demux which can be used for
>>> switching orientation of the SBU lines in USB Type-C
>>> applications.
>>>
>>> TMUXHS4212 datasheet: https://www.ti.com/lit/ds/symlink/tmuxhs4212.pdf
>>>
>>> Signed-off-by: Parth Pancholi <parth.pancholi@toradex.com>
>>> ---
>>> Documentation/devicetree/bindings/usb/gpio-sbu-mux.yaml | 1 +
>>> 1 file changed, 1 insertion(+)
>>
>> Where is an user of this?
>
> The Linux driver (drivers/usb/typec/mux/gpio-sbu-mux.c) is using only
> "gpio-sbu-mux", just in case you did not check yourself already.
>
> As of now there is no DT file in-tree using this new compatible, FWIW
> "onnn,fsusb43l10x" in the same file is not used by anybody. From some
> old discussion here [1] (not exactly the same - I know, and coming not
> from a DT kernel maintainer) I assumed that it was fine to send such
> a change.
>
> If it's not the case we'll send the patch later on, however some
> DT files maintainers (e.g. arch/arm64/boot/dts/ti/) have a policy to
> just accept DT file in which the binding changes are already merged
> therefore I was trying to be a little bit proactive here.
TI? Never heard something like this from them... Such requirement would
seriously slow down any work, so it's not really reasonable. Expectation
is to post both binding change and an user, so DTS, in case of USB in
separate patchsets.
Otherwise you will get such questions, so your biondings patches also
won't have easy path to merging...
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-05-20 6:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 11:11 [PATCH] dt-bindings: usb: gpio-sbu-mux: Add an entry for TMUXHS4212 Parth Pancholi
2024-05-19 17:38 ` Krzysztof Kozlowski
2024-05-19 20:27 ` Francesco Dolcini
2024-05-20 6:53 ` Krzysztof Kozlowski [this message]
2024-05-20 12:14 ` Nishanth Menon
2024-05-20 12:40 ` Nishanth Menon
2024-05-21 7:43 ` Krzysztof Kozlowski
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=469be7c2-6865-40d4-bd06-15dc3a08b3e3@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=francesco@dolcini.it \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=parth.pancholi@toradex.com \
--cc=parth105105@gmail.com \
--cc=robh@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