Now extcon-usb-gpio only supports for GPIO egdge trigger, but VBUS/ID gpios' detection can be triggered by the level trigger on some platforms. Thus intoduce one property 'extcon-gpio,level-trigger' to identify this situation.
Signed-off-by: Baolin Wang baolin.wang@linaro.org --- .../devicetree/bindings/extcon/extcon-usb-gpio.txt | 3 +++ 1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/extcon/extcon-usb-gpio.txt b/Documentation/devicetree/bindings/extcon/extcon-usb-gpio.txt index dfc14f7..191504b 100644 --- a/Documentation/devicetree/bindings/extcon/extcon-usb-gpio.txt +++ b/Documentation/devicetree/bindings/extcon/extcon-usb-gpio.txt @@ -9,6 +9,9 @@ Required properties: 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. +- extcon-gpio,level-trigger: Boolean, set this gpio's interrupt flag to +level trigger. If not specified defaults to false, gpio's interrupt flag +defaults to edge trigger.
Example: Examples of extcon-usb-gpio node in dra7-evm.dts as listed below: extcon_usb1 {