[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131206132405.GC30960@ulmo.nvidia.com>
Date: Fri, 6 Dec 2013 14:24:06 +0100
From: Thierry Reding <thierry.reding@...il.com>
To: Mark Brown <broonie@...nel.org>
Cc: Milo Kim <milo.kim@...com>, Lee Jones <lee.jones@...aro.org>,
Samuel Ortiz <sameo@...ux.intel.com>,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-pwm@...r.kernel.org, Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH v4 0/4] LP3943 MFD driver for a GPIO expander and a PWM
generator
On Thu, Dec 05, 2013 at 09:43:41PM +0000, Mark Brown wrote:
> On Wed, Dec 04, 2013 at 11:34:32AM +0100, Thierry Reding wrote:
> > On Wed, Sep 25, 2013 at 01:22:55PM +0900, Milo Kim wrote:
>
> > > mfd: add LP3943 MFD driver
> > > gpio: add LP3943 I2C GPIO expander driver
> > > pwm: add LP3943 PWM driver
> > > Documentation: add LP3943 DT bindings and document
>
> > I suspect that given the build-time dependencies Lee may want to take
> > all four patches through the MFD tree, so I've acked the PWM parts.
>
> FWIW this isn't an issue with new MFDs - since the function drivers will
> depend on the core driver it's not possible to enable them in Kconfig
> until the core driver is also merged and you don't get bisect issues.
Right. I hadn't thought about that. Thanks for mentioning it.
Thierry
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists