[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3c72e1f3-7873-4f13-a5cd-0aecc5163aab@google.com>
Date: Wed, 26 Nov 2025 12:50:19 -0800
From: Amit Sunil Dhamne <amitsd@...gle.com>
To: Heikki Krogerus <heikki.krogerus@...ux.intel.com>
Cc: Sebastian Reichel <sre@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, André Draszik
<andre.draszik@...aro.org>, Lee Jones <lee@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Badhri Jagan Sridharan <badhri@...gle.com>,
Peter Griffin <peter.griffin@...aro.org>,
Tudor Ambarus <tudor.ambarus@...aro.org>,
Alim Akhtar <alim.akhtar@...sung.com>, linux-kernel@...r.kernel.org,
linux-pm@...r.kernel.org, devicetree@...r.kernel.org,
linux-usb@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, RD Babiera <rdbabiera@...gle.com>,
Kyle Tso <kyletso@...gle.com>
Subject: Re: [PATCH 3/6] dt-bindings: usb: maxim,max33359: Add supply property
for VBUS in OTG mode
Hi Heikki,
On 11/26/25 2:01 AM, Heikki Krogerus wrote:
> Sun, Nov 23, 2025 at 08:35:50AM +0000, Amit Sunil Dhamne via B4 Relay kirjoitti:
>> From: Amit Sunil Dhamne <amitsd@...gle.com>
>>
>> Add a regulator supply property for VBUS when usb is in OTG mode.
> What is "OTG mode"?
>
> OTG is usually used to refer to the USB in device role, even though the
> specification actually defines OTG device as a device capable of both
> host and device roles. So the term was confusing already before.
> Nevertheless, the emphasis is always on data-role, _not_ power-role.
Thanks for the insight!
>
> Here it seems MAX33359 uses the term OTG as a synonym for "source", so
> power-role?
Essentially. The datasheet refers to the mode where VBUS is sourced as
OTG mode.
> Please don't use the term OTG unless you really have to - it's too
> confusing. I know the MAX33359 datasheet uses it, but what you really
> do here is regulate VBUS. So please:
>
> s/otg-vbus/vbus/
I will drop OTG term at least in the USB world and restrict it to the
charger driver.
BR,
Amit
>
> thanks,
>
>> Signed-off-by: Amit Sunil Dhamne <amitsd@...gle.com>
>> Reviewed-by: Badhri Jagan Sridharan <badhri@...gle.com>
>> ---
>> Documentation/devicetree/bindings/usb/maxim,max33359.yaml | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/usb/maxim,max33359.yaml b/Documentation/devicetree/bindings/usb/maxim,max33359.yaml
>> index 3de4dc40b791..a529f18c4918 100644
>> --- a/Documentation/devicetree/bindings/usb/maxim,max33359.yaml
>> +++ b/Documentation/devicetree/bindings/usb/maxim,max33359.yaml
>> @@ -32,6 +32,9 @@ properties:
>> description:
>> Properties for usb c connector.
>>
>> + otg-vbus-supply:
>> + description: Regulator to control OTG VBUS supply.
>> +
>> required:
>> - compatible
>> - reg
>> @@ -53,6 +56,7 @@ examples:
>> reg = <0x25>;
>> interrupt-parent = <&gpa8>;
>> interrupts = <2 IRQ_TYPE_LEVEL_LOW>;
>> + otg-vbus-supply = <&otg_vbus_reg>;
>>
>> connector {
>> compatible = "usb-c-connector";
>>
>> --
>> 2.52.0.rc2.455.g230fcf2819-goog
>>
Powered by blists - more mailing lists