From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 02/10] mach-u300: rewrite gpio driver, move to drivers/gpio
Date: Fri, 20 May 2011 02:50:22 +0100 [thread overview]
Message-ID: <20110520015022.GA3095@pulham.picochip.com> (raw)
In-Reply-To: <0D753D10438DA54287A00B027084269764D3045B3B@AUSP01VMBX24.collaborationhost.net>
On Thu, May 19, 2011 at 04:18:56PM -0500, H Hartley Sweeten wrote:
> On Thursday, May 19, 2011 12:12 PM, Sascha Hauer wrote:
> > On Thu, May 19, 2011 at 09:56:32PM +0800, Shawn Guo wrote:
> >> On Thu, May 19, 2011 at 02:21:27PM +0200, Linus Walleij wrote:
> >>> On Thu, May 19, 2011 at 10:56 AM, Shawn Guo <shawn.guo@freescale.com> wrote:
> >>>
> >>>> I start working on moving mxs gpio (arch/arm/mach-mxs/gpio.c) into
> >>>> driver/gpio, and I see the possibility to go a different approach
> >>>> from U300 one posted here.
> >>>
> >>> I've tried to figure out what relation the mail has to the U300 driver
> >>> but cannot find any, more than that it's moving a driver... Please
> >>> start a new mail thread.
> >>>
> >> I will post mxs-gpio driver once I get it done. Then please review
> >> the code and see the difference between mxs-gpio and u300-gpio,
> >> though these hardwares have something in common.
> >
> > I'm pretty sure they have something in common and even more that *all*
> > gpio drivers have something in common. I wonder if it really makes sense
> > to move the gpio driver to drivers/gpio without creating a common
> > mmio_gpio_chip beforehand. This can't be very hard.
>
> Jamie Iles (cc'ed) posted some patches that extended the basic_mmio_gpio
> driver so that it could be used as a library by other gpio drivers.
>
> Jamie, could you re-post that series to the linux-arm-kernel list for
> review?
Grant has applied these patches but I've put them in a public branch if
that's OK rather than reposting:
git://github.com/jamieiles/linux-2.6-ji.git gpio
Jamie
next prev parent reply other threads:[~2011-05-20 1:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 13:13 [PATCH 02/10] mach-u300: rewrite gpio driver, move to drivers/gpio Linus Walleij
2011-04-27 18:23 ` H Hartley Sweeten
2011-04-28 7:07 ` Linus Walleij
2011-04-28 7:10 ` Linus Walleij
2011-04-28 17:41 ` H Hartley Sweeten
2011-05-13 14:51 ` Linus Walleij
2011-05-19 8:56 ` Shawn Guo
2011-05-19 12:21 ` Linus Walleij
2011-05-19 13:56 ` Shawn Guo
2011-05-19 19:11 ` Sascha Hauer
2011-05-19 19:30 ` Nicolas Pitre
2011-05-20 3:18 ` Shawn Guo
2011-05-20 3:43 ` Kyungmin Park
2011-05-20 3:54 ` Nicolas Pitre
2011-05-19 21:18 ` H Hartley Sweeten
2011-05-20 1:50 ` Jamie Iles [this message]
2011-05-20 22:07 ` H Hartley Sweeten
2011-05-21 13:03 ` Jamie Iles
2011-05-20 7:01 ` Grant Likely
2011-05-20 7:47 ` Linus Walleij
[not found] ` <BANLkTi=poU17RqAzp28CPjWHrN_+aFiyag@mail.gmail.com>
2011-05-19 11:38 ` Barry Song
2011-05-19 12:25 ` Linus Walleij
2011-05-19 12:35 ` Barry Song
2011-05-19 13:17 ` Linus Walleij
2011-05-19 14:05 ` Barry Song
2011-05-20 6:58 ` Grant Likely
2011-05-20 6:52 ` Grant Likely
2011-05-20 7:46 ` Linus Walleij
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=20110520015022.GA3095@pulham.picochip.com \
--to=jamie@jamieiles.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).