From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] mtd: vf610_nfc: mark page as dirty on block erase
Date: Thu, 2 Apr 2015 18:48:19 -0500 [thread overview]
Message-ID: <1428018499.22867.304.camel@freescale.com> (raw)
In-Reply-To: <877ftxnrak.fsf@nbsps.com>
On Tue, 2015-03-31 at 11:02 -0400, Bill Pringlemeir wrote:
> On 2015-03-31 00:15, Scott Wood wrote:
>
> > Especially since you'd be doing one write rather than four full-page
> > "partial" writes. Surely the bottleneck here is the NAND chip itself,
> > not copying data to the buffer?
>
> The AHB bus that the NFC controller is on is relatively slow. Here are
> some numbers from 'AN4947-vybrid-bus-architechure',
>
> Vybrid Cortex A5 to DDR (in CPU clocks 400/500MHz),
>
> First read Subsequent
> 285 8 all caches on
> 345 269 no cache, mmu
> 437 371 no cache, no mmu
>
> The NFC is on an AHB bus 32bit, 66MHz (not AXI 64bit, 133-166MHz like
> DDR). The AHB will be about four times slower. Also the reads and
> writes to the physical NAND must take place serially. Here are the
> program page steps.
>
> 1. Issue controller Read full page to NFC buffer.
> 2. Copy update partial page from DDR to NFC buffer.
> 3. Issue write NAND page.
Why is any sort of read part of the write process?
If this controller can't handle subpage writes properly, then disable
them.
-Scott
next prev parent reply other threads:[~2015-04-02 23:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 16:54 [U-Boot] [PATCH 1/2] mtd: vf610_nfc: mark page as dirty on block erase Stefan Agner
2015-03-24 16:54 ` [U-Boot] [PATCH 2/2] mtd: vf610_nfc: specify transfer size before each transfer Stefan Agner
2015-03-30 17:02 ` [U-Boot] [PATCH 1/2] mtd: vf610_nfc: mark page as dirty on block erase Bill Pringlemeir
2015-03-30 20:14 ` Stefan Agner
2015-03-30 20:46 ` Scott Wood
2015-03-30 20:34 ` Scott Wood
2015-03-30 20:40 ` Stefan Agner
2015-03-30 20:48 ` Scott Wood
2015-03-30 21:26 ` Stefan Agner
2015-03-30 22:15 ` Scott Wood
2015-03-30 22:24 ` Stefan Agner
2015-03-31 4:34 ` Scott Wood
2015-03-31 15:02 ` Bill Pringlemeir
2015-04-02 23:48 ` Scott Wood [this message]
2015-04-03 18:09 ` Stefan Agner
2015-04-03 20:15 ` Scott Wood
2015-04-03 20:28 ` Stefan Agner
2015-04-03 21:03 ` Scott Wood
2015-04-07 14:06 ` Bill Pringlemeir
2015-04-07 16:02 ` Scott Wood
2015-04-07 17:54 ` Bill Pringlemeir
2015-04-07 21:09 ` Scott Wood
2015-03-30 21:35 ` Bill Pringlemeir
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=1428018499.22867.304.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=u-boot@lists.denx.de \
/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