Hi, On Thu 12 Sep 19, 10:17, Linus Walleij wrote: > On Tue, Sep 10, 2019 at 4:29 PM Paul Kocialkowski > <paul.kocialkowski@xxxxxxxxxxx> wrote: > > > The LogiCVC display hardware block comes with GPIO capabilities > > that must be exposed separately from the main driver (as GPIOs) for > > use with regulators and panels. A syscon is used to share the same > > regmap across the two drivers. > > > > Since the GPIO capabilities are pretty simple, add them to the syscon > > GPIO driver. > > > > Signed-off-by: Paul Kocialkowski <paul.kocialkowski@xxxxxxxxxxx> > > I'm fine with this for now, but the gpio-syscon driver is now growing > big and when you use it you are getting support for a whole bunch > of systems you're not running on included in your binary. > > We need to think about possibly creating drivers/gpio/syscon > and split subdrivers into separate files and config options > so that people can slim down to what they actually need. Thanks for the review! I understand your concern about more devices getting pulled-in and built unconditionally. Though I do like the idea of having a single driver for only exposing the GPIO part of bigger components instead of specific drivers with < 100 lines of useful code. Maybe a first step would be to introduce Kconfig options for each device and ifdef around in the code, as to solve the "built unconditionally" aspect? Either way, I'll send v2 still adding my driver to gpio-syscon but feel free to have me in the loop when that driver needs to be changed. > > + *bit = 1 << offset; > > Please do this: > > #include <linux/bits.h> > > *bit = BIT(offset); Sure thing and sorry I missed that, thanks! Cheers, Paul -- Paul Kocialkowski, Bootlin Embedded Linux and kernel engineering https://bootlin.com
Attachment:
signature.asc
Description: PGP signature
