Cherry-pick gpio and pinctrl drivers from upstream

[Asmaa Mnebhi]

SRU Justification:

[Impact]

Cherry pick gpio-mlxbf3.c and pinctrl-mlxbf3.c patches from linux-next.

[Fix]

* Revert existing pinctrl-mlxbf3.c driver changes
* Revert existing gpio-mlxbf3.c driver changes
* Cherry-pick all the following commits from linux-next:
  gpio-mlxbf3.c:
  cd33f216d241520385a5166ae73a0771197a9f0b
  38a700efc51080c7184f71edbf5e49561da9754f
  1d2a22fa6d2511d5871d87c15b4fe7a944fe3b2a

  pinctrl-mlxbf3.c:
  d11f932808dc689717e409bbc81b5093e7902fc9
  743d3336029ffe2bb38e982a3b572ced243c6d43
  c0f84760b01e8d8b59e9e186a4f7fa8f081a4488
  69657e60b8a7faf83b583c658ec7ce1f5ece9eb3

[Test Case]

* All test cases are for BF3 only
* Check that the gpio-mlxbf3 driver gets loaded at boot time without issues
* Check that the pinctrl-mlxbf3 driver gets loaded at boot time without issues
* use libgpiod to test the access to gpio pin 0 through 4 i.e. read and write.
* rmmod and modprobe of both drivers
* Check that pwr-mlxbf driver is loaded successfully
* Check that mlxbf-gige driver is loaded successfully and the irq is initialized properly (dmesg | grep PHY)

[Regression Potential]

* We introduced a dependency of the gpio-mlxbf3 driver on pinctrl-mlxbf3. So we need to make sure that
  doesnt trigger any regressions with loading other dependent drivers
* make sure that removing/reloading the driver/restarting the DPU doesnt cause any panic related to these drivers.

[Bartlomiej Zolnierkiewicz (bzolnier)]

This bug is awaiting verification that the linux-bluefield/5.15.0-1025.27 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-bluefield/5.15.0-1027.29 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Bartlomiej Zolnierkiewicz (bzolnier)]

Mark the verification as already done using the new tag.