Commit c281d8a5 authored by Sean Anderson's avatar Sean Anderson Committed by Greg Kroah-Hartman

dt-bindings: usb: usb-nop-xceiv: Repurpose vbus-regulator

The vbus-regulator property was never actually read from the device tree.
Introduce a new property vbus-supply to represent the regulator powering
the VBUS when acting as an A-Device. This supply will be enabled and
disabled as necessary. Note that this is different from vbus-regulator,
which represented the available current available to draw from VBUS in
B-Device mode. Because no one was using vbus-regulator, remove it.
Signed-off-by: default avatarSean Anderson <sean.anderson@seco.com>
Reviewed-by: default avatarLinus Walleij <linus.walleij@linaro.org>
Link: https://lore.kernel.org/r/20240123225111.1629405-2-sean.anderson@seco.comSigned-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
parent 4158af05
...@@ -37,10 +37,11 @@ properties: ...@@ -37,10 +37,11 @@ properties:
description: Should specify the GPIO detecting a VBus insertion description: Should specify the GPIO detecting a VBus insertion
maxItems: 1 maxItems: 1
vbus-regulator: vbus-supply:
description: Should specify the regulator supplying current drawn from description: regulator supplying VBUS. It will be enabled and disabled
the VBus line. dynamically in OTG mode. If the regulator is controlled by a
$ref: /schemas/types.yaml#/definitions/phandle GPIO line, this should be modeled as a regulator-fixed and
referenced by this supply.
wakeup-source: wakeup-source:
description: description:
...@@ -65,7 +66,7 @@ examples: ...@@ -65,7 +66,7 @@ examples:
vcc-supply = <&hsusb1_vcc_regulator>; vcc-supply = <&hsusb1_vcc_regulator>;
reset-gpios = <&gpio1 7 GPIO_ACTIVE_LOW>; reset-gpios = <&gpio1 7 GPIO_ACTIVE_LOW>;
vbus-detect-gpio = <&gpio2 13 GPIO_ACTIVE_HIGH>; vbus-detect-gpio = <&gpio2 13 GPIO_ACTIVE_HIGH>;
vbus-regulator = <&vbus_regulator>; vbus-supply = <&vbus_regulator>;
#phy-cells = <0>; #phy-cells = <0>;
}; };
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment