Re: [PATCH 05/10] [v2] mips: select legacy gpiolib interfaces where used
Thomas Bogendoerfer <[email protected]> Mon, 15 Jun 2026 12:33:22 +0200
| Newsgroups | org.kernel.vger.linux-sh,org.infradead.lists.linux-arm-kernel,org.kernel.vger.linux-gpio,org.kernel.vger.linux-input,org.kernel.vger.linux-kernel,org.kernel.vger.linux-leds,org.kernel.vger.linux-mips,org.kernel.vger.linux-omap,org.kernel.vger.linux-wireless,org.kernel.vger.netdev |
|---|---|
| Message-ID | <[email protected]> |
On Wed, May 20, 2026 at 08:38:10PM +0200, Arnd Bergmann wrote: > From: Arnd Bergmann <[email protected]> > > A few old machines have not been converted away from the old-style > gpiolib interfaces. Make these select the new CONFIG_GPIOLIB_LEGACY > symbol so the code still works where it is needed but can be left > out otherwise. > > This is the list of all gpio_request() calls in mips: > > arch/mips/alchemy/devboards/db1000.c: gpio_request(19, "sd0_cd"); > arch/mips/alchemy/devboards/db1000.c: gpio_request(20, "sd1_cd"); > arch/mips/alchemy/devboards/db1200.c: gpio_request(215, "otg-vbus"); > arch/mips/bcm47xx/workarounds.c: err = gpio_request_one(usb_power, GPIOF_OUT_INIT_HIGH, "usb_power"); > arch/mips/bcm63xx/boards/board_bcm963xx.c: gpio_request_one(board.ephy_reset_gpio, > arch/mips/txx9/rbtx4927/setup.c: gpio_request(15, "sio-dtr"); > > Most of these should be easy enough to change to modern gpio descriptors > or remove if they are no longer in use. > > Reviewed-by: Bartosz Golaszewski <[email protected]> > Reviewed-by: Linus Walleij <[email protected]> > Signed-off-by: Arnd Bergmann <[email protected]> > --- > v2: no changes. There was no discussion on this, but the patch > has so far not made it into the linux-mips tree, so I'm including > it for completeness. > --- > arch/mips/Kconfig | 5 +++++ > arch/mips/alchemy/Kconfig | 1 - > arch/mips/txx9/Kconfig | 1 + > 3 files changed, 6 insertions(+), 1 deletion(-) applied to mips-next Thomas. -- Crap can work. Given enough thrust pigs will fly, but it's not necessarily a good idea. [ RFC1925, 2.3 ]