From: Mark Underwood <basicmark@yahoo.com>
To: linux-mtd@lists.infradead.org
Subject: Re: NAND driver
Date: Tue, 26 Feb 2008 09:04:27 +0000 (GMT) [thread overview]
Message-ID: <631124.21101.qm@web36909.mail.mud.yahoo.com> (raw)
In-Reply-To: <751269.90312.qm@web36904.mail.mud.yahoo.com>
--- Mark Underwood <basicmark@yahoo.com> wrote:
> Im writing a NAND driver for an ASIC. The NAND controller has been designed to handle page read
> &
> writes with little SW intervention using interrupts or DMA, so I plan to implement the
> write_page_raw & read_page_raw functions.
> However, looking through nand_base.c it looks like not all NAND access go through these
> functions
> so to start with I have implemented the cmd_ctrl function & supplied the IO_ADDR_R & IO_ADDR_W
> address with the thinking that these would be a fall back when the access doesn't go through the
> raw functions.
> Unfortunately it seems the single write functionality of the controller is broken. The page
> read
> & write functionality only allow me to work in 512byte blocks so I can't write OOB that way. Can
> you confirm that there are cases where OOB is written separately and if so do you have any
> suggestions for getting around this problem?
>
> Many thanks,
>
> Mark
>
I forgot to say that I'm working on a 2.6.21.1 kernel.
After some pondering I managed to implement the single write functionality by abusing the command
fifo and playing with GPIO pins.
Looking through nand_base.c I notice that although I can pass in *_page_raw operations in the
nand_chip structure they are not used in the *_page_swecc functions but instead they call the
internal *_page_raw functions directly. I propose just to replace the direct calls with indirect
ones (via the function pointers in the nand_chip structure). Does this proposal sound OK?
Mark
>
>
> ___________________________________________________________
> Rise to the challenge for Sport Relief with Yahoo! For Good
>
> http://uk.promotions.yahoo.com/forgood/
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
___________________________________________________________
Rise to the challenge for Sport Relief with Yahoo! For Good
http://uk.promotions.yahoo.com/forgood/
next prev parent reply other threads:[~2008-02-26 9:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 9:54 NAND driver Mark Underwood
2008-02-26 9:04 ` Mark Underwood [this message]
2008-03-26 4:57 ` RadhaKumar Pulyala
-- strict thread matches above, loose matches on Subject: below --
2004-06-01 22:23 Thomas Gleixner
2004-06-02 6:08 ` Pantelis Antoniou
2004-06-02 22:04 ` Thomas Gleixner
2004-04-15 19:50 Thomas Gleixner
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=631124.21101.qm@web36909.mail.mud.yahoo.com \
--to=basicmark@yahoo.com \
--cc=linux-mtd@lists.infradead.org \
/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