All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mohammed, Afzal" <afzal@ti.com>
To: "Hunter, Jon" <jon-hunter@ti.com>
Cc: "tony@atomide.com" <tony@atomide.com>,
	"paul@pwsan.com" <paul@pwsan.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH v4 1/3] ARM: OMAP2+: nand: unify init functions
Date: Tue, 26 Jun 2012 08:35:10 +0000	[thread overview]
Message-ID: <C8443D0743D26F4388EA172BF4E2A7A93E99F02D@DBDE01.ent.ti.com> (raw)
In-Reply-To: <4FE883F5.6040806@ti.com>

Hi Jon,

On Mon, Jun 25, 2012 at 20:59:57, Hunter, Jon wrote:
> On 06/22/2012 04:00 AM, Afzal Mohammed wrote:
> > Helper function for updating nand platform data has been
> > added the capability to take timing structure arguement.
> > Usage of omap_nand_flash_init() has been replaced by modifed
> > one, omap_nand_flash_init was doing things similar to
> > board_nand_init except that NAND CS# were being acquired
> > based on bootloader setting. As CS# is hardwired for a given
> > board, acquiring gpmc CS# has been removed, and updated with
> > the value on board.
> > 
> > NAND CS# used in beagle board was found to be CS0.
> > Thomas Weber <thomas.weber.linux@googlemail.com> reported
> > that value of devkit8000 to be CS0. Overo board was found
> > to be using CS0 based on u-boot, while google grep says
> > omap3touchbook too has CS0.

> Reviewed-by: Jon Hunter <jon-hunter@ti.com>

Thanks,
Afzal

WARNING: multiple messages have this Message-ID (diff)
From: afzal@ti.com (Mohammed, Afzal)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/3] ARM: OMAP2+: nand: unify init functions
Date: Tue, 26 Jun 2012 08:35:10 +0000	[thread overview]
Message-ID: <C8443D0743D26F4388EA172BF4E2A7A93E99F02D@DBDE01.ent.ti.com> (raw)
In-Reply-To: <4FE883F5.6040806@ti.com>

Hi Jon,

On Mon, Jun 25, 2012 at 20:59:57, Hunter, Jon wrote:
> On 06/22/2012 04:00 AM, Afzal Mohammed wrote:
> > Helper function for updating nand platform data has been
> > added the capability to take timing structure arguement.
> > Usage of omap_nand_flash_init() has been replaced by modifed
> > one, omap_nand_flash_init was doing things similar to
> > board_nand_init except that NAND CS# were being acquired
> > based on bootloader setting. As CS# is hardwired for a given
> > board, acquiring gpmc CS# has been removed, and updated with
> > the value on board.
> > 
> > NAND CS# used in beagle board was found to be CS0.
> > Thomas Weber <thomas.weber.linux@googlemail.com> reported
> > that value of devkit8000 to be CS0. Overo board was found
> > to be using CS0 based on u-boot, while google grep says
> > omap3touchbook too has CS0.

> Reviewed-by: Jon Hunter <jon-hunter@ti.com>

Thanks,
Afzal

  reply	other threads:[~2012-06-26  8:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-22  9:00 [PATCH v4 0/3] Prepare for GPMC driver conversion Afzal Mohammed
2012-06-22  9:00 ` Afzal Mohammed
2012-06-22  9:00 ` [PATCH v4 1/3] ARM: OMAP2+: nand: unify init functions Afzal Mohammed
2012-06-22  9:00   ` Afzal Mohammed
2012-06-25 15:29   ` Jon Hunter
2012-06-25 15:29     ` Jon Hunter
2012-06-26  8:35     ` Mohammed, Afzal [this message]
2012-06-26  8:35       ` Mohammed, Afzal
2012-06-22  9:00 ` [PATCH v4 2/3] ARM: OMAP2+: gpmc: handle additional timings Afzal Mohammed
2012-06-22  9:00   ` Afzal Mohammed
2012-06-22  9:01 ` [PATCH v4 3/3] ARM: OMAP2+: onenand: prepare for gpmc driver migration Afzal Mohammed
2012-06-22  9:01   ` Afzal Mohammed
2012-06-25 16:12   ` Jon Hunter
2012-06-25 16:12     ` Jon Hunter
2012-06-26  8:29     ` Mohammed, Afzal
2012-06-26  8:29       ` Mohammed, Afzal
2012-06-26 14:39       ` Jon Hunter
2012-06-26 14:39         ` Jon Hunter
2012-06-26 14:56         ` Jon Hunter
2012-06-26 14:56           ` Jon Hunter
2012-06-27  6:53           ` Mohammed, Afzal
2012-06-27  6:53             ` 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=C8443D0743D26F4388EA172BF4E2A7A93E99F02D@DBDE01.ent.ti.com \
    --to=afzal@ti.com \
    --cc=jon-hunter@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=tony@atomide.com \
    /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.