public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "Kim, Milo" <Milo.Kim@ti.com>,
	"Samuel Ortiz (sameo@linux.intel.com)" <sameo@linux.intel.com>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-pwm@vger.kernel.org" <linux-pwm@vger.kernel.org>
Subject: Re: [PATCH v2 2/4] gpio: add LP3943 I2C GPIO expander driver
Date: Thu, 8 Aug 2013 10:03:55 +0100	[thread overview]
Message-ID: <20130808090355.GA14515@lee--X1> (raw)
In-Reply-To: <CACRpkdZmMh9MwFQKhZPUZ0dKXQ=8Ear_danBSgOD=PYQUk5QxA@mail.gmail.com>

On Wed, 07 Aug 2013, Linus Walleij wrote:

> On Tue, Jul 30, 2013 at 2:42 AM, Kim, Milo <Milo.Kim@ti.com> wrote:
> 
> > This is one of LP3943 MFD driver.
> > LP3943 is configurable as a GPIO expander, up to 16 GPIOs.
> >
> > * Application note: how to configure LP3943 as a GPIO expander
> >   http://www.ti.com/lit/an/snva287a/snva287a.pdf
> >
> > * Supported GPIO controller operations
> >   request, free, direction_input, direction_output, get and set
> >
> > * GPIO direction register not supported
> >   LP3943 doesn't have the GPIO direction register. It only provides input and
> >   output status registers.
> >   So, private data for the direction should be handled manually.
> >   This variable is updated whenever the direction is changed and
> >   used in 'get' operation.
> >
> > * Pin assignment
> >   A driver data, 'pin_used' is checked when a GPIO is requested.
> >   If the GPIO is already assigned, then returns as failure.
> >   If the GPIO is available, 'pin_used' is set.
> >   When the GPIO is not used anymore, then it is cleared.
> >   It is defined as unsigned long type for atomic bit operation APIs,
> >   but only LSB 16bits are used because LP3943 has 16 outputs.
> >
> > Cc: Linus Walleij <linus.walleij@linaro.org>
> > Signed-off-by: Milo Kim <milo.kim@ti.com>
> > ---
> > * Patch v2
> >   Use bitops macros for bit manipulations.
> >   Support device tree structure for the GPIO controller.
> >   Add request() and free() for the pin assignment.
> 
> This adresses all my concerns, nice driver.
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> 
> I guess this will be merged through the MFD tree along
> with the MFD core patch? That needs to go in first anyway.

That's fine, but first:

1/4 Needs Linus to review
4/4 Needs Thierry's PWM Ack

After that please send v3 with Linus' Rev-By on this patch.

-- 
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

      reply	other threads:[~2013-08-08  9:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30  0:42 [PATCH v2 2/4] gpio: add LP3943 I2C GPIO expander driver Kim, Milo
2013-08-07 18:49 ` Linus Walleij
2013-08-08  9:03   ` Lee Jones [this message]

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=20130808090355.GA14515@lee--X1 \
    --to=lee.jones@linaro.org \
    --cc=Milo.Kim@ti.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=sameo@linux.intel.com \
    --cc=thierry.reding@gmail.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