From: Thierry Reding <thierry.reding@gmail.com>
To: Milo Kim <milo.kim@ti.com>
Cc: Lee Jones <lee.jones@linaro.org>,
Samuel Ortiz <sameo@linux.intel.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-pwm@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v4 0/4] LP3943 MFD driver for a GPIO expander and a PWM generator
Date: Wed, 4 Dec 2013 11:34:32 +0100 [thread overview]
Message-ID: <20131204103431.GC26589@ulmo.nvidia.com> (raw)
In-Reply-To: <1380082975-6022-1-git-send-email-milo.kim@ti.com>
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
On Wed, Sep 25, 2013 at 01:22:55PM +0900, Milo Kim wrote:
> LP3943 is an integrated device capable of driving 16 output channels.
> It can be used for GPIO expander and PWM generators.
> LP3493 registers are controlled via the I2C interface.
>
> This patch-set consists of four parts - MFD, GPIO, PWM and documents.
>
> Update from v3 to v4:
> Move the driver description from the documentation to the MFD driver file.
>
> Milo Kim (4):
> 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.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-12-04 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 4:22 [PATCH v4 0/4] LP3943 MFD driver for a GPIO expander and a PWM generator Milo Kim
2013-12-03 23:27 ` Milo Kim
2013-12-04 8:05 ` Lee Jones
2013-12-04 10:34 ` Thierry Reding [this message]
2013-12-04 10:50 ` Lee Jones
2013-12-05 21:43 ` Mark Brown
2013-12-06 13:24 ` Thierry Reding
2013-12-06 16:24 ` Lee Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131204103431.GC26589@ulmo.nvidia.com \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=milo.kim@ti.com \
--cc=sameo@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).