From: Swati Agarwal <swati.agarwal@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>,
andersson@kernel.org, conor+dt@kernel.org, krzk+dt@kernel.org,
robh@kernel.org, konradybcio@kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: lemans-evk: Add host mode support for USB1 controller
Date: Mon, 8 Dec 2025 16:19:56 +0530 [thread overview]
Message-ID: <9937db19-de90-459f-844d-bce60abe9f7b@oss.qualcomm.com> (raw)
In-Reply-To: <638f4184-b582-4a48-ad63-7c1fd2db492f@oss.qualcomm.com>
Hi,
On 12/3/2025 5:17 PM, Konrad Dybcio wrote:
> On 12/3/25 12:41 PM, Krishna Kurapati wrote:
>>
>>
>> On 12/3/2025 4:59 PM, Konrad Dybcio wrote:
>>> On 12/3/25 3:42 AM, Swati Agarwal wrote:
>>>> Enable Host mode support for USB1 controller on EVK Platform.
>>>>
>>>> For secondary USB Typec port, there is a genesys USB HUB sitting in between
>>>> SOC and HD3SS3220 Type-C port controller and SS lines run from the SoC
>>>> through the hub to the Port controller. Mark the second USB controller as
>>>> host only capable.
>>>>
>>>> Added HD3SS3220 Type-C port controller along with Type-c connector for
>>>> controlling vbus supply.
>>>>
>>>> Signed-off-by: Swati Agarwal <swati.agarwal@oss.qualcomm.com>
>>>> ---
>
> [...]
>
>>>> + hd3ss3220_47_in_ep: endpoint {
>>>
>>> How about rename the other one to hd3ss3220_0 and name this one hd3ss322_1?
>>> _47 doesn't really tell us anything and may re-appear if there's another
>>> instance of this IC on another I2C bus
Thanks Konrad and Dmitry for the review.
For addressing this renaming for USB0 controller, shall i keep a separate patch and should i address in same DT patch for USB1?>>>
>>
>> ACK. Can we rename them as "usb-typec_1" and "usb_typec_2" ?
>> Krzysztof suggested to use generic names and hence we used "usb-typec" instead of hd3ss3220.
>
> The generic names rule only applies to node names (text before '@'),
> the labels are generally only expected to "make overall sense", I think
>
>>>> +&usb_1 {
>>>> + dr_mode = "host";
>>>
>>> The connector states it's a dual-role data and power device. Is there any
>>> reason to keep this in host-only mode?
>>>
>>
>> As mentioned in commit text, there is a onboard hub sitting between SoC and the HD3SS3220 port controller. Hence device mode can't be used. This was the reason we left the above port nodes empty since we can't connect them to port nodes of controller.
>
> It would have helped if I had paid more attention to that message then..
>
>> Can we mark the connector as host only and remove the empty endpoints ? Would that we sufficient ?
>
> The connector should definitely be marked host-only, but the endpoints should
> still reflect the physical connectivity.
>
> If I understood your case properly, this is analogous to what &usb2_2_dwc3
> does in arch/arm64/boot/dts/qcom/sdm850-lenovo-yoga-c630.dts - see Commit
> c02716951e66 ("arm64: dts: qcom: sdm850-lenovo-yoga-c630: add routing for
> second USB connector")
For adding, onboard hub which is GL3590 in DT, it requires adding SS hub bindings in genesys,gl850g.yaml.
My plan is to first submit the binding patch and then follow up with this DT patch on top of it.
Regards,
Swati>
> Konrad
next prev parent reply other threads:[~2025-12-08 10:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 2:42 [PATCH] arm64: dts: qcom: lemans-evk: Add host mode support for USB1 controller Swati Agarwal
2025-12-03 11:29 ` Konrad Dybcio
2025-12-03 11:41 ` Krishna Kurapati
2025-12-03 11:47 ` Konrad Dybcio
2025-12-08 10:49 ` Swati Agarwal [this message]
2025-12-08 16:42 ` Konrad Dybcio
2025-12-09 6:03 ` Swati Agarwal
2025-12-09 7:44 ` Dmitry Baryshkov
2025-12-06 4:11 ` Dmitry Baryshkov
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=9937db19-de90-459f-844d-bce60abe9f7b@oss.qualcomm.com \
--to=swati.agarwal@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krishna.kurapati@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox