Comment 341 for bug 1887190

Revision history for this message
Coiby Xu (coiby) wrote :

Hi Mike Boruta (maridius),

> On Sun, Nov 29, 2020 at 08:07:43PM -0000, Mike Boruta wrote:
> >@Coiby Xu (coiby)
> >
> >Hello Coiby, had some time today so I compiled 5.7.19 from ubuntu
> >mainline (https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7.19/) with
> >pinctrl_amd configured as a module, applied the patch in #171, and ran
> >the command you provided:
> >
> >$ sudo cat /sys/kernel/debug/gpio | grep -A1 pin130
> >pin130 Level trigger| Active low| interrupt is enabled| interrupt is unmasked| disable wakeup in S0i3 state| disable wakeup in S3 state|
> > disable wakeup in S4/S5 state| input is high| pull-up is disabled| Pull-down is disabled| output is disabled| 0x51bc8
> >
> Obviously, the patch in #171 didn't take into effect because 0x51bc8 means
> debounce filter is enabled and the debounce timeout is set to 124.8ms.
> So my best guess is
> /lib/modules/`uname -r`/kernel/drivers/pinctrl/pinctrl-amd.ko.xz
> hasn't been replaced by the patched one.

I had the same issue when using Fedora and find out it's caused by the pinctrl-amd driver being stored into the initramfs. Maybe the same thing happened to ubuntu. You can try re-building the initramfs by running `sudo update-initramfs -u' after replacing the old module with the new one.