On Sat, Jan 21, 2023 at 2:48 PM Mario Limonciello <mario.limonciello@xxxxxxx> wrote: > If one GPIO has debounce enabled but future GPIOs in the list don't > have debounce the time never gets reset and shows wrong value. > > Signed-off-by: Mario Limonciello <mario.limonciello@xxxxxxx> Patch applied for fixes. Yours, Lijnus Walleij
Re: [PATCH 1/2] pinctrl: amd: Fix debug output for debounce time
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH 1/2] pinctrl: amd: Fix debug output for debounce time
- From: Linus Walleij <linus.walleij@xxxxxxxxxx>
- Date: Fri, 27 Jan 2023 13:40:59 +0100
- In-reply-to: <20230121134812.16637-2-mario.limonciello@amd.com>
- References: <20230121134812.16637-1-mario.limonciello@amd.com> <20230121134812.16637-2-mario.limonciello@amd.com>
- References:
- [PATCH 0/2] Fix some more fallout from GPIOs from _CRS
- From: Mario Limonciello
- [PATCH 1/2] pinctrl: amd: Fix debug output for debounce time
- From: Mario Limonciello
- [PATCH 0/2] Fix some more fallout from GPIOs from _CRS
- Prev by Date: Re: [PATCH] pinctrl: aspeed: Force to disable the function's signal
- Next by Date: Re: [PATCH] pinctrl: single: fix potential NULL dereference
- Previous by thread: [PATCH 1/2] pinctrl: amd: Fix debug output for debounce time
- Next by thread: [PATCH 0/2] add pinctrl driver for MT7981 SoC
- Index(es):
 |