drivers: gpio: sch: implementation does not configure interrupt level/edge #12763
Assignees
Labels
area: GPIO
bug
The issue is a bug, or the PR is fixing a bug
priority: medium
Medium impact/importance bug
Comments
dcpleung
added a commit
to dcpleung/zephyr
that referenced
this issue
Feb 5, 2019
The GPIO controller only supports edge triggering according to the descriptions of the associated registers. So errors out when level trigger is requested. Also adds the option to do double edges triggering as the controller supports this. Fixes zephyrproject-rtos#12763 Signed-off-by: Daniel Leung <daniel.leung@intel.com>
galak
pushed a commit
that referenced
this issue
Feb 7, 2019
The GPIO controller only supports edge triggering according to the descriptions of the associated registers. So errors out when level trigger is requested. Also adds the option to do double edges triggering as the controller supports this. Fixes #12763 Signed-off-by: Daniel Leung <daniel.leung@intel.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
gpio_sch.cconfigures for interrupts but does not inspect the trigger type (GPIO_INT_LEVELvsGPIO_INT_EDGE). It should do so and should diagnose if one of those triggers is not supported.As implemented the driver will behave correctly only for level-triggered interrupts (
GPIO_INT_EDGEis the non-default configuration).The text was updated successfully, but these errors were encountered: