[Kernel-packages] [Bug 2027816] Re: Interrupt storm on GPIO controller on AMD platforms
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: linux (Ubuntu Lunar) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2027816 Title: Interrupt storm on GPIO controller on AMD platforms Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Released Bug description: On ASUS TUF A16 it is reported that the ITE5570 ACPI device connected to GPIO 7 is causing an interrupt storm. This issue doesn't happen on Windows. Comparing the GPIO register configuration between Windows and Linux bit 20 has been configured as a pull up on Windows, but not on Linux. Checking GPIO declaration from the firmware it is clear it *should* have been a pull up on Linux as well. ``` GpioInt (Level, ActiveLow, Exclusive, PullUp, 0x, "\\_SB.GPIO", 0x00, ResourceConsumer, ,) { // Pin list 0x0007 } ``` On Linux amd_gpio_set_config() is currently only used for programming the debounce. Actually the GPIO core calls it with all the arguments that are supported by a GPIO, pinctrl-amd just responds `-ENOTSUPP`. To solve this issue expand amd_gpio_set_config() to support the other arguments amd_pinconf_set() supports, namely `PIN_CONFIG_BIAS_PULL_DOWN`, `PIN_CONFIG_BIAS_PULL_UP`, and `PIN_CONFIG_DRIVE_STRENGTH`. Upstream bug in https://bugzilla.kernel.org/show_bug.cgi?id=217336 Related fixes are: * v6.4: * commit 010f493d90ee ("pinctrl: amd: Add fields for interrupt status and wake status") * commit 75358cf3319d ("pinctrl: amd: Adjust debugfs output") * v6.5-rc1: * commit 968ab9261627 ("pinctrl: amd: Detect internal GPIO0 debounce handling") * linux-next: * commit 0d5ace1a07f7 ("pinctrl: amd: Only use special debounce behavior for GPIO 0") * commit 635a750d958e ("pinctrl: amd: Use amd_pinconf_set() for all config options") * commit 3f62312d04d4 ("pinctrl: amd: Drop pull up select configuration") * commit 283c5ce7da0a ("pinctrl: amd: Unify debounce handling into amd_pinconf_set()") To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2027816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027816] Re: Interrupt storm on GPIO controller on AMD platforms
These fixes all landed in 6.5-rc2, mantic and noble have them for sure, closing those tasks. I'd expect backporting to be done for Lunar and Jammy if necessary. ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Mantic) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** No longer affects: linux-oem-6.1 (Ubuntu Lunar) ** No longer affects: linux-oem-6.1 (Ubuntu Mantic) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2027816 Title: Interrupt storm on GPIO controller on AMD platforms Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Confirmed Status in linux source package in Mantic: Fix Released Bug description: On ASUS TUF A16 it is reported that the ITE5570 ACPI device connected to GPIO 7 is causing an interrupt storm. This issue doesn't happen on Windows. Comparing the GPIO register configuration between Windows and Linux bit 20 has been configured as a pull up on Windows, but not on Linux. Checking GPIO declaration from the firmware it is clear it *should* have been a pull up on Linux as well. ``` GpioInt (Level, ActiveLow, Exclusive, PullUp, 0x, "\\_SB.GPIO", 0x00, ResourceConsumer, ,) { // Pin list 0x0007 } ``` On Linux amd_gpio_set_config() is currently only used for programming the debounce. Actually the GPIO core calls it with all the arguments that are supported by a GPIO, pinctrl-amd just responds `-ENOTSUPP`. To solve this issue expand amd_gpio_set_config() to support the other arguments amd_pinconf_set() supports, namely `PIN_CONFIG_BIAS_PULL_DOWN`, `PIN_CONFIG_BIAS_PULL_UP`, and `PIN_CONFIG_DRIVE_STRENGTH`. Upstream bug in https://bugzilla.kernel.org/show_bug.cgi?id=217336 Related fixes are: * v6.4: * commit 010f493d90ee ("pinctrl: amd: Add fields for interrupt status and wake status") * commit 75358cf3319d ("pinctrl: amd: Adjust debugfs output") * v6.5-rc1: * commit 968ab9261627 ("pinctrl: amd: Detect internal GPIO0 debounce handling") * linux-next: * commit 0d5ace1a07f7 ("pinctrl: amd: Only use special debounce behavior for GPIO 0") * commit 635a750d958e ("pinctrl: amd: Use amd_pinconf_set() for all config options") * commit 3f62312d04d4 ("pinctrl: amd: Drop pull up select configuration") * commit 283c5ce7da0a ("pinctrl: amd: Unify debounce handling into amd_pinconf_set()") To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2027816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027816] Re: Interrupt storm on GPIO controller on AMD platforms
oops, disregard that one, didn't land yet ** Tags removed: verification-needed-jammy-linux-oem-6.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2027816 Title: Interrupt storm on GPIO controller on AMD platforms Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: On ASUS TUF A16 it is reported that the ITE5570 ACPI device connected to GPIO 7 is causing an interrupt storm. This issue doesn't happen on Windows. Comparing the GPIO register configuration between Windows and Linux bit 20 has been configured as a pull up on Windows, but not on Linux. Checking GPIO declaration from the firmware it is clear it *should* have been a pull up on Linux as well. ``` GpioInt (Level, ActiveLow, Exclusive, PullUp, 0x, "\\_SB.GPIO", 0x00, ResourceConsumer, ,) { // Pin list 0x0007 } ``` On Linux amd_gpio_set_config() is currently only used for programming the debounce. Actually the GPIO core calls it with all the arguments that are supported by a GPIO, pinctrl-amd just responds `-ENOTSUPP`. To solve this issue expand amd_gpio_set_config() to support the other arguments amd_pinconf_set() supports, namely `PIN_CONFIG_BIAS_PULL_DOWN`, `PIN_CONFIG_BIAS_PULL_UP`, and `PIN_CONFIG_DRIVE_STRENGTH`. Upstream bug in https://bugzilla.kernel.org/show_bug.cgi?id=217336 Related fixes are: * v6.4: * commit 010f493d90ee ("pinctrl: amd: Add fields for interrupt status and wake status") * commit 75358cf3319d ("pinctrl: amd: Adjust debugfs output") * v6.5-rc1: * commit 968ab9261627 ("pinctrl: amd: Detect internal GPIO0 debounce handling") * linux-next: * commit 0d5ace1a07f7 ("pinctrl: amd: Only use special debounce behavior for GPIO 0") * commit 635a750d958e ("pinctrl: amd: Use amd_pinconf_set() for all config options") * commit 3f62312d04d4 ("pinctrl: amd: Drop pull up select configuration") * commit 283c5ce7da0a ("pinctrl: amd: Unify debounce handling into amd_pinconf_set()") To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2027816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027816] Re: Interrupt storm on GPIO controller on AMD platforms
please verify oem-6.1 1022 ** Tags added: verification-needed-jammy-linux-oem-6.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2027816 Title: Interrupt storm on GPIO controller on AMD platforms Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: On ASUS TUF A16 it is reported that the ITE5570 ACPI device connected to GPIO 7 is causing an interrupt storm. This issue doesn't happen on Windows. Comparing the GPIO register configuration between Windows and Linux bit 20 has been configured as a pull up on Windows, but not on Linux. Checking GPIO declaration from the firmware it is clear it *should* have been a pull up on Linux as well. ``` GpioInt (Level, ActiveLow, Exclusive, PullUp, 0x, "\\_SB.GPIO", 0x00, ResourceConsumer, ,) { // Pin list 0x0007 } ``` On Linux amd_gpio_set_config() is currently only used for programming the debounce. Actually the GPIO core calls it with all the arguments that are supported by a GPIO, pinctrl-amd just responds `-ENOTSUPP`. To solve this issue expand amd_gpio_set_config() to support the other arguments amd_pinconf_set() supports, namely `PIN_CONFIG_BIAS_PULL_DOWN`, `PIN_CONFIG_BIAS_PULL_UP`, and `PIN_CONFIG_DRIVE_STRENGTH`. Upstream bug in https://bugzilla.kernel.org/show_bug.cgi?id=217336 Related fixes are: * v6.4: * commit 010f493d90ee ("pinctrl: amd: Add fields for interrupt status and wake status") * commit 75358cf3319d ("pinctrl: amd: Adjust debugfs output") * v6.5-rc1: * commit 968ab9261627 ("pinctrl: amd: Detect internal GPIO0 debounce handling") * linux-next: * commit 0d5ace1a07f7 ("pinctrl: amd: Only use special debounce behavior for GPIO 0") * commit 635a750d958e ("pinctrl: amd: Use amd_pinconf_set() for all config options") * commit 3f62312d04d4 ("pinctrl: amd: Drop pull up select configuration") * commit 283c5ce7da0a ("pinctrl: amd: Unify debounce handling into amd_pinconf_set()") To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2027816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027816] Re: Interrupt storm on GPIO controller on AMD platforms
** Description changed: On ASUS TUF A16 it is reported that the ITE5570 ACPI device connected to GPIO 7 is causing an interrupt storm. This issue doesn't happen on Windows. Comparing the GPIO register configuration between Windows and Linux bit 20 has been configured as a pull up on Windows, but not on Linux. Checking GPIO declaration from the firmware it is clear it *should* have been a pull up on Linux as well. ``` GpioInt (Level, ActiveLow, Exclusive, PullUp, 0x, -"\\_SB.GPIO", 0x00, ResourceConsumer, ,) + "\\_SB.GPIO", 0x00, ResourceConsumer, ,) { // Pin list 0x0007 } ``` On Linux amd_gpio_set_config() is currently only used for programming the debounce. Actually the GPIO core calls it with all the arguments that are supported by a GPIO, pinctrl-amd just responds `-ENOTSUPP`. To solve this issue expand amd_gpio_set_config() to support the other arguments amd_pinconf_set() supports, namely `PIN_CONFIG_BIAS_PULL_DOWN`, `PIN_CONFIG_BIAS_PULL_UP`, and `PIN_CONFIG_DRIVE_STRENGTH`. Upstream bug in https://bugzilla.kernel.org/show_bug.cgi?id=217336 - Related fixes are: (all in linux-next) - * commit 968ab9261627 ("pinctrl: amd: Detect internal GPIO0 debounce handling") - * commit 0d5ace1a07f7 ("pinctrl: amd: Only use special debounce behavior for GPIO 0") - * commit 635a750d958e ("pinctrl: amd: Use amd_pinconf_set() for all config options") - * commit 3f62312d04d4 ("pinctrl: amd: Drop pull up select configuration") - * commit 283c5ce7da0a ("pinctrl: amd: Unify debounce handling into amd_pinconf_set()") + Related fixes are: + * v6.5-rc1: + * commit 968ab9261627 ("pinctrl: amd: Detect internal GPIO0 debounce handling") + * linux-next: + * commit 0d5ace1a07f7 ("pinctrl: amd: Only use special debounce behavior for GPIO 0") + * commit 635a750d958e ("pinctrl: amd: Use amd_pinconf_set() for all config options") + * commit 3f62312d04d4 ("pinctrl: amd: Drop pull up select configuration") + * commit 283c5ce7da0a ("pinctrl: amd: Unify debounce handling into amd_pinconf_set()") ** Description changed: On ASUS TUF A16 it is reported that the ITE5570 ACPI device connected to GPIO 7 is causing an interrupt storm. This issue doesn't happen on Windows. Comparing the GPIO register configuration between Windows and Linux bit 20 has been configured as a pull up on Windows, but not on Linux. Checking GPIO declaration from the firmware it is clear it *should* have been a pull up on Linux as well. ``` GpioInt (Level, ActiveLow, Exclusive, PullUp, 0x, "\\_SB.GPIO", 0x00, ResourceConsumer, ,) { // Pin list 0x0007 } ``` On Linux amd_gpio_set_config() is currently only used for programming the debounce. Actually the GPIO core calls it with all the arguments that are supported by a GPIO, pinctrl-amd just responds `-ENOTSUPP`. To solve this issue expand amd_gpio_set_config() to support the other arguments amd_pinconf_set() supports, namely `PIN_CONFIG_BIAS_PULL_DOWN`, `PIN_CONFIG_BIAS_PULL_UP`, and `PIN_CONFIG_DRIVE_STRENGTH`. Upstream bug in https://bugzilla.kernel.org/show_bug.cgi?id=217336 Related fixes are: + * v6.4: + * commit 010f493d90ee ("pinctrl: amd: Add fields for interrupt status and wake status") + * commit 75358cf3319d ("pinctrl: amd: Adjust debugfs output") * v6.5-rc1: - * commit 968ab9261627 ("pinctrl: amd: Detect internal GPIO0 debounce handling") + * commit 968ab9261627 ("pinctrl: amd: Detect internal GPIO0 debounce handling") * linux-next: - * commit 0d5ace1a07f7 ("pinctrl: amd: Only use special debounce behavior for GPIO 0") - * commit 635a750d958e ("pinctrl: amd: Use amd_pinconf_set() for all config options") - * commit 3f62312d04d4 ("pinctrl: amd: Drop pull up select configuration") - * commit 283c5ce7da0a ("pinctrl: amd: Unify debounce handling into amd_pinconf_set()") + * commit 0d5ace1a07f7 ("pinctrl: amd: Only use special debounce behavior for GPIO 0") + * commit 635a750d958e ("pinctrl: amd: Use amd_pinconf_set() for all config options") + * commit 3f62312d04d4 ("pinctrl: amd: Drop pull up select configuration") + * commit 283c5ce7da0a ("pinctrl: amd: Unify debounce handling into amd_pinconf_set()") -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2027816 Title: Interrupt storm on GPIO controller on AMD platforms Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description:
[Kernel-packages] [Bug 2027816] Re: Interrupt storm on GPIO controller on AMD platforms
** Summary changed: - interrupt storm on GPIO controller on AMD platforms + Interrupt storm on GPIO controller on AMD platforms -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2027816 Title: Interrupt storm on GPIO controller on AMD platforms Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: On ASUS TUF A16 it is reported that the ITE5570 ACPI device connected to GPIO 7 is causing an interrupt storm. This issue doesn't happen on Windows. Comparing the GPIO register configuration between Windows and Linux bit 20 has been configured as a pull up on Windows, but not on Linux. Checking GPIO declaration from the firmware it is clear it *should* have been a pull up on Linux as well. ``` GpioInt (Level, ActiveLow, Exclusive, PullUp, 0x, "\\_SB.GPIO", 0x00, ResourceConsumer, ,) { // Pin list 0x0007 } ``` On Linux amd_gpio_set_config() is currently only used for programming the debounce. Actually the GPIO core calls it with all the arguments that are supported by a GPIO, pinctrl-amd just responds `-ENOTSUPP`. To solve this issue expand amd_gpio_set_config() to support the other arguments amd_pinconf_set() supports, namely `PIN_CONFIG_BIAS_PULL_DOWN`, `PIN_CONFIG_BIAS_PULL_UP`, and `PIN_CONFIG_DRIVE_STRENGTH`. Upstream bug in https://bugzilla.kernel.org/show_bug.cgi?id=217336 Related fixes are: (all in linux-next) * commit 968ab9261627 ("pinctrl: amd: Detect internal GPIO0 debounce handling") * commit 0d5ace1a07f7 ("pinctrl: amd: Only use special debounce behavior for GPIO 0") * commit 635a750d958e ("pinctrl: amd: Use amd_pinconf_set() for all config options") * commit 3f62312d04d4 ("pinctrl: amd: Drop pull up select configuration") * commit 283c5ce7da0a ("pinctrl: amd: Unify debounce handling into amd_pinconf_set()") To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2027816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027816] Re: interrupt storm on GPIO controller on AMD platforms
commit 635a750d958e ("pinctrl: amd: Use amd_pinconf_set() for all config options") is marked with: Fixes: 2956b5d94a76 ("pinctrl / gpio: Introduce .set_config() callback for GPIO chips") which was landed to v4.11. It follows all the kernels ever since could suffer from the same issue here. ** Tags added: amd oem-priority originate-from-2026793 ** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux (Ubuntu Mantic) Status: New => Confirmed ** Changed in: linux (Ubuntu Lunar) Status: New => Confirmed ** Changed in: linux (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2027816 Title: interrupt storm on GPIO controller on AMD platforms Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: On ASUS TUF A16 it is reported that the ITE5570 ACPI device connected to GPIO 7 is causing an interrupt storm. This issue doesn't happen on Windows. Comparing the GPIO register configuration between Windows and Linux bit 20 has been configured as a pull up on Windows, but not on Linux. Checking GPIO declaration from the firmware it is clear it *should* have been a pull up on Linux as well. ``` GpioInt (Level, ActiveLow, Exclusive, PullUp, 0x, "\\_SB.GPIO", 0x00, ResourceConsumer, ,) { // Pin list 0x0007 } ``` On Linux amd_gpio_set_config() is currently only used for programming the debounce. Actually the GPIO core calls it with all the arguments that are supported by a GPIO, pinctrl-amd just responds `-ENOTSUPP`. To solve this issue expand amd_gpio_set_config() to support the other arguments amd_pinconf_set() supports, namely `PIN_CONFIG_BIAS_PULL_DOWN`, `PIN_CONFIG_BIAS_PULL_UP`, and `PIN_CONFIG_DRIVE_STRENGTH`. Upstream bug in https://bugzilla.kernel.org/show_bug.cgi?id=217336 Related fixes are: (all in linux-next) * commit 968ab9261627 ("pinctrl: amd: Detect internal GPIO0 debounce handling") * commit 0d5ace1a07f7 ("pinctrl: amd: Only use special debounce behavior for GPIO 0") * commit 635a750d958e ("pinctrl: amd: Use amd_pinconf_set() for all config options") * commit 3f62312d04d4 ("pinctrl: amd: Drop pull up select configuration") * commit 283c5ce7da0a ("pinctrl: amd: Unify debounce handling into amd_pinconf_set()") To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2027816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp