GPIO static allocation warning with v6.2-rcX

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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



[Index of Archives]     [Linux SPI]     [Linux Kernel]     [Linux ARM (vger)]     [Linux ARM MSM]     [Linux Omap]     [Linux Arm]     [Linux Tegra]     [Fedora ARM]     [Linux for Samsung SOC]     [eCos]     [Linux Fastboot]     [Gcc Help]     [Git]     [DCCP]     [IETF Announce]     [Security]     [Linux MIPS]     [Yosemite Campsites]

  Powered by Linux