[PATCH 00/10] Prepare for GPMC driver conversion (w.r.t MTD)
Tony Lindgren
tony at atomide.com
Wed Jun 13 07:09:08 EDT 2012
Hi,
Sorry for the delay, had to do some fixes to get my GPMC testcase
working..
* Mohammed, Afzal <afzal at ti.com> [120612 03:01]:
> Hi Tony, Artem,
>
> On Thu, Jun 07, 2012 at 20:44:03, Mohammed, Afzal wrote:
>
> > > This series cleans up gpmc mtd interactions so that GPMC driver
> > > conversion which is going to happen shortly would happen smoothly
> > > by not creating much disturbance outside of arch/arm/*omap*/
> > >
> > > This series,
> > > 1. provides the ability for OMAP NAND driver to configure GPMC-NAND
> > > registers by NAND driver itself instead of using exported GPMC
> > > symbols
> > > 2. modifies GPMC to provide OMAP ONENAND & NAND drivers with GPMC
> > > allocated address space as resource
> > > 3. creates a fictitious GPMC interrupt chip and provide the clients
> > > with interrupts that could be handled using standard APIs (helps
> > > in removing the requirement for driver of peripheral connected to
> > > GPMC having the knowledge about GPMC interrupt handling). The
> > > only user is OMAP NAND driver, it has also been modified to take
> > > advantage of this
> > >
> > > This series has been made over 3.5-rc1
> >
> > Ping
>
> Please let me know your comments on this. This is a prerequisite for
> gpmc driver conversion series [1]
Looks good to me, made one comment to "mtd: nand: omap2: handle nand on gpmc"
patch. Maybe after that is fixed Artem can take a look and maybe ack
the two mtd related patches?
Regards,
Tony
> [1] http://www.mail-archive.com/linux-omap@vger.kernel.org/msg69897.html
>
> Regards
> Afzal
More information about the linux-mtd
mailing list