patrick/zephyr
1
0
Fork 0
Code Issues Pull requests Actions 8 Packages Projects Releases Wiki Activity
zephyr/drivers/input/Kconfig.gpio_keys

11 lines
277 B
Plaintext
Raw Normal View History

gpio: Add driver support for software based gpio debounce Software based GPIO debounce driver implementation. Signed-off-by: Al Semjonovs <asemjonovs@google.com>
2022-12-06 23:14:05 +01:00
# Copyright (c) 2022 Google LLC
# SPDX-License-Identifier: Apache-2.0
drivers: move gpio_keys from gpio to input Port the gpio_keys_zephyr driver from the gpio subsystem with a dedicated API to the input subsystem reporting input events. Move the test as well, simplify the cases a bit since the API is simpler now. Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
2023-01-31 16:58:22 +01:00
config INPUT_GPIO_KEYS
input: unify gpio-keys and zephyr,gpio-keys Change the gpio-keys and zephyr,gpio-keys so that they can both be used with the input subsystem driver. Make the zephyr,code property optional so that existing out of tree board can still use this node with their custom code, but change everything else so that an existin gpio-keys node can be used with the input driver as long as the codes are defined. From the application perspective, this means that the application can still use the GPIOs directly, the input specific driver only gets enabled if CONFIG_INPUT is enabled and the driver can always be turned off manually. This makes gpio-keys behave the same as gpio-leds with CONFIG_LED. Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
2023-08-03 12:52:55 +02:00
bool "GPIO Keys input driver"
gpio: Add driver support for software based gpio debounce Software based GPIO debounce driver implementation. Signed-off-by: Al Semjonovs <asemjonovs@google.com>
2022-12-06 23:14:05 +01:00
default y
input: unify gpio-keys and zephyr,gpio-keys Change the gpio-keys and zephyr,gpio-keys so that they can both be used with the input subsystem driver. Make the zephyr,code property optional so that existing out of tree board can still use this node with their custom code, but change everything else so that an existin gpio-keys node can be used with the input driver as long as the codes are defined. From the application perspective, this means that the application can still use the GPIOs directly, the input specific driver only gets enabled if CONFIG_INPUT is enabled and the driver can always be turned off manually. This makes gpio-keys behave the same as gpio-leds with CONFIG_LED. Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
2023-08-03 12:52:55 +02:00
depends on DT_HAS_GPIO_KEYS_ENABLED || DT_HAS_ZEPHYR_GPIO_KEYS_ENABLED
drivers: input: add missing GPIO_KEYS GPIO dependency Add a missing dependency between GPIO_KEYS and GPIO. Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
2023-08-03 23:12:51 +02:00
depends on GPIO
gpio: Add driver support for software based gpio debounce Software based GPIO debounce driver implementation. Signed-off-by: Al Semjonovs <asemjonovs@google.com>
2022-12-06 23:14:05 +01:00
help
input: unify gpio-keys and zephyr,gpio-keys Change the gpio-keys and zephyr,gpio-keys so that they can both be used with the input subsystem driver. Make the zephyr,code property optional so that existing out of tree board can still use this node with their custom code, but change everything else so that an existin gpio-keys node can be used with the input driver as long as the codes are defined. From the application perspective, this means that the application can still use the GPIOs directly, the input specific driver only gets enabled if CONFIG_INPUT is enabled and the driver can always be turned off manually. This makes gpio-keys behave the same as gpio-leds with CONFIG_LED. Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
2023-08-03 12:52:55 +02:00
Enable support for GPIO Keys input driver.
Reference in a new issue Copy permalink