Re: [PATCH] gpio: Allow user to customise maximum number of GPIOs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Christophe Leroy <christophe.leroy@xxxxxxxxxx>
Subject: Re: [PATCH] gpio: Allow user to customise maximum number of GPIOs
From: Linus Walleij <linus.walleij@xxxxxxxxxx>
Date: Fri, 26 Aug 2022 15:49:49 +0200
Cc: Arnd Bergmann <arnd@xxxxxxxx>, Alexandre Courbot <gnurou@xxxxxxxxx>, Alexandre Courbot <acourbot@xxxxxxxxxx>, Bartosz Golaszewski <brgl@xxxxxxxx>, Jonathan Corbet <corbet@xxxxxxx>, Russell King <linux@xxxxxxxxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>, Borislav Petkov <bp@xxxxxxxxx>, Dave Hansen <dave.hansen@xxxxxxxxxxxxxxx>, "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" <x86@xxxxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>, "open list:GPIO SUBSYSTEM" <linux-gpio@xxxxxxxxxxxxxxx>, "open list:DOCUMENTATION" <linux-doc@xxxxxxxxxxxxxxx>, open list <linux-kernel@xxxxxxxxxxxxxxx>, "moderated list:ARM PORT" <linux-arm-kernel@xxxxxxxxxxxxxxxxxxx>, "open list:GENERIC INCLUDE/ASM HEADER FILES" <linux-arch@xxxxxxxxxxxxxxx>
In-reply-to: <87f2ff4c-3426-201c-df86-2d06d3587a20@csgroup.eu>
References: <f31b818cf8d682de61c74b133beffcc8a8202478.1660041358.git.christophe.leroy@csgroup.eu> <CACRpkdY53c0qXx24Am1TMivXr-MV+fQ8B0CDjtGi6=+2tn4-7A@mail.gmail.com> <CAK8P3a1Vh1Uehuin-u5QrTO5qh+t0aK_hA-QZwqc00Db_+MKcw@mail.gmail.com> <CACRpkdbhbwBe=jU5prifXCYUXPqULhst0se3ZRH+sWOh9XeoLQ@mail.gmail.com> <CAK8P3a0j-54_OkXC7x3NSNaHhwJ+9umNgbpsrPxUB4dwewK63A@mail.gmail.com> <CACRpkda0+iy8H0YmyowSDn8RbYgnVbC1k+o5F67inXg4Qb934Q@mail.gmail.com> <CAK8P3a0uuJ_z8wmNmQTW_qPNqzz7XoxZdHgqbzmK+ydtjraeHg@mail.gmail.com> <CACRpkdb5ow4hD3td6agCuKWvuxptm5AV4rsCrcxNStNdXnBzrA@mail.gmail.com> <87f2ff4c-3426-201c-df86-2d06d3587a20@csgroup.eu>

On Thu, Aug 25, 2022 at 4:00 PM Christophe Leroy
<christophe.leroy@xxxxxxxxxx> wrote:

> > Christophe? Will you take a stab at it?
>
> Which patch should I write ?

One that removes CONFIG_ARCH_HAS_NR_GPIO entirely, then
allocate bases for new GPIO chips from 0 and upward instead.
And then see what happens.

Yours,
Linus Walleij

Follow-Ups:
- Re: [PATCH] gpio: Allow user to customise maximum number of GPIOs
  - From: Christophe Leroy

References:
- [PATCH] gpio: Allow user to customise maximum number of GPIOs
  - From: Christophe Leroy
- Re: [PATCH] gpio: Allow user to customise maximum number of GPIOs
  - From: Linus Walleij
- Re: [PATCH] gpio: Allow user to customise maximum number of GPIOs
  - From: Arnd Bergmann
- Re: [PATCH] gpio: Allow user to customise maximum number of GPIOs
  - From: Linus Walleij
- Re: [PATCH] gpio: Allow user to customise maximum number of GPIOs
  - From: Arnd Bergmann
- Re: [PATCH] gpio: Allow user to customise maximum number of GPIOs
  - From: Linus Walleij
- Re: [PATCH] gpio: Allow user to customise maximum number of GPIOs
  - From: Arnd Bergmann
- Re: [PATCH] gpio: Allow user to customise maximum number of GPIOs
  - From: Linus Walleij
- Re: [PATCH] gpio: Allow user to customise maximum number of GPIOs
  - From: Christophe Leroy

Prev by Date: [PATCH v3] wait_on_bit: add an acquire memory barrier
Next by Date: Re: [PATCH] wait_on_bit: add an acquire memory barrier
Previous by thread: Re: [PATCH] gpio: Allow user to customise maximum number of GPIOs
Next by thread: Re: [PATCH] gpio: Allow user to customise maximum number of GPIOs
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel] [Kernel Newbies] [x86 Platform Driver] [Netdev] [Linux Wireless] [Netfilter] [Bugtraq] [Linux Filesystems] [Yosemite Discussion] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Device Mapper]