2014-04-27 22:10 GMT+02:00 Hauke Mehrtens <ha...@hauke-m.de>: > On 04/17/2014 10:43 PM, Rafał Miłecki wrote: >> Arch code for bcm47xx uses gpio_keys which results in buttons generating >> input events. This means we need kmod-button-hotplug which works as >> input_handler. >> >> Signed-off-by: Rafał Miłecki <zaj...@gmail.com> > > Nack > > We use kmod-gpio-button-hotplug to avoid using the input subsystem and > directly use the gpio-keys. gpio-button-hotplug is a driver for > gpio-keys and works without input. This way we save some memory.
I was using CONFIG_PACKAGE_kmod-input-core=y CONFIG_PACKAGE_kmod-input-gpio-keys=y which enabled in-kernel driver for "gpio-keys". In such case I couldn't use CONFIG_PACKAGE_kmod-gpio-button-hotplug and I had to select CONFIG_PACKAGE_kmod-button-hotplug That was my mistake I selected CONFIG_PACKAGE_kmod-input-gpio-keys=y in the first place. I wonder if we could/should forbid to select CONFIG_PACKAGE_kmod-input-gpio-keys and CONFIG_PACKAGE_kmod-gpio-button-hotplug at the same time. _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
