Re: [PATCH v3 1/5] dt-bindings: usb: convert ti,hd3ss3220 bindings to json-schema

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>>>
>>> Hi Biju,
>>>
>>> I'm involved in a separate thread[1] and I just wanted to get your
>>> inputs on how you understood the port and endpoint assignments for the
>>> USB type C connectors in different designs.
>>>
>>> Since the hd3ss3220 does the type C lane detect and has an integrated
>>> lane select mux, what is the ss_ep being used for?
>>
>> In our case, Type C Connector --> HS lines directly connected to SoC, where
>> as the SS lines connected  to HD3SS3220 Mux and output of mux is
>> Connected to SoC.
>>
>> This mux driver detects state change on the CC lines, reading the
>> orientation/role and communicating this information to SoC for assigning
>> roles using USB role switch framework.
>>
>> Case 1:-  Model connector node as the child node of the mux.
>>
>> The bindings for this case [1] is not complaint to typec connector bindings,
>> since it is missing port@0 node.
>> [1] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
>> next.git/tree/Documentation/devicetree/bindings/usb/ti,hd3ss3220.txt?h=n
>> ext-20200917
>>
>> typec Connector bindings requires port@0 should be HS and port@1 should
>> be SS as per the discussion [2],  so I need to remodel connector node as
>> separate one.
>> [2] https://patchwork.kernel.org/patch/11669423/
>>
>> Case 2:-  Model connector node as a separate one based on the hardware
>> design
>>
>> Type c connector port@0  --> SoC  (hs ep) Type c connector  port@1 -->
>> connected to USB3.0 Mux -->  SoC( for usb3 role switch)
>>
>> Here the input of the Mux is connected to TypeC connector and Output of
>> the mux is connected to the SoC, which is inline with hardware design.
>> The full example of this model here [3]
>> [3] https://patchwork.kernel.org/patch/11733263/
>>
>> In both our designs, looks like, type c connector connected to SS MUX and
>> output of SS Mux is Connected to SoC for role switch. Am I missing some
>> thing?
>> So may be we need to update the connector bindings for this use case. What
>> do you think?
> 
> FYI, I have posted v4 with changes in usb connector bindings.
> 
> [1] https://patchwork.kernel.org/patch/11787677/
> [2] https://patchwork.kernel.org/patch/11787679/
> 
Hi Biju,

Great, thanks! Let me take a look :).

Thanks

Regards,
Wesley Cheng


-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project



[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux