The upstream patch "gpio: mlxbf3: only get IRQ for device instance 0" does NOT apply cleanly to the BF3 GPIO driver in Jammy. There's additional logic required in Jammy that affects this patch merge.
For now, let's just use this bug for Noble repo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2115531 Title: gpio-mlxbf3: need to fix get IRQ resource error Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] The BF3 GPIO driver (gpio-mlxbf3) in both Jammy and Noble repos are missing an upstream patch. The result is that kernel log shows this error message upon every boot: mlxbf3_gpio MLNXBF33:01: error -ENXIO: IRQ index 0 not found [Fix] The upstream patch "gpio: mlxbf3: only get IRQ for device instance 0" needs to be cherry picked into Jammy and Noble repos. [Test Case] * Boot BF3 platform with software containing fix * Check the kernel log via dmesg * Verify no errors from BF3 GPIO driver related to "IRQ index 0" [Regression Potential] This fix is straightforward and present in upstream, so low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2115531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
