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: Mon, 30 Mar 2015 23:34:36 -0500 [thread overview]
Message-ID: <1427776476.22867.220.camel@freescale.com> (raw)
In-Reply-To: <1d8481267a40fed73b4aff1a50ae0774@agner.ch>
On Tue, 2015-03-31 at 00:24 +0200, Stefan Agner wrote:
> Actually, I just realized that the driver is not caching writes.
>
> switch (command) {
> case NAND_CMD_PAGEPROG:
> nfc->page = -1;
> + vf610_nfc_transfer_size(nfc->regs, nfc->page_sz);
> vf610_nfc_send_commands(nfc->regs, NAND_CMD_SEQIN,
> command, PROGRAM_PAGE_CMD_CODE);
> vf610_nfc_addr_cycle(mtd, column, page);
> break;
>
> The nfc->page = -1 resets the page cache, so the next read triggers a
> full page read.
>
> I will check the performance consequences when disabling cache entirely,
> and whether it would be possible to implement a OOB only read.
OK. In the meantime I'll apply this.
-Scott
next prev parent reply other threads:[~2015-03-31 4:34 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 [this message]
2015-03-31 15:02 ` Bill Pringlemeir
2015-04-02 23:48 ` Scott Wood
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=1427776476.22867.220.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