On Wed, Jul 29, 2026 at 3:20 AM Madhavan Srinivasan <[email protected]> wrote:
>
>
> On 6/9/26 3:50 AM, Rosen Penev wrote:
> > On Mon, Jun 8, 2026 at 3:10 PM Linus Walleij <[email protected]> wrote:
> >> Hi Rosen,
> >>
> >> On Tue, Jun 2, 2026 at 7:01 AM Rosen Penev <[email protected]> wrote:
> >>
> >>> This series moves the ppc4xx GPIO driver from arch/powerpc to
> >>> drivers/gpio, converts it to be a proper platform driver using
> >>> generic MMIO helpers, drops architecture-specific accessors, and
> >>> prepares it for module build and COMPILE_TEST.
> >>>
> >>> Patches 1-4 move the driver and convert it to standard platform
> >>> driver infrastructure. Patch 5 switches to generic MMIO helpers.
> >>> Patch 6 drops PPC-specific IO accessors and enables COMPILE_TEST.
> >>> Patch 7 adds the missing MODULE metadata so the driver can actually
> >>> be built as a module.
> >>>
> >>> Rosen Penev (7):
> >>>    gpio: move ppc4xx gpio driver from arch/powerpc to drivers/gpio
> >>>    gpio: ppc44x: Use module platform driver helper for GPIO
> >>>    gpio: ppc44x: Set GPIO chip firmware node
> >>>    gpio: ppc44x: Use platform resource helper for GPIO MMIO
> >>>    gpio: ppc44x: Convert GPIO to generic MMIO
> >>>    gpio: ppc44x: drop PPC-specific IO helpers and rename to ppc44x
> >>>    gpio: ppc44x: add MODULE info
> >> Overall a very nice patch series and happy to see that AI can
> >> assist with this kind of refactoring!
> >>
> >> I guess we should provide some slack so someone from the PPC
> >> camp can test it, and if they don't test it, then it is abandoned and
> >> we should then just apply it anyway.
> > Hmm? I have the hardware. It works fine.
> Honestly I dont have the hardware to test this,
> but thanks for the confirming, i will pull this for the next merge.
Can't tell if you mean next merge window or not.

Anyway, 
https://lore.kernel.org/linuxppc-dev/[email protected]/
needs handling first IMO.

It's needed for kernel 6.18. Otherwise my buttons and LEDs don't work properly.
>
> Maddy
> >> The series:
> >> Reviewed-by: Linus Walleij <[email protected]>
> >>
> >> Yours,
> >> Linus Walleij

Reply via email to