From: Tony Lindgren <tony@atomide.com>
To: Grazvydas Ignotas <notasas@gmail.com>
Cc: Vimal Singh <vimal.newwork@gmail.com>, linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/4]: OMAP: ZOOM: Introducing 'board-zoom-flash.c' for NAND init in ZOOM boards
Date: Fri, 4 Dec 2009 14:19:18 -0800 [thread overview]
Message-ID: <20091204221917.GM24013@atomide.com> (raw)
In-Reply-To: <6ed0b2680912030806n5bd6a358g640ec5e93accc5a8@mail.gmail.com>
* Grazvydas Ignotas <notasas@gmail.com> [091203 08:05]:
> On Thu, Dec 3, 2009 at 4:15 PM, Vimal Singh <vimal.newwork@gmail.com> wrote:
> > From 948584f4157a9eb99ba085968d23add28cbfd160 Mon Sep 17 00:00:00 2001
> > From: Vimal Singh <vimalsingh@ti.com>
> > Date: Tue, 1 Dec 2009 11:36:56 +0530
> > Subject: [PATCH] OMAP: ZOOM: Introducing 'board-zoom-flash.c'
> >
> > This patch adds 'board-zoom-flash.c', which could be utilized
> > by boards similar to ZOOM2. (For ex: LDP, ZOOM2, ZOOM3).
>
> So it's not really zoom specific, i.e. can be used by other boards
> with NAND like beagleboard and pandora? If that's the case, perhaps
> the file could be named something like omap3-nand.c or simply just
> nand.c .
>
> >
> > This does initialization for NAND device based on the 'cs' number
> > and partition information passed from board file (ex: board-zoom2.c).
> >
> > Signed-off-by: Vimal Singh <vimalsingh@ti.com>
> > ---
> > arch/arm/mach-omap2/board-zoom-flash.c | 59 +++++++++++++++++++++++++
> > arch/arm/mach-omap2/include/mach/board-zoom.h | 11 +++++
> > 2 files changed, 70 insertions(+), 0 deletions(-)
> > create mode 100644 arch/arm/mach-omap2/board-zoom-flash.c
> >
> > diff --git a/arch/arm/mach-omap2/board-zoom-flash.c
> > b/arch/arm/mach-omap2/board-zoom-flash.c
> > new file mode 100644
> > index 0000000..b3e66ca
> > --- /dev/null
> > +++ b/arch/arm/mach-omap2/board-zoom-flash.c
<snip>
> > +void __init zoom_flash_init(struct flash_partitions zoom_nand_parts[], int cs)
> > +{
> > + u32 gpmc_base_add = OMAP34XX_GPMC_VIRT;
> > +
> > + zoom_nand_data.cs = cs;
> > + zoom_nand_data.parts = zoom_nand_parts[0].parts;
> > + zoom_nand_data.nr_parts = zoom_nand_parts[0].nr_parts;
> > + zoom_nand_data.gpmc_baseaddr = (void *)(gpmc_base_add);
> > + zoom_nand_data.gpmc_cs_baseaddr = (void *)(gpmc_base_add +
> > + GPMC_CS0_BASE +
> > + cs * GPMC_CS_SIZE);
> > + gpmc_nand_init(&zoom_nand_data);
> > +}
And here too you should use gpmc_cs_request().
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-12-04 22:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 14:15 [PATCH 1/4]: OMAP: ZOOM: Introducing 'board-zoom-flash.c' for NAND init in ZOOM boards Vimal Singh
2009-12-03 16:06 ` Grazvydas Ignotas
2009-12-04 22:19 ` Tony Lindgren [this message]
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=20091204221917.GM24013@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=notasas@gmail.com \
--cc=vimal.newwork@gmail.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.