[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHp75Vexy1p8E5VYj=kX9VPxAghzVwbh3ANvLVP4yrxkHZ+H7A@mail.gmail.com>
Date: Thu, 27 Apr 2023 14:01:21 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Christophe Leroy <christophe.leroy@...roup.eu>
Cc: Andreas Kemnade <andreas@...nade.info>,
"linus.walleij@...aro.org" <linus.walleij@...aro.org>,
"brgl@...ev.pl" <brgl@...ev.pl>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
": Tony Lindgren" <tony@...mide.com>,
Aaro Koskinen <aaro.koskinen@....fi>,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>
Subject: Re: [PATCH] gpiolib: fix allocation of mixed dynamic/static GPIOs
On Thu, Apr 27, 2023 at 1:55 PM Christophe Leroy
<christophe.leroy@...roup.eu> wrote:
> Le 27/04/2023 à 12:46, Andy Shevchenko a écrit :
> > On Thu, Apr 27, 2023 at 1:37 PM Andreas Kemnade <andreas@...nade.info> wrote:
> >> On Thu, 27 Apr 2023 06:20:34 +0000
> >> Christophe Leroy <christophe.leroy@...roup.eu> wrote:
...
> >> I will send a v2 of this patch with refined logic.
> >
> > Actually it would be nice to integrate a warning (if we don't have it
> > yet) when adding a GPIO chip with a static allocation and which will
> > overlap the dynamic base. Can you add that into your v2?
> >
>
> At the time being we have a warning for all static allocations,
> allthough their has been some discussion about reverting it, see commit
> 502df79b8605 ("gpiolib: Warn on drivers still using static gpiobase
> allocation")
Ah, even better! Then no need to have a specific one, thanks!
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists