On Wed, Nov 9, 2022 at 2:38 PM Geert Uytterhoeven
<geert+renesas@xxxxxxxxx> 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@xxxxxxxxx>
Thanks, queued in renesas-pinctrl-for-v6.2.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
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
