mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-27 06:05:12 +07:00
541332a13b
Driver can now work with both ID and VBUS pins or either one of them. There can be the following 3 cases 1) Both ID and VBUS GPIOs are available: ID = LOW -> USB_HOST active, USB inactive ID = HIGH -> USB_HOST inactive, USB state is same as VBUS. 2) Only ID GPIO is available: ID = LOW -> USB_HOST active, USB inactive ID = HIGH -> USB_HOST inactive, USB active 3) Only VBUS GPIO is available: VBUS = LOW -> USB_HOST inactive, USB inactive VBUS = HIGH -> USB_HOST inactive, USB active Signed-off-by: Roger Quadros <rogerq@ti.com> Reviewed-by: Peter Chen <peter.chen@nxp.com> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
22 lines
589 B
Plaintext
22 lines
589 B
Plaintext
USB GPIO Extcon device
|
|
|
|
This is a virtual device used to generate USB cable states from the USB ID pin
|
|
connected to a GPIO pin.
|
|
|
|
Required properties:
|
|
- compatible: Should be "linux,extcon-usb-gpio"
|
|
|
|
Either one of id-gpio or vbus-gpio must be present. Both can be present as well.
|
|
- id-gpio: gpio for USB ID pin. See gpio binding.
|
|
- vbus-gpio: gpio for USB VBUS pin.
|
|
|
|
Example: Examples of extcon-usb-gpio node in dra7-evm.dts as listed below:
|
|
extcon_usb1 {
|
|
compatible = "linux,extcon-usb-gpio";
|
|
id-gpio = <&gpio6 1 GPIO_ACTIVE_HIGH>;
|
|
}
|
|
|
|
&omap_dwc3_1 {
|
|
extcon = <&extcon_usb1>;
|
|
};
|