On Thu, Sep 7, 2017 at 11:30 PM, <woojung....@microchip.com> wrote: >> If someone is using GPIO descriptors with GPIO disabled, i.e. calling >> gpiod_get() and friends, this is very likely to be a bug, and what >> the driver wants to do is: >> >> depends on GPIOLIB >> >> or >> >> select GPIOLIB >> >> in Kconfig. The whole optional thing is mainly a leftover from when it >> was possible to have a local implementation of the GPIOLIB API in >> some custom header file, noone sane should be doing that anymore, >> and if they do, they can very well face the warnings. >> >> If someone is facing a lot of WARN_ON() messages to this, it is a clear >> indication that they need to fix their Kconfig and in that case it is proper. > Linus & Andrew, > > I knew that it is already in David's pulling request. > Configuring GPIOLIB is the right solution even if platform doesn't use it?
I guess? "Platform doesn't use it" what does that mean? Does it mean it does not call the APIs of the GPIOLIB, does it mean it doesn't have a GPIO driver at probe (but may have one by having it probed from a module) or does it mean the platform can never have it? If it calls the APIs, it is using it. Yours, Linus Walleij
