From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: neil.armstrong@linaro.org,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: usb: qcom,pmic-typec: drop port description
Date: Fri, 22 Mar 2024 15:23:21 +0000 [thread overview]
Message-ID: <0b091595-1587-421d-bb00-c00ef729d143@linaro.org> (raw)
In-Reply-To: <c0f1e898-7638-4b7b-a938-9e31e5b57e57@linaro.org>
On 22/03/2024 15:09, neil.armstrong@linaro.org wrote:
>> TBH I think we should drop this HS, SS stuff from the connector
>> definition - there's nothing to say in a h/w definition anywhere HS
>> must be a port or indeed SS - not all hardware knows or cares about
>> different HS/SS signalling.
>
> It matches the USB-C connector electrical characteristics, which by spec
> has, at least:
> - High-Speed USB Line
> - up to 4 differential high-speed lanes that can be switched to DP, USB2
> or PCIe
> - SideBand line (SBU)
>
> And those 3 components can be handled by 3 different HW in the SoC, so
> each one has a dedicated port.
>
> Remember DT describes the HW, not the SW implementation.
>
> Neil
Yes, you're right about that.
I suppose
1. Orientation switches should be defined as coming from a port on the
connector associated with the CC pins.
port@3:
orientation-switch port name goes here
2. Data-role switches...
Again the CC pins
https://community.silabs.com/s/article/what-s-the-role-of-cc-pin-in-type-c-solution?language=en_US
Maybe the right-thing-to-do is to add another port for the CC pins -
which would still describe the hardware characteristics but would
_accurately_ name the thing which does the data-role/orientation switching
CC1/CC2
Then we would not be abusing HS/SS/SBU for the port names - we'd be
extending the connector definition but also naming the ports/endpoints
appropriately associated with the data over the hw
---
bod
next prev parent reply other threads:[~2024-03-22 15:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 11:52 [PATCH 0/2] dt-bindings: usb: qcom,pmic-typec: OF graph corrections Dmitry Baryshkov
2024-03-22 11:52 ` [PATCH 1/2] dt-bindings: usb: qcom,pmic-typec: drop port description Dmitry Baryshkov
2024-03-22 12:35 ` Bryan O'Donoghue
2024-03-22 13:28 ` Dmitry Baryshkov
2024-03-22 14:52 ` Bryan O'Donoghue
2024-03-22 15:09 ` neil.armstrong
2024-03-22 15:23 ` Bryan O'Donoghue [this message]
2024-03-22 15:49 ` Dmitry Baryshkov
2024-03-22 18:36 ` Rob Herring
2024-03-22 19:08 ` Dmitry Baryshkov
2024-03-22 20:44 ` Bryan O'Donoghue
2024-03-22 22:31 ` Dmitry Baryshkov
2024-03-22 11:52 ` [PATCH 2/2] dt-bindings: usb: qcom,pmic-typec: update example to follow connector schema Dmitry Baryshkov
2024-03-22 18:26 ` Konrad Dybcio
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=0b091595-1587-421d-bb00-c00ef729d143@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.