From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: linux-renesas-soc@vger.kernel.org, linux-sh@vger.kernel.org,
linux-gpio@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH] pinctrl: renesas: gpio: Use dynamic GPIO base if no function GPIOs
Date: Thu, 17 Nov 2022 20:49:52 +0100 [thread overview]
Message-ID: <CAMuHMdWczT_G7MKULUKZfZxkrB9Hk-SNam-qZqqsmb+sz1sQHg@mail.gmail.com> (raw)
In-Reply-To: <df2cf30ac4c3cbee726799f32b727c1ebe62819c.1668000684.git.geert+renesas@glider.be>
On Wed, Nov 9, 2022 at 2:38 PM Geert Uytterhoeven
<geert+renesas@glider.be> wrote:
> Since commit 502df79b860563d7 ("gpiolib: Warn on drivers still using
> static gpiobase allocation") in gpio/for-next, one or more warnings are
> printed during boot on systems where the pin controller also provides
> GPIO functionality:
>
> gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation.
>
> Fix this for ARM-based SH/R-Mobile SoCs by:
> 1. Taking into account a non-zero GPIO base in the various GPIO chip
> callbacks,
> 2. Switching to dynamic allocation of the GPIO base when support for
> legacy function GPIOs is not enabled.
>
> On SuperH SoCs using legacy function GPIOs, the GPIO bases of the GPIO
> controller and the GPIO function controller must not be changed, as all
> board files rely on the fixed GPIO_* and GPIO_FN_* definitions provided
> by the various <cpu/sh*.h> header files.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Thanks, queued in renesas-pinctrl-for-v6.2.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2022-11-17 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 13:33 [PATCH] pinctrl: renesas: gpio: Use dynamic GPIO base if no function GPIOs Geert Uytterhoeven
2022-11-17 19:49 ` Geert Uytterhoeven [this message]
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=CAMuHMdWczT_G7MKULUKZfZxkrB9Hk-SNam-qZqqsmb+sz1sQHg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=christophe.leroy@csgroup.eu \
--cc=geert+renesas@glider.be \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).