linux-kernel - Re: [PATCH v5 1/2] dt-bindings: usb: ti,hd3ss3220: Add support for VBUS based on ID state

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <e4ebf454-93ae-47be-bb12-2ab363812b1b@oss.qualcomm.com>
Date: Mon, 27 Oct 2025 14:01:55 +0530
From: Krishna Kurapati PSSNV <krishna.kurapati@....qualcomm.com>
To: Biju Das <biju.das.jz@...renesas.com>
Cc: "linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Rob Herring <robh@...nel.org>,
        Krzysztof Kozlowski <krzk+dt@...nel.org>,
        Conor Dooley <conor+dt@...nel.org>,
        Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
        Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v5 1/2] dt-bindings: usb: ti,hd3ss3220: Add support for
 VBUS based on ID state



On 10/27/2025 1:02 PM, Biju Das wrote:
> 
> 
>> -----Original Message-----
>> From: Krishna Kurapati <krishna.kurapati@....qualcomm.com>
>> Sent: 27 October 2025 07:28
> .kernel.org; linux-kernel@...r.kernel.org; Krishna
>> Kurapati <krishna.kurapati@....qualcomm.com>
>> Subject: [PATCH v5 1/2] dt-bindings: usb: ti,hd3ss3220: Add support for VBUS based on ID state
>>
>> Update the bindings to support reading ID state and VBUS, as per the
>> HD3SS3220 data sheet. The ID pin is kept high if VBUS is not at VSafe0V and asserted low once VBUS is
>> at VSafe0V, enforcing the Type-C requirement that VBUS must be at VSafe0V before re-enabling VBUS.
>>
>> Add id-gpios property to describe the input gpio for USB ID pin.
>>
>> Signed-off-by: Krishna Kurapati <krishna.kurapati@....qualcomm.com>
>> ---
>>   Documentation/devicetree/bindings/usb/ti,hd3ss3220.yaml | 8 ++++++++
>>   1 file changed, 8 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/usb/ti,hd3ss3220.yaml
>> b/Documentation/devicetree/bindings/usb/ti,hd3ss3220.yaml
>> index bec1c8047bc0..06099e93c6c3 100644
>> --- a/Documentation/devicetree/bindings/usb/ti,hd3ss3220.yaml
>> +++ b/Documentation/devicetree/bindings/usb/ti,hd3ss3220.yaml
>> @@ -25,6 +25,14 @@ properties:
>>     interrupts:
>>       maxItems: 1
>>
>> +  id-gpios:
>> +    description:
>> +      An input gpio for USB ID pin. Upon detecting a UFP device, HD3SS3220
>> +      will keep ID pin high if VBUS is not at VSafe0V. Once VBUS is at VSafe0V,
>> +      the HD3SS3220 will assert ID pin low. This is done to enforce Type-C
>> +      requirement that VBUS must be at VSafe0V before re-enabling VBUS.
>> +    maxItems: 1
>> +
> 
> Maybe to help DT users, add an example for this use case??
> 
Hi Biju,

  Adding GPIO to dt is a generic thing. Also this is an optional 
proprety. Can we skip adding an example.

Regards,
Krishna,