From: Mario Limonciello <mario.limonciello@xxxxxxx> I have some hardware in front of me that uses the soc-button-array driver but the power button doesn't work. Digging into it, it's because the ASL prescribes a debounce of 0 for the power button, but the soc-button-array driver hardcodes 50ms. Hardcoding it to what the ASL expects the power button works. I looked at the callpath into the GPIO core and I believe it's because the debounce value from _CRS is never programmed to the hardware the way that the GPIO gets setup. This series add that programming path and then drops the hardcoded value. Hopefully Hans can confirm this continues to work on the hardware that he originally developed the hardcoding for. If it doesn't work on that hardware, I think it's more scalable to introduce a quirk for it so that the kernel can at least set the values intended by the firmware. Mario Limonciello (2): gpiolib: acpi: Program debounce when finding GPIO Revert "Input: soc_button_array - debounce the buttons" drivers/gpio/gpiolib-acpi-core.c | 4 ++++ drivers/input/misc/soc_button_array.c | 2 -- 2 files changed, 4 insertions(+), 2 deletions(-) -- 2.43.0
