On Sat, Jan 15, 2022 at 6:24 PM Hans de Goede <hdegoede@xxxxxxxxxx> wrote: > On 1/13/22 12:56, Hans de Goede wrote: > > On 1/13/22 12:31, Andy Shevchenko wrote: ... > > Spoiler: I believe the best thing we can do here is to just > > never touch the debounce settings at all, see below. > So one more argument in favor of just disabling support for > setting the debounce value, while looking at a git log of > the baytrail pinctrl driver I noticed this: > So before that (which is not that long ago) we were never doing any > of the pinctrl stuff at all AFAICT, which to me seems like another > argument that the best answer to the debounce settings challenges > is to just not do it ? Hesitating between enabling this feature and practical applications, I think you are right. No need to keep the code that never has been properly enabled on the real products (as I read from your research). -- With Best Regards, Andy Shevchenko