From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/4] mtd: vf610_nfc: support subpage write
Date: Fri, 3 Apr 2015 15:36:43 -0500 [thread overview]
Message-ID: <1428093403.22867.347.camel@freescale.com> (raw)
In-Reply-To: <1428086445-10554-4-git-send-email-stefan@agner.ch>
On Fri, 2015-04-03 at 20:40 +0200, Stefan Agner wrote:
> Support subpage writes using a custom implementation of write_subpage.
> The driver loads the page into SRAM buffer using NAND_CMD_READ0, when
> the framework requests the NAND_CMD_SEQIN command. Then, the buffer is
> updated by the custom write_subpage implementation. Upon write, the
> controller calculates the hardware ECC across the whole page before
> programming the page.
>
> This method saves transferring the whole page over the bus to the NFC
> IP, which would happen when using NAND_NO_SUBPAGE_WRITE.
>
> Signed-off-by: Stefan Agner <stefan@agner.ch>
As previously discussed, please explain why subpage writes make sense
with this controller.
-Scott
next prev parent reply other threads:[~2015-04-03 20:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 18:40 [U-Boot] [PATCH 1/4] mtd: vf610_nfc: use in-band bad block table Stefan Agner
2015-04-03 18:40 ` [U-Boot] [PATCH 2/4] mtd: vf610_nfc: add Freescale NFC controller configs to Kconfig Stefan Agner
2015-04-03 20:30 ` Scott Wood
2015-04-03 20:42 ` Stefan Agner
2015-04-03 20:46 ` Scott Wood
2015-04-03 22:30 ` Stefan Agner
2015-04-03 22:47 ` Scott Wood
2015-04-03 18:40 ` [U-Boot] [PATCH 3/4] mtd: vf610_nfc: add 32-error correction option for HW ECC Stefan Agner
2015-04-03 18:40 ` [U-Boot] [PATCH 4/4] mtd: vf610_nfc: support subpage write Stefan Agner
2015-04-03 20:36 ` Scott Wood [this message]
2015-04-03 22:24 ` Stefan Agner
2015-04-07 13:48 ` Bill Pringlemeir
2015-04-07 16:21 ` Scott Wood
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=1428093403.22867.347.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.