From: Tony Lindgren <tony@atomide.com>
To: "Mohammed, Afzal" <afzal@ti.com>
Cc: "artem.bityutskiy@linux.intel.com"
<artem.bityutskiy@linux.intel.com>,
"ivan.djelic@parrot.com" <ivan.djelic@parrot.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH 00/10] Prepare for GPMC driver conversion (w.r.t MTD)
Date: Wed, 13 Jun 2012 04:09:08 -0700 [thread overview]
Message-ID: <20120613110908.GJ12766@atomide.com> (raw)
In-Reply-To: <C8443D0743D26F4388EA172BF4E2A7A93E997FF8@DBDE01.ent.ti.com>
Hi,
Sorry for the delay, had to do some fixes to get my GPMC testcase
working..
* Mohammed, Afzal <afzal@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
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: "Mohammed, Afzal" <afzal@ti.com>
Cc: "artem.bityutskiy@linux.intel.com"
<artem.bityutskiy@linux.intel.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"ivan.djelic@parrot.com" <ivan.djelic@parrot.com>
Subject: Re: [PATCH 00/10] Prepare for GPMC driver conversion (w.r.t MTD)
Date: Wed, 13 Jun 2012 04:09:08 -0700 [thread overview]
Message-ID: <20120613110908.GJ12766@atomide.com> (raw)
In-Reply-To: <C8443D0743D26F4388EA172BF4E2A7A93E997FF8@DBDE01.ent.ti.com>
Hi,
Sorry for the delay, had to do some fixes to get my GPMC testcase
working..
* Mohammed, Afzal <afzal@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
next prev parent reply other threads:[~2012-06-13 11:09 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 6:45 [PATCH 00/10] Prepare for GPMC driver conversion (w.r.t MTD) Afzal Mohammed
2012-06-04 6:45 ` Afzal Mohammed
2012-06-04 6:46 ` [PATCH 01/10] ARM: OMAP2+: gpmc: update nand register helper Afzal Mohammed
2012-06-04 6:46 ` Afzal Mohammed
2012-06-04 6:46 ` [PATCH 02/10] ARM: OMAP2+: gpmc-nand: update gpmc-nand regs Afzal Mohammed
2012-06-04 6:46 ` Afzal Mohammed
2012-06-04 6:46 ` [PATCH 03/10] mtd: nand: omap2: handle nand on gpmc Afzal Mohammed
2012-06-04 6:46 ` Afzal Mohammed
2012-06-13 10:45 ` Tony Lindgren
2012-06-13 10:45 ` Tony Lindgren
2012-06-04 6:46 ` [PATCH 04/10] ARM: OMAP2+: gpmc-nand: update resource with memory Afzal Mohammed
2012-06-04 6:46 ` Afzal Mohammed
2012-06-04 6:46 ` [PATCH 05/10] ARM: OMAP2+: gpmc-onenand: provide memory as resource Afzal Mohammed
2012-06-04 6:46 ` Afzal Mohammed
2012-06-04 6:46 ` [PATCH 06/10] mtd: nand: omap2: obtain memory from resource Afzal Mohammed
2012-06-04 6:46 ` Afzal Mohammed
2012-06-04 6:47 ` [PATCH 07/10] mtd: onenand: " Afzal Mohammed
2012-06-04 6:47 ` Afzal Mohammed
2012-06-04 6:47 ` [PATCH 08/10] ARM: OMAP2+: gpmc: Modify interrupt handling Afzal Mohammed
2012-06-04 6:47 ` Afzal Mohammed
2012-06-04 6:47 ` [PATCH 09/10] ARM: OMAP2+: gpmc-nand: Modify Interrupt handling Afzal Mohammed
2012-06-04 6:47 ` Afzal Mohammed
2012-06-04 6:47 ` [PATCH 10/10] mtd: nand: omap2: use gpmc provided irqs Afzal Mohammed
2012-06-04 6:47 ` Afzal Mohammed
2012-06-07 15:14 ` [PATCH 00/10] Prepare for GPMC driver conversion (w.r.t MTD) Mohammed, Afzal
2012-06-12 9:57 ` Mohammed, Afzal
2012-06-13 11:09 ` Tony Lindgren [this message]
2012-06-13 11:09 ` Tony Lindgren
2012-06-13 11:12 ` Mohammed, Afzal
2012-06-13 11:12 ` Mohammed, Afzal
2012-06-14 16:01 ` Mohammed, Afzal
2012-06-14 16:01 ` Mohammed, Afzal
2012-06-14 16:17 ` Artem Bityutskiy
2012-06-14 16:17 ` Artem Bityutskiy
2012-06-14 16:17 ` Mohammed, Afzal
2012-06-14 16:17 ` Mohammed, Afzal
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=20120613110908.GJ12766@atomide.com \
--to=tony@atomide.com \
--cc=afzal@ti.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=ivan.djelic@parrot.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.