From: Tony Lindgren <tony@atomide.com>
To: Vimal Singh <vimal.newwork@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH v2 1/3] OMAP: ZOOM: Introducing 'board-zoom-flash.c'
Date: Wed, 17 Feb 2010 16:40:51 -0800 [thread overview]
Message-ID: <20100218004051.GJ21755@atomide.com> (raw)
In-Reply-To: <ce9ab5791002130142p7f57ce1bwe33a650e3de3464d@mail.gmail.com>
* Vimal Singh <vimal.newwork@gmail.com> [100213 01:40]:
> On Fri, Feb 12, 2010 at 2:49 AM, Tony Lindgren <tony@atomide.com> wrote:
> > * Tony Lindgren <tony@atomide.com> [100211 12:43]:
> >> * Vimal Singh <vimal.newwork@gmail.com> [100210 21:16]:
> >> > From: Vimal Singh <vimalsingh@ti.com>
> >> >
> >> > This patch adds 'board-zoom-flash.c', which could be utilized
> >> > by boards similar to ZOOM2. (For ex: LDP, ZOOM2, ZOOM3).
> >> >
> >> > 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 | 85 +++++++++++++++++++++++++
> >> > arch/arm/mach-omap2/include/mach/board-zoom.h | 11 +++
> >> > 2 files changed, 96 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..f2328a4
> >> > --- /dev/null
> >> > +++ b/arch/arm/mach-omap2/board-zoom-flash.c
> >> > @@ -0,0 +1,85 @@
> >> > +/*
> >> > + * board-zoom-flash.c
> >> > + *
> >> > + * Copyright (C) 2009 Texas Instruments Inc.
> >> > + * Vimal Singh <vimalsingh@ti.com>
> >> > + *
> >> > + * This program is free software; you can redistribute it and/or modify
> >> > + * it under the terms of the GNU General Public License version 2 as
> >> > + * published by the Free Software Foundation.
> >> > + */
> >> > +
> >> > +#include <linux/kernel.h>
> >> > +#include <linux/delay.h>
> >> > +#include <linux/platform_device.h>
> >> > +#include <linux/mtd/nand.h>
> >> > +#include <linux/types.h>
> >> > +#include <linux/io.h>
> >> > +
> >> > +#include <asm/mach/flash.h>
> >> > +#include <plat/board.h>
> >> > +#include <plat/gpmc.h>
> >> > +#include <plat/nand.h>
> >> > +
> >> > +#include <mach/board-zoom.h>
> >> > +
> >> > +#if defined(CONFIG_MTD_NAND_OMAP2) || \
> >> > + defined(CONFIG_MTD_NAND_OMAP2_MODULE)
> >> > +
> >> > +/* Note that all values in this struct are in nanoseconds */
> >> > +static struct gpmc_timings nand_timings = {
> >> > +
> >> > + .sync_clk = 0,
> >> > +
> >> > + .cs_on = 0,
> >> > + .cs_rd_off = 36,
> >> > + .cs_wr_off = 36,
> >> > +
> >> > + .adv_on = 6,
> >> > + .adv_rd_off = 24,
> >> > + .adv_wr_off = 36,
> >> > +
> >> > + .we_off = 30,
> >> > + .oe_off = 48,
> >> > +
> >> > + .access = 54,
> >> > + .rd_cycle = 72,
> >> > + .wr_cycle = 72,
> >> > +
> >> > + .wr_access = 30,
> >> > + .wr_data_mux_bus = 0,
> >> > +};
> >> > +
> >> > +/* NAND chip access: 16 bit */
> >> > +static struct omap_nand_platform_data zoom_nand_data = {
> >> > + .nand_setup = NULL,
> >> > + .gpmc_t = &nand_timings,
> >> > + .dma_channel = -1, /* disable DMA in OMAP NAND driver */
> >> > + .dev_ready = NULL,
> >> > + .devsize = 1, /* '0' for 8-bit, '1' for 16-bit device */
> >> > +};
> >> > +
> >> > +/**
> >> > + * zoom_flash_init - Identify devices connected to GPMC and register.
> >> > + *
> >> > + * @return - void.
> >> > + */
> >> > +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);
> >>
> >> The gpmc_baseaddr and gpmc_cs_baseaddr should no longer be
> >> needed with gpmc-nand.c, right?
>
> As said earlier too these are needed by 'nand/omap2.c' driver not for
> gpmc.-nand.c, we still need to pass these.
Right..
> >
> > Yeah.. For now, I suggest you set the gpmc_baseaddr and
> > gpmc_cs_baseaddr in gpmc_nand_init() based on the results from
> > gpmc_cs_request.
> >
> > That will allow us to remove the insane hardcoded gpmc virtual
> > addresses from all board-*.c files.
>
> OK
This change you can already make without changing the driver.
> >
> > And then we can finally fix gpmc-nand.c driver not to go tinker
> You mean omap2.c nand driver?
>
> > with the GPMC registers directly. All of that should be in
> > gpmc-nand.c using gpmc.c. The driver should be just a generic
> > NAND driver.
>
> Yes, but that will take complete clean-up of omap2.c nand driver by
> moving all functions accessing GPMC registers from 'nand/omap2.c' to
> 'gpmc-nand.c'. And we can take that work later.
> Once everything is working fine and is at proper place, clean-up will
> have more visibility.
>
> IMHO, you can still take patches for now. As, this is how already done
> for sdp boards too.
I'd rather get things fixed rather than merge obviously broken stuff.
The thing is that unless it's fixed to start with, nobody bothers to
fix it afterwards and then I need to deal with cleaning up the mess.
Regards,
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
next prev parent reply other threads:[~2010-02-18 0:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 5:19 [PATCH v2 1/3] OMAP: ZOOM: Introducing 'board-zoom-flash.c' Vimal Singh
2010-02-11 20:47 ` Tony Lindgren
2010-02-11 21:19 ` Tony Lindgren
2010-02-13 9:42 ` Vimal Singh
2010-02-18 0:40 ` Tony Lindgren [this message]
[not found] <2A3DCF3DA181AD40BDE86A3150B27B6B030D3C8C1F@dbde02.ent.ti.com>
2010-04-05 5:45 ` 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=20100218004051.GJ21755@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox