All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Felsch <m.felsch@pengutronix.de>
To: linus.walleij@linaro.org, brgl@bgdev.pl, shawnguo@kernel.org,
	bartosz.golaszewski@linaro.org, christophe.leroy@csgroup.eu
Cc: kernel@pengutronix.de, linux-gpio@vger.kernel.org
Subject: GPIO static allocation warning with v6.2-rcX
Date: Fri, 20 Jan 2023 11:46:47 +0100	[thread overview]
Message-ID: <20230120104647.nwki4silrtd7bt3w@pengutronix.de> (raw)

Hi all,

I stumbled over the following warning while testing the new v6.2-rc4 on
a imx8mm-evk:

[    1.507131] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation.
[    1.517786] gpio gpiochip1: Static allocation of GPIO base is deprecated, use dynamic allocation.
[    1.528273] gpio gpiochip2: Static allocation of GPIO base is deprecated, use dynamic allocation.
[    1.538739] gpio gpiochip3: Static allocation of GPIO base is deprecated, use dynamic allocation.
[    1.549195] gpio gpiochip4: Static allocation of GPIO base is deprecated, use dynamic allocation.

The warning was introduced by commit [1] but at least the following
drivers are parsing the alias for a gpiochip to use it as base:
 - drivers/gpio/gpio-mxs.c
 - drivers/gpio/gpio-mxc.c
 - drivers/gpio/gpio-clps711x.c
 - drivers/gpio/gpio-mvebu.c
 - drivers/gpio/gpio-rockchip.c
 - drivers/gpio/gpio-vf610.c
 - drivers/gpio/gpio-zynq.c

According commit [2] it seems valid and correct to me to use the alias
and the user-space may rely on this.

Now my question is how we can get rid of the warning without breaking
the user-space?

[1] 502df79b86056 gpiolib: Warn on drivers still using static gpiobase allocation
[2] 7e6086d9e54a1 gpio/mxc: specify gpio base for device tree probe

Regards,
  Marco

             reply	other threads:[~2023-01-20 10:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-20 10:46 Marco Felsch [this message]
2023-01-23 14:55 ` GPIO static allocation warning with v6.2-rcX Bartosz Golaszewski
2023-01-23 14:56   ` Bartosz Golaszewski
2023-01-25  9:35   ` Sascha Hauer
2023-01-25 13:56     ` Bartosz Golaszewski
2023-01-26 10:27       ` Sascha Hauer
2023-01-26  1:57     ` Kent Gibson
2023-01-26 10:14       ` Sascha Hauer
2023-01-26 10:26         ` Kent Gibson
2023-01-26  9:35     ` Linus Walleij
2023-01-26 10:49       ` Sascha Hauer
2023-01-29 18:33         ` Robert Schwebel
2023-01-30 10:19           ` Linus Walleij
2023-01-30 11:02             ` Marco Felsch
2023-01-30 15:01               ` Linus Walleij
2023-01-30 15:45                 ` Rob Herring
2023-01-31  7:21                   ` Alexander Stein
2023-01-30 17:26                 ` Andy Shevchenko
2023-01-30 16:48             ` Uwe Kleine-König
2023-01-30 17:21               ` Bartosz Golaszewski
2023-01-30 23:26               ` Linus Walleij
2023-03-02  2:19           ` Kent Gibson
2023-03-02 15:40             ` Andy Shevchenko
2023-01-26  9:42     ` Linus Walleij

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=20230120104647.nwki4silrtd7bt3w@pengutronix.de \
    --to=m.felsch@pengutronix.de \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=christophe.leroy@csgroup.eu \
    --cc=kernel@pengutronix.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=shawnguo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.