[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <543b5d42-a007-4f13-824e-1f8a27dfbd33@landley.net>
Date: Tue, 12 Aug 2025 13:28:22 -0500
From: Rob Landley <rob@...dley.net>
To: Arnd Bergmann <arnd@...nel.org>, Bartosz Golaszewski <brgl@...ev.pl>,
Linus Walleij <linus.walleij@...aro.org>, linux-gpio@...r.kernel.org,
Yoshinori Sato <ysato@...rs.sourceforge.jp>, Rich Felker <dalias@...c.org>,
John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
Cc: Arnd Bergmann <arnd@...db.de>, Michael Ellerman <mpe@...erman.id.au>,
Steven Rostedt <rostedt@...dmis.org>, "Paul E. McKenney"
<paulmck@...nel.org>, Masahiro Yamada <masahiroy@...nel.org>,
Dave Vasilevsky <dave@...ilevsky.ca>,
Geert Uytterhoeven <geert+renesas@...der.be>, linux-sh@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 04/21] sh: select legacy gpiolib interface
On 8/8/25 10:17, Arnd Bergmann wrote:
> diff --git a/arch/sh/Kconfig b/arch/sh/Kconfig
> index d5795067befa..d60f1d5a94c0 100644
> --- a/arch/sh/Kconfig
> +++ b/arch/sh/Kconfig
> @@ -462,6 +462,7 @@ config CPU_SUBTYPE_SHX3
> select CPU_SHX3
> select GENERIC_CLOCKEVENTS_BROADCAST if SMP
> select GPIOLIB
> + select GPIOLIB_LEGACY
> select PINCTRL
Is there a reason to have both rather than having GPIOLIB_LEGACY select
GPIOLIB? (Does the legacy one ever NOT use the new one?)
Rob
Powered by blists - more mailing lists