• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 601 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

Linux/AM4378: gpio-keys debounce limit

TMDXIDK5718: Problem with USB_ID GPIO

Christian Leeb
Expert 1690 points
Part Number: TMDXIDK5718
Other Parts Discussed in Thread: AM5748

Hi,

I have AM5748 based custom HW, Using TISDK 6.0.0.07

Using excon for USB:

/ {
extcon_usb2: extcon_usb2_usb {
compatible = "linux,extcon-usb-gpio";
vbus-gpio = <&gpio2 26 0 GPIO_ACTIVE_HIGH>;
id-gpio = <&gpio4 27 0 GPIO_ACTIVE_HIGH>;
};
};

When booting I get

[   10.112887] extcon-usb-gpio extcon_usb2_usb: GPIO lookup for consumer id

[   10.112898] extcon-usb-gpio extcon_usb2_usb: using device tree for GPIO lookup

[   10.112911] of_get_named_gpiod_flags: can't parse 'id-gpios' property of node '/extcon_usb2_usb[0]'

[   10.113001] of_get_named_gpiod_flags: parsed 'id-gpio' property of node '/extcon_usb2_usb[0]' - status (0)

[   10.113074] extcon-usb-gpio extcon_usb2_usb: GPIO lookup for consumer vbus

[   10.113082] extcon-usb-gpio extcon_usb2_usb: using device tree for GPIO lookup

[   10.113092] of_get_named_gpiod_flags: can't parse 'vbus-gpios' property of node '/extcon_usb2_usb[0]'

[   10.113122] of_get_named_gpiod_flags: parsed 'vbus-gpio' property of node '/extcon_usb2_usb[0]' - status (0)

 

[   10.113346] omap_gpio 48059000.gpio: Could not set line 27 debounce to 20000 microseconds (-22)

 


The pin vbus-gpio is working but it seems that extcon-usb-gpio driver is requesting an invalid debounce time?

Regards, Chris

  • 0
    TI__Guru**** 171431 points

    Hi Chris,

    Christian Leeb said:
    The pin vbus-gpio is working but it seems that extcon-usb-gpio driver is requesting an invalid debounce time?

    At a first glance of the gpio driver, it seems to be the case. I will look into it to understand what is happening.

  • 0
    TI__Guru**** 171431 points

    Hi Chris,

    Sorry for taking so long to get back on this.

    I just reviewed the kernel code, it turned out that when programming the id-gpio pin, the extcon driver (extcon-palmas.c) tries to set 20ms debounce to the gpio controller, which is over the limit on AM57x, so printed this kernel message, and switched to use software debounce. So this message can be ignored.