All of lore.kernel.org
 help / color / mirror / Atom feed
From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: Rosen Penev <rosenp@gmail.com>, Linus Walleij <linusw@kernel.org>
Cc: linux-gpio@vger.kernel.org, chleroy@kernel.org,
	Michael Ellerman <mpe@ellerman.id.au>,
	Nicholas Piggin <npiggin@gmail.com>,
	Bartosz Golaszewski <brgl@kernel.org>,
	"open list:LINUX FOR POWERPC (32-BIT AND 64-BIT)"
	<linuxppc-dev@lists.ozlabs.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/7] gpio: move ppc4xx driver to drivers/gpio and modernize
Date: Wed, 29 Jul 2026 15:50:42 +0530	[thread overview]
Message-ID: <230cf7f0-600e-40e7-8056-6332c678e14c@linux.ibm.com> (raw)
In-Reply-To: <CAKxU2N_LhgDj-+-gd0_N9gQOzCddq7dypYhayFQ_09zggpor6Q@mail.gmail.com>


On 6/9/26 3:50 AM, Rosen Penev wrote:
> On Mon, Jun 8, 2026 at 3:10 PM Linus Walleij <linusw@kernel.org> wrote:
>> Hi Rosen,
>>
>> On Tue, Jun 2, 2026 at 7:01 AM Rosen Penev <rosenp@gmail.com> 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.

Maddy
>> The series:
>> Reviewed-by: Linus Walleij <linusw@kernel.org>
>>
>> Yours,
>> Linus Walleij


  parent reply	other threads:[~2026-07-29 10:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02  5:01 [PATCH 0/7] gpio: move ppc4xx driver to drivers/gpio and modernize Rosen Penev
2026-06-02  5:01 ` [PATCH 1/7] gpio: move ppc4xx gpio driver from arch/powerpc to drivers/gpio Rosen Penev
2026-06-02  5:01 ` [PATCH 2/7] gpio: ppc44x: Use module platform driver helper for GPIO Rosen Penev
2026-06-02  5:01 ` [PATCH 3/7] gpio: ppc44x: Set GPIO chip firmware node Rosen Penev
2026-06-02  5:01 ` [PATCH 4/7] gpio: ppc44x: Use platform resource helper for GPIO MMIO Rosen Penev
2026-06-02  5:01 ` [PATCH 5/7] gpio: ppc44x: Convert GPIO to generic MMIO Rosen Penev
2026-06-02  7:51   ` Bartosz Golaszewski
2026-06-02  9:26     ` Rosen Penev
2026-07-29 10:55       ` Madhavan Srinivasan
2026-07-29 18:32         ` Rosen Penev
2026-07-30  5:48           ` Christophe Leroy (CS GROUP)
2026-07-30 20:44             ` Rosen Penev
2026-06-02  5:01 ` [PATCH 6/7] gpio: ppc44x: drop PPC-specific IO helpers and rename to ppc44x Rosen Penev
2026-06-02  5:01 ` [PATCH 7/7] gpio: ppc44x: add MODULE info Rosen Penev
2026-06-08 22:10 ` [PATCH 0/7] gpio: move ppc4xx driver to drivers/gpio and modernize Linus Walleij
2026-06-08 22:20   ` Rosen Penev
2026-06-08 22:59     ` Linus Walleij
2026-07-29 10:20     ` Madhavan Srinivasan [this message]
2026-07-29 18:31       ` Rosen Penev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=230cf7f0-600e-40e7-8056-6332c678e14c@linux.ibm.com \
    --to=maddy@linux.ibm.com \
    --cc=brgl@kernel.org \
    --cc=chleroy@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=rosenp@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.