2023-11-15 16:50:56

by Bartosz Golaszewski

[permalink] [raw]
Subject: [PATCH 0/3] pinctrl: don't use gpiod_to_chip()

From: Bartosz Golaszewski <[email protected]>

Let's start working towards removing gpiod_to_chip() from the kernel.
Start with pinctrl. The first patch should go through the GPIO tree
and become available through an immutable tag so that we can get more
conversions in this cycle elsewhere.

Bartosz Golaszewski (3):
gpiolib: provide gpio_devie_get_label()
pinctrl: stop using gpiod_to_chip()
pinctrl: don't include GPIOLIB private header

drivers/gpio/gpiolib.c | 14 ++++++++++++++
drivers/pinctrl/core.c | 18 ++++++++----------
include/linux/gpio/driver.h | 1 +
3 files changed, 23 insertions(+), 10 deletions(-)

--
2.40.1


2023-11-16 13:44:10

by Linus Walleij

[permalink] [raw]
Subject: Re: [PATCH 0/3] pinctrl: don't use gpiod_to_chip()

On Wed, Nov 15, 2023 at 5:50 PM Bartosz Golaszewski <[email protected]> wrote:

> From: Bartosz Golaszewski <[email protected]>
>
> Let's start working towards removing gpiod_to_chip() from the kernel.
> Start with pinctrl. The first patch should go through the GPIO tree
> and become available through an immutable tag so that we can get more
> conversions in this cycle elsewhere.

Fair enough, maybe an immutable branch with all three patches?
Probably best to merga all three into both subsystems I think.

Acked-by: Linus Walleij <[email protected]>

Yours,
Linus Walleij

2023-11-20 15:07:39

by Bartosz Golaszewski

[permalink] [raw]
Subject: Re: [PATCH 0/3] pinctrl: don't use gpiod_to_chip()

On Thu, Nov 16, 2023 at 2:43 PM Linus Walleij <[email protected]> wrote:
>
> On Wed, Nov 15, 2023 at 5:50 PM Bartosz Golaszewski <[email protected]> wrote:
>
> > From: Bartosz Golaszewski <[email protected]>
> >
> > Let's start working towards removing gpiod_to_chip() from the kernel.
> > Start with pinctrl. The first patch should go through the GPIO tree
> > and become available through an immutable tag so that we can get more
> > conversions in this cycle elsewhere.
>
> Fair enough, maybe an immutable branch with all three patches?
> Probably best to merga all three into both subsystems I think.
>

Nah, I don't think I need to pollute the GPIO tree with every pinctrl
patch. It's enough to just merge the first one into GPIO and you do
the same in pinctrl.

Bart

> Acked-by: Linus Walleij <[email protected]>
>
> Yours,
> Linus Walleij

2023-11-24 10:02:03

by Linus Walleij

[permalink] [raw]
Subject: Re: [PATCH 0/3] pinctrl: don't use gpiod_to_chip()

On Mon, Nov 20, 2023 at 4:06 PM Bartosz Golaszewski <[email protected]> wrote:
> On Thu, Nov 16, 2023 at 2:43 PM Linus Walleij <[email protected]> wrote:
> > On Wed, Nov 15, 2023 at 5:50 PM Bartosz Golaszewski <[email protected]> wrote:
> >
> > > From: Bartosz Golaszewski <[email protected]>
> > >
> > > Let's start working towards removing gpiod_to_chip() from the kernel.
> > > Start with pinctrl. The first patch should go through the GPIO tree
> > > and become available through an immutable tag so that we can get more
> > > conversions in this cycle elsewhere.
> >
> > Fair enough, maybe an immutable branch with all three patches?
> > Probably best to merga all three into both subsystems I think.
> >
>
> Nah, I don't think I need to pollute the GPIO tree with every pinctrl
> patch. It's enough to just merge the first one into GPIO and you do
> the same in pinctrl.

Fair enough, but I need that immutable branch for patch 1 so I
can merge the rest on top.

Yours,
Linus Walleij

2023-11-24 19:40:33

by Bartosz Golaszewski

[permalink] [raw]
Subject: Re: [PATCH 0/3] pinctrl: don't use gpiod_to_chip()

On Fri, Nov 24, 2023 at 11:01 AM Linus Walleij <[email protected]> wrote:
>
> On Mon, Nov 20, 2023 at 4:06 PM Bartosz Golaszewski <[email protected]> wrote:
> > On Thu, Nov 16, 2023 at 2:43 PM Linus Walleij <[email protected]> wrote:
> > > On Wed, Nov 15, 2023 at 5:50 PM Bartosz Golaszewski <[email protected]> wrote:
> > >
> > > > From: Bartosz Golaszewski <[email protected]>
> > > >
> > > > Let's start working towards removing gpiod_to_chip() from the kernel.
> > > > Start with pinctrl. The first patch should go through the GPIO tree
> > > > and become available through an immutable tag so that we can get more
> > > > conversions in this cycle elsewhere.
> > >
> > > Fair enough, maybe an immutable branch with all three patches?
> > > Probably best to merga all three into both subsystems I think.
> > >
> >
> > Nah, I don't think I need to pollute the GPIO tree with every pinctrl
> > patch. It's enough to just merge the first one into GPIO and you do
> > the same in pinctrl.
>
> Fair enough, but I need that immutable branch for patch 1 so I
> can merge the rest on top.
>
> Yours,
> Linus Walleij

I applied the first patch (after fixing the typo in the commit
message) and sent you the immutable branch to pull. Please apply the
remaining patches to the pinctrl tree directly.

Thanks!
Bart

2023-11-24 23:29:25

by Linus Walleij

[permalink] [raw]
Subject: Re: [PATCH 0/3] pinctrl: don't use gpiod_to_chip()

On Fri, Nov 24, 2023 at 8:40 PM Bartosz Golaszewski <[email protected]> wrote:
> On Fri, Nov 24, 2023 at 11:01 AM Linus Walleij <[email protected]> wrote:
> >
> > On Mon, Nov 20, 2023 at 4:06 PM Bartosz Golaszewski <[email protected]> wrote:
> > > On Thu, Nov 16, 2023 at 2:43 PM Linus Walleij <[email protected]> wrote:
> > > > On Wed, Nov 15, 2023 at 5:50 PM Bartosz Golaszewski <[email protected]> wrote:
> > > >
> > > > > From: Bartosz Golaszewski <[email protected]>
> > > > >
> > > > > Let's start working towards removing gpiod_to_chip() from the kernel.
> > > > > Start with pinctrl. The first patch should go through the GPIO tree
> > > > > and become available through an immutable tag so that we can get more
> > > > > conversions in this cycle elsewhere.
> > > >
> > > > Fair enough, maybe an immutable branch with all three patches?
> > > > Probably best to merga all three into both subsystems I think.
> > > >
> > >
> > > Nah, I don't think I need to pollute the GPIO tree with every pinctrl
> > > patch. It's enough to just merge the first one into GPIO and you do
> > > the same in pinctrl.
> >
> > Fair enough, but I need that immutable branch for patch 1 so I
> > can merge the rest on top.
> >
> > Yours,
> > Linus Walleij
>
> I applied the first patch (after fixing the typo in the commit
> message) and sent you the immutable branch to pull. Please apply the
> remaining patches to the pinctrl tree directly.

Pulled it and applied the other two patches on top, thanks!

Yours,
Linus Walleij