From: Tony Lindgren <tony@atomide.com>
To: Sukumar Ghorai <s-ghorai@ti.com>
Cc: Vimal Singh <vimalsingh@ti.com>,
linux-omap@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/4] omap3: nand: prefetch in irq mode support
Date: Mon, 2 Aug 2010 16:03:07 +0300 [thread overview]
Message-ID: <20100802130306.GL12293@atomide.com> (raw)
In-Reply-To: <1278996337-25172-2-git-send-email-s-ghorai@ti.com>
* Sukumar Ghorai <s-ghorai@ti.com> [100713 07:39]:
> This patch enable prefetch-irq mode for NAND.
<snip>
> --- a/arch/arm/mach-omap2/board-flash.c
> +++ b/arch/arm/mach-omap2/board-flash.c
> @@ -133,6 +133,7 @@ static struct omap_nand_platform_data board_nand_data = {
> .nand_setup = NULL,
> .gpmc_t = &nand_timings,
> .dma_channel = -1, /* disable DMA in OMAP NAND driver */
> + .gpmc_irq = GPMC_IRQ_NUMBER,
> .dev_ready = NULL,
> .devsize = 0, /* '0' for 8-bit, '1' for 16-bit device */
> };
> --- a/arch/arm/mach-omap2/include/mach/board-flash.h
> +++ b/arch/arm/mach-omap2/include/mach/board-flash.h
> @@ -19,6 +19,9 @@
> #define PDC_ONENAND 3
> #define DBG_MPDB 4
>
> +/* Interrupt number to the MPU Subsystem for GPMC */
> +#define GPMC_IRQ_NUMBER 20
> +
This does not look right for the IRQ. Please add it to the irqs.h and 34xx,
then set it dynamically during the init just like we handle the other
interrupt numbers.
This is because the irq numbers can change between omaps, like irqs-44xx.h
already has
#define OMAP44XX_IRQ_GPMC (20 + OMAP44XX_IRQ_GIC_START)
> @@ -130,6 +141,13 @@ struct omap_nand_info {
> unsigned long phys_base;
> struct completion comp;
> int dma_ch;
> + int gpmc_irq;
> + enum {
> + NAND_IO_READ = 0, /* read */
> + NAND_IO_WRITE, /* write */
> + } iomode;
> + u_char *buf;
> + int buf_len;
> };
These should probably be OMAP_NAND_IO_READ and OMAP_NAND_IO_WRITE?
Regards,
Tony
next prev parent reply other threads:[~2010-08-02 13:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 4:45 [PATCH v3 0/4] nand prefetch-irq support and ecc layout chanage Sukumar Ghorai
2010-07-13 4:45 ` [PATCH v3 1/4] omap3: nand: prefetch in irq mode support Sukumar Ghorai
2010-07-13 4:45 ` [PATCH v3 2/4] omap3: nand: configurable fifo threshold to gain the throughput Sukumar Ghorai
2010-07-13 4:45 ` [PATCH v3 3/4] omap: nand: ecc layout select from board file Sukumar Ghorai
2010-07-13 4:45 ` [PATCH v3 4/4] omap: nand: making ecc layout as compatible with romcode ecc Sukumar Ghorai
2010-08-02 13:03 ` Tony Lindgren [this message]
2010-08-02 13:39 ` [PATCH v3 1/4] omap3: nand: prefetch in irq mode support 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=20100802130306.GL12293@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=s-ghorai@ti.com \
--cc=vimalsingh@ti.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;
as well as URLs for NNTP newsgroup(s).