From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Arnd Bergmann <arnd@kernel.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Steven Rostedt <rostedt@goodmis.org>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sh: select legacy gpiolib interface
Date: Tue, 28 Apr 2026 18:08:27 +0200 [thread overview]
Message-ID: <716fb62be57fd01c68cfed9220da7ebddfa321ae.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <20260428155528.3218943-1-arnd@kernel.org>
Hi Arnd,
On Tue, 2026-04-28 at 17:55 +0200, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> Many board files on sh reference the legacy gpiolib interfaces that
> are becoming optional. To ensure the boards can keep building, select
> CONFIG_GPIOLIB_LEGACY on each of the boards that have one of the
> hardcoded calls.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> arch/sh/Kconfig | 1 +
> arch/sh/boards/Kconfig | 8 ++++++++
> arch/sh/boards/mach-highlander/Kconfig | 1 +
> arch/sh/boards/mach-rsk/Kconfig | 3 +++
> 4 files changed, 13 insertions(+)
>
> 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
>
> # SH4AL-DSP Processor Support
> diff --git a/arch/sh/boards/Kconfig b/arch/sh/boards/Kconfig
> index 1af93be61b1f..d89b74177233 100644
> --- a/arch/sh/boards/Kconfig
> +++ b/arch/sh/boards/Kconfig
> @@ -80,6 +80,7 @@ config SH_7724_SOLUTION_ENGINE
> select SOLUTION_ENGINE
> depends on CPU_SUBTYPE_SH7724
> select GPIOLIB
> + select GPIOLIB_LEGACY
> select REGULATOR_FIXED_VOLTAGE if REGULATOR
> imply SND_SOC_AK4642 if SND_SIMPLE_CARD
> help
> @@ -199,6 +200,7 @@ config SH_SH7757LCR
> bool "SH7757LCR"
> depends on CPU_SUBTYPE_SH7757
> select GPIOLIB
> + select GPIOLIB_LEGACY
> select REGULATOR_FIXED_VOLTAGE if REGULATOR
>
> config SH_SH7785LCR
> @@ -226,6 +228,7 @@ config SH_URQUELL
> bool "Urquell"
> depends on CPU_SUBTYPE_SH7786
> select GPIOLIB
> + select GPIOLIB_LEGACY
> select HAVE_PCI
> select NO_IOPORT_MAP if !PCI
>
> @@ -233,6 +236,7 @@ config SH_MIGOR
> bool "Migo-R"
> depends on CPU_SUBTYPE_SH7722
> select GPIOLIB
> + select GPIOLIB_LEGACY
> select REGULATOR_FIXED_VOLTAGE if REGULATOR
> help
> Select Migo-R if configuring for the SH7722 Migo-R platform
> @@ -242,6 +246,7 @@ config SH_AP325RXA
> bool "AP-325RXA"
> depends on CPU_SUBTYPE_SH7723
> select GPIOLIB
> + select GPIOLIB_LEGACY
> select REGULATOR_FIXED_VOLTAGE if REGULATOR
> help
> Renesas "AP-325RXA" support.
> @@ -251,6 +256,7 @@ config SH_KFR2R09
> bool "KFR2R09"
> depends on CPU_SUBTYPE_SH7724
> select GPIOLIB
> + select GPIOLIB_LEGACY
> select REGULATOR_FIXED_VOLTAGE if REGULATOR
> help
> "Kit For R2R for 2009" support.
> @@ -259,6 +265,7 @@ config SH_ECOVEC
> bool "EcoVec"
> depends on CPU_SUBTYPE_SH7724
> select GPIOLIB
> + select GPIOLIB_LEGACY
> select REGULATOR_FIXED_VOLTAGE if REGULATOR
> imply SND_SOC_DA7210 if SND_SIMPLE_CARD
> help
> @@ -329,6 +336,7 @@ config SH_MAGIC_PANEL_R2
> bool "Magic Panel R2"
> depends on CPU_SUBTYPE_SH7720
> select GPIOLIB
> + select GPIOLIB_LEGACY
> select REGULATOR_FIXED_VOLTAGE if REGULATOR
> help
> Select Magic Panel R2 if configuring for Magic Panel R2.
> diff --git a/arch/sh/boards/mach-highlander/Kconfig b/arch/sh/boards/mach-highlander/Kconfig
> index b0abd03cac4e..cd3a553ce30c 100644
> --- a/arch/sh/boards/mach-highlander/Kconfig
> +++ b/arch/sh/boards/mach-highlander/Kconfig
> @@ -20,6 +20,7 @@ config SH_R7785RP
> bool "R7785RP board support"
> depends on CPU_SUBTYPE_SH7785
> select GPIOLIB
> + select GPIOLIB_LEGACY
>
> endchoice
>
> diff --git a/arch/sh/boards/mach-rsk/Kconfig b/arch/sh/boards/mach-rsk/Kconfig
> index f0299bc4416f..3810937aa5d4 100644
> --- a/arch/sh/boards/mach-rsk/Kconfig
> +++ b/arch/sh/boards/mach-rsk/Kconfig
> @@ -12,16 +12,19 @@ config SH_RSK7201
> config SH_RSK7203
> bool "RSK7203"
> select GPIOLIB
> + select GPIOLIB_LEGACY
> depends on CPU_SUBTYPE_SH7203
>
> config SH_RSK7264
> bool "RSK2+SH7264"
> select GPIOLIB
> + select GPIOLIB_LEGACY
> depends on CPU_SUBTYPE_SH7264
>
> config SH_RSK7269
> bool "RSK2+SH7269"
> select GPIOLIB
> + select GPIOLIB_LEGACY
> depends on CPU_SUBTYPE_SH7269
>
> endchoice
Thanks, this looks reasonable from what I can see. Most boards require at least
gpio_request() which is now guarded behind CONFIG_GPIOLIB_LEGACY.
Does this maybe need a Fixes: tag to identify the commit which introduced the new
config option CONFIG_GPIOLIB_LEGACY?
Reviewed-by: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Thanks,
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2026-04-28 16:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 15:55 [PATCH] sh: select legacy gpiolib interface Arnd Bergmann
2026-04-28 16:08 ` John Paul Adrian Glaubitz [this message]
2026-04-28 16:20 ` Arnd Bergmann
2026-04-28 16:21 ` John Paul Adrian Glaubitz
2026-04-28 16:24 ` Arnd Bergmann
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=716fb62be57fd01c68cfed9220da7ebddfa321ae.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=dalias@libc.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=ysato@users.sourceforge.jp \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox