[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110402025901.GB13341@sirena.org.uk>
Date: Sat, 2 Apr 2011 03:59:02 +0100
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Nicolas Pitre <nico@...xnic.net>
Cc: Arnd Bergmann <arnd@...db.de>, Detlef Vollmann <dv@...lmann.ch>,
Ingo Molnar <mingo@...e.hu>, david@...g.hm,
Russell King - ARM Linux <linux@....linux.org.uk>,
Tony Lindgren <tony@...mide.com>,
Catalin Marinas <catalin.marinas@....com>,
lkml <linux-kernel@...r.kernel.org>,
"H. Peter Anvin" <hpa@...or.com>,
David Brown <davidb@...eaurora.org>,
linux-omap@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [GIT PULL] omap changes for v2.6.39 merge window
On Fri, Apr 01, 2011 at 03:54:47PM -0400, Nicolas Pitre wrote:
> 1) GPIO drivers
> As Linus observed, in the majority of the cases GPIOs are accessed
> through simple memory-mapped registers. Some have absolute state
> registers, the others have separate clear/set registers. Suffice to
> create two generic GPIO drivers each covering those two common cases,
> and those generic drivers would simply register with the higher level
> gpiolib code, and all the board code would have to do is to provide
> the data for those GPIOs (register offsets, number of GPIOs, etc.).
> Whether this data eventually comes from DT is an orthogonal issue.
For this case we actually already have the basic_mmio_gpio driver in
tree, we should be pushing for wider usage of that.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists