From: Karl Palsson <[email protected]> Add documentation that makes it easier to find the alternative, recommended, and default handling for buttons in OpenWrt.
Signed-off-by: Karl Palsson <[email protected]> --- I was having a hard time discovering buttons, and getting conflicts after enabling the input-gpio-keys* modules. zajec on IRC suggested I could submit patches to improve the docs and hopefully help with discovering gpio-button-hotplug. package/kernel/linux/modules/input.mk | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/package/kernel/linux/modules/input.mk b/package/kernel/linux/modules/input.mk index 32adc1e..f42cbae 100644 --- a/package/kernel/linux/modules/input.mk +++ b/package/kernel/linux/modules/input.mk @@ -82,6 +82,9 @@ endef define KernelPackage/input-gpio-keys/description This driver implements support for buttons connected to GPIO pins of various CPUs (and some other chips). + + See also gpio-button-hotplug which is an alternative, lower overhead + implementation that generates uevents instead of kernel input events. endef $(eval $(call KernelPackage,input-gpio-keys)) @@ -101,6 +104,9 @@ endef define KernelPackage/input-gpio-keys-polled/description Kernel module for support polled GPIO keys input device + + See also gpio-button-hotplug which is an alternative, lower overhead + implementation that generates uevents instead of kernel input events. endef $(eval $(call KernelPackage,input-gpio-keys-polled)) -- 1.8.3.1 _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
