From: Jamie Iles <jamie@jamieiles.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: Jamie Iles <jamie@jamieiles.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
grant.likely@secretlab.ca
Subject: Re: [RFC PATCH 0/3] Use basic_mmio_gpio to implement a generic gpio chip
Date: Thu, 12 May 2011 23:21:57 +0100 [thread overview]
Message-ID: <20110512222157.GH8718@pulham.picochip.com> (raw)
In-Reply-To: <0D753D10438DA54287A00B027084269764D2D09197@AUSP01VMBX24.collaborationhost.net>
Hi Hartley,
On Thu, May 12, 2011 at 12:35:06PM -0500, H Hartley Sweeten wrote:
> On Wed May 05 2011, Jamie Iles wrote:
> > This series is based on my earlier set of GPIO patches[1] to extend the
> > basic_mmio_driver to be used as a library to implement a more generic gpio
> > chip as initially implemented by Anton Vorontsov[2].
> >
> > I've modified Anton's patch slightly to allow the bgpio_chip to be embedded
> > into another structure and converted two drivers over - bt8xxgpio and
> > langwell. bt8xxgpio seems to play nicely, but langwell not so much as it
> > didn't previously use a gpio_chip per bank but it is a nice illustration.
> >
> > Note that this is the same set of patches as attached in "Re: [PATCHv3 0/7]
> > gpio: extend basic_mmio_gpio for different controllers" but reposted as a set
> > of patches for convenience.
> >
> > 1. http://article.gmane.org/gmane.linux.kernel/1124700
> > 2. http://lkml.org/lkml/2011/4/19/401
> >
> > Jamie Iles (3):
> > basic_mmio_gpio: split into a gpio library and platform device
> > gpio/bt8xxgpio: convert to use basic_mmio_gpio library
> > gpio/langwell: convert to use basic_mmio_gpio library
> >
> > drivers/gpio/Kconfig | 8 +
> > drivers/gpio/Makefile | 1 +
> > drivers/gpio/basic_mmio_gpio.c | 317 +++++++++++++++++++++------------------
> > drivers/gpio/bt8xxgpio.c | 119 +++------------
> > drivers/gpio/langwell_gpio.c | 253 +++++++++++++++----------------
> > include/linux/basic_mmio_gpio.h | 55 +++++++
> > 6 files changed, 381 insertions(+), 372 deletions(-)
>
> Hello Jamie,
>
> I was wondering on the status of this patch series, and Anton's for that matter.
>
> I think I can convert the ep93xx gpio support to use this basic_mmio_gpio library
> but would like to make sure I have seen all the relevant patches. Is there any
> plan on someone getting this into linux-next?
I'm not too sure - I think Grant has taken the patches that this was
dependent on, and there is still the issue that both yourself and Anton
noticed (not actually adding the gpio_chip [Doh]), but other than that I
haven't seen any other feedback.
If this made a positive difference for ep93xx then I'm sure this would
help!
Jamie
next prev parent reply other threads:[~2011-05-12 22:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 17:35 H Hartley Sweeten
2011-05-12 22:21 ` Jamie Iles [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-04 15:07 Jamie Iles
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=20110512222157.GH8718@pulham.picochip.com \
--to=jamie@jamieiles.com \
--cc=grant.likely@secretlab.ca \
--cc=hartleys@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®