lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230228084627.e3afg3tp6tzpepb4@pengutronix.de>
Date:   Tue, 28 Feb 2023 09:46:27 +0100
From:   Marco Felsch <m.felsch@...gutronix.de>
To:     Dario Binacchi <dario.binacchi@...rulasolutions.com>
Cc:     Stefan Wahren <stefan.wahren@...e.com>,
        Sascha Hauer <s.hauer@...gutronix.de>,
        Shawn Guo <shawnguo@...nel.org>,
        Bartosz Golaszewski <brgl@...ev.pl>,
        linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org,
        NXP Linux Team <linux-imx@....com>,
        Pengutronix Kernel Team <kernel@...gutronix.de>,
        Fabio Estevam <festevam@...il.com>,
        Linus Walleij <linus.walleij@...aro.org>,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] gpio: mxs: use dynamic allocation of base

Hi Dario,

On 23-02-28, Dario Binacchi wrote:
> Hi Stefan,
> 
> On Mon, Feb 27, 2023 at 6:52 PM Stefan Wahren <stefan.wahren@...e.com> wrote:
> >
> > Hi Dario,
> >
> > Am 26.02.23 um 21:53 schrieb Dario Binacchi:
> > > Since commit 502df79b860563d7 ("gpiolib: Warn on drivers still using static
> > > gpiobase allocation"), one or more warnings are printed during boot on
> > > systems where static allocation of GPIO base is used:
> > >
> > > [    0.136834] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation.
> > > [    0.142753] gpio gpiochip1: Static allocation of GPIO base is deprecated, use dynamic allocation.
> > > [    0.148452] gpio gpiochip2: Static allocation of GPIO base is deprecated, use dynamic allocation.
> > > [    0.154341] gpio gpiochip3: Static allocation of GPIO base is deprecated, use dynamic allocation.
> > > [    0.160097] gpio gpiochip4: Static allocation of GPIO base is deprecated, use dynamic allocation.
> > >
> > > So let's follow the suggestion and use dynamic allocation.
> >
> > i understand the motivation of avoiding these warnings.
> >
> > AFAIK the MXS platform is older than the dynamic allocation of GPIO
> > base. In the perfect world all applications has been migrated to
> > libgpiod / chardev GPIO. But i'm really concerned this hasn't happend
> > yet, at least for this platform. So i believe this change break
> > applications, since it affects userspace.
> 
> Thanks for your explanations.

There was also a lengthly discussion here:

https://lore.kernel.org/all/20230120104647.nwki4silrtd7bt3w@pengutronix.de/

> Do you think it makes sense to use a Kconfig option to enable/disable
> the dynamic allocation of GPIO base?

What we could do is to check the GPIO_SYSFS kconfig symbol. If this is
enabled we should keep the current behaviour to not break the uAPI else
we can go with the dynamic numbering. What we should avoid is a new
Kconfig symbol.

Regards,
  Marco

> As done, if I'm not mistaken, in commit 80d34260f36c6 ("pinctrl:
> renesas: gpio: Use dynamic GPIO base if no function GPIOs")?
> With legacy support enabled by default, but the ability to try out the
> latest dynamic allocation functionality.
> 
> Thanks and regards,
> Dario
> 
> >
> > Best regards
> >
> > >
> > > Signed-off-by: Dario Binacchi <dario.binacchi@...rulasolutions.com>
> > > ---
> > >
> > >   drivers/gpio/gpio-mxs.c | 2 +-
> > >   1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/gpio/gpio-mxs.c b/drivers/gpio/gpio-mxs.c
> > > index 7f59e5d936c2..b48a7c1fb7c1 100644
> > > --- a/drivers/gpio/gpio-mxs.c
> > > +++ b/drivers/gpio/gpio-mxs.c
> > > @@ -330,7 +330,7 @@ static int mxs_gpio_probe(struct platform_device *pdev)
> > >
> > >       port->gc.to_irq = mxs_gpio_to_irq;
> > >       port->gc.get_direction = mxs_gpio_get_direction;
> > > -     port->gc.base = port->id * 32;
> > > +     port->gc.base = -1;
> > >
> > >       err = gpiochip_add_data(&port->gc, port);
> > >       if (err)
> 
> 
> 
> -- 
> 
> Dario Binacchi
> 
> Senior Embedded Linux Developer
> 
> dario.binacchi@...rulasolutions.com
> 
> __________________________________
> 
> 
> Amarula Solutions SRL
> 
> Via Le Canevare 30, 31100 Treviso, Veneto, IT
> 
> T. +39 042 243 5310
> info@...rulasolutions.com
> 
> www.amarulasolutions.com
> 
> 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ