[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-gpio
Subject:    Re: [PATCH] gpiolib: fix allocation of mixed dynamic/static GPIOs
From:       Andy Shevchenko <andy.shevchenko () gmail ! com>
Date:       2023-04-27 11:01:21
Message-ID: CAHp75Vexy1p8E5VYj=kX9VPxAghzVwbh3ANvLVP4yrxkHZ+H7A () mail ! gmail ! com
[Download RAW message or body]

On Thu, Apr 27, 2023 at 1:55 PM Christophe Leroy
<christophe.leroy@csgroup.eu> wrote:
> Le 27/04/2023 à 12:46, Andy Shevchenko a écrit :
> > On Thu, Apr 27, 2023 at 1:37 PM Andreas Kemnade <andreas@kemnade.info> wrote:
> >> On Thu, 27 Apr 2023 06:20:34 +0000
> >> Christophe Leroy <christophe.leroy@csgroup.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
[prev in list] [next in list] [prev in thread] [next in thread]