public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Poirier <mathieu.poirier@canonical.com>
To: tony@atomide.com
Cc: linux-omap@vger.kernel.org,
	Mathieu Poirier <mathieu.poirier@canonical.com>
Subject: [PATCH] Initializing gpmc before accessing flash
Date: Wed, 11 Aug 2010 08:41:30 -0600	[thread overview]
Message-ID: <1281537690.1512.2.camel@black> (raw)

>From b12de3010763a8c047eefd2eb9296eb68157b07e Mon Sep 17 00:00:00 2001
From: Mathieu J. Poirier <mathieu.poirier@canonical.com>
Date: Tue, 10 Aug 2010 17:14:25 -0400
Subject: [PATCH] Initializing gpmc before accessing flash

Adding initialization of the General Purpose Memory Controller
(gpmc) in 'omap3beagle_flash_init'.

The gpmc init was decoupled from nand flash init and
got its own init function.  This change was not reflected in
'omap3beagle_flash_init' resulting in a lookup failure when
probing for flash.

BugLink: https://bugs/launchpad.net/bugs/608266

Signed-off-by: Mathieu Poirier <mathieu.poirier@canonical.com>
---
 arch/arm/mach-omap2/board-omap3beagle.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/arch/arm/mach-omap2/board-omap3beagle.c b/arch/arm/mach-omap2/board-omap3beagle.c
index 7a1b351..e1203a4 100644
--- a/arch/arm/mach-omap2/board-omap3beagle.c
+++ b/arch/arm/mach-omap2/board-omap3beagle.c
@@ -466,6 +466,7 @@ static void __init omap3beagle_flash_init(void)
 		omap3beagle_nand_data.gpmc_cs_baseaddr = (void *)
 			(gpmc_base_add + GPMC_CS0_BASE + nandcs * GPMC_CS_SIZE);
 		omap3beagle_nand_data.gpmc_baseaddr = (void *) (gpmc_base_add);
+               gpmc_nand_init(&omap3beagle_nand_data);
 
 		printk(KERN_INFO "Registering NAND on CS%d\n", nandcs);
 		if (platform_device_register(&omap3beagle_nand_device) < 0)
-- 
1.7.0.4




             reply	other threads:[~2010-08-11 14:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-11 14:41 Mathieu Poirier [this message]
2010-08-12  5:21 ` [PATCH] Initializing gpmc before accessing flash Ghorai, Sukumar

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=1281537690.1512.2.camel@black \
    --to=mathieu.poirier@canonical.com \
    --cc=linux-omap@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox