All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: Rosen Penev <rosenp@gmail.com>,
	Madhavan Srinivasan <maddy@linux.ibm.com>
Cc: Bartosz Golaszewski <brgl@kernel.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Nicholas Piggin <npiggin@gmail.com>,
	Linus Walleij <linusw@kernel.org>,
	"open list:LINUX FOR POWERPC (32-BIT AND 64-BIT)"
	<linuxppc-dev@lists.ozlabs.org>,
	open list <linux-kernel@vger.kernel.org>,
	linux-gpio@vger.kernel.org
Subject: Re: [PATCH 5/7] gpio: ppc44x: Convert GPIO to generic MMIO
Date: Thu, 30 Jul 2026 07:48:57 +0200	[thread overview]
Message-ID: <880aae3c-a552-4d3f-8ed1-e3dc3911ee1a@kernel.org> (raw)
In-Reply-To: <CAKxU2N8n4iHrr-+NxL6D9WZ4EgH_XVJ7yfPa4P6ZyFNJTir60w@mail.gmail.com>



Le 29/07/2026 à 20:32, Rosen Penev a écrit :
> On Wed, Jul 29, 2026 at 3:55 AM Madhavan Srinivasan <maddy@linux.ibm.com> wrote:
>>
>>
>> On 6/2/26 2:56 PM, Rosen Penev wrote:
>>> On Tue Jun 2, 2026 at 12:51 AM PDT, Bartosz Golaszewski wrote:
>>>> On Tue, 2 Jun 2026 07:01:29 +0200, Rosen Penev <rosenp@gmail.com> said:
>>>>> Use gpio_generic_chip_init() to set up the PPC44x GPIO chip
>>>>> instead of open-coding the basic get, set, locking and state handling.
>>>>>
>>>>> Keep the PPC44x-specific direction callbacks because they still need to
>>>>> program ODR and the OSR/TSR registers around the generic data and
>>>>> direction registers.
>>>>>
>>>>> Assisted-by: Codex:GPT-5.5
>>>>> Signed-off-by: Rosen Penev <rosenp@gmail.com>
>>>>> ---
>>>> ...
>>>>
>>>>> @@ -124,10 +102,11 @@ static int
>>>>>    ppc4xx_gpio_dir_out(struct gpio_chip *gc, unsigned int gpio, int val)
>>>>>    {
>>>>>      struct ppc4xx_gpio_chip *chip = gpiochip_get_data(gc);
>>>>> +   struct gpio_generic_chip *gen_gc = &chip->chip;
>>>>>      struct ppc4xx_gpio __iomem *regs = chip->regs;
>>>>>      unsigned long flags;
>>>>>
>>>>> -   spin_lock_irqsave(&chip->lock, flags);
>>>>> +   gpio_generic_chip_lock_irqsave(gen_gc, flags);
>>>> If you're already doing it, can you use lock guards too?
>>> Sure. btw, I avoided placing
>>
>> Do you have plan to address this comment in v2
> Yeah I have it fixed locally.

You should probably put patch 
https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20260517063754.21819-1-rosenp@gmail.com/ 
as first patch in this series in order to enable applying the fix to 
6.18 without applying the entire series and to avoid any future conflict.

Christophe


> 
> I'm not sure if this has to do through the PPC or GPIO tree.
>>
>> Maddy
>>>
>>> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore.kernel.org%2Fall%2F20260517063754.21819-1-rosenp%40gmail.com%2F&data=05%7C02%7Cchristophe.leroy%40csgroup.eu%7C2ac0ec525c7045cd969508deed9fc7e0%7C8b87af7d86474dc78df45f69a2011bb5%7C0%7C0%7C639209467691381845%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=iqGebSy%2BbKMBFZz%2FZwZ9N2Jf8v63FkGPNhrdUf864fE%3D&reserved=0
>>>
>>> in the beginning of the series. My thinking is that's for older kernels.
>>> I believe either the generic API or devm_gpiochip_add_data fixes this.
>>>> Bart
>>>


  reply	other threads:[~2026-07-30  5:49 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) [this message]
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
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=880aae3c-a552-4d3f-8ed1-e3dc3911ee1a@kernel.org \
    --to=chleroy@kernel.org \
    --cc=brgl@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=maddy@linux.ibm.com \
    --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.