All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Agner <stefan@agner.ch>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/8] mtd: vf610_nfc: various fixes and improvements
Date: Wed,  8 Apr 2015 16:44:33 +0200	[thread overview]
Message-ID: <1428504281-30214-1-git-send-email-stefan@agner.ch> (raw)

This patchset contains various improvements and enhancements to the
NAND flash controller found on Vybrid (vf610) and other Freescale
platforms. It's a merge and follow up of two patchset sent earlier:
- mtd: vf610_nfc: remove caching of page in page buffer
  http://lists.denx.de/pipermail/u-boot/2015-April/209817.html
- mtd: vf610_nfc: use in-band bad block table
  http://lists.denx.de/pipermail/u-boot/2015-April/209889.html

The patch "mtd: vf610_nfc: support subpage write" has been dropped
as discussed. As a further consequence, this patchset includes a
patch which changes the behaviour of the SEQIN command (patch 3).

- Patch 1 to 3 fix non-critical issues or undesirable behavior.
- Patch 4 enhances the driver with a page read function with reads
  the OOB area only and also simplifies vf610_nfc_read_buf.
- Patch 5 switches to in-band bad block table which is a prerequisit
  for 32-error correction (patch 7) on 64 byte OOB.
- Patch 6 converts the driver to be configureable through Kconfig.
- Patch 7 enhances driver configuration for 32-error correction.
- Patch 8 allows reading the ONFI parameter page.

The changes between 1-4 has been discussed on the mailinglist lately.

Stefan Agner (8):
  mtd: vf610_nfc: remove caching of page in buffer
  mtd: vf610_nfc: remove read on SEQIN
  mtd: vf610_nfc: allow bitflips in an empty page
  mtd: vf610_nfc: implement OOB only read
  mtd: vf610_nfc: use in-band bad block table
  mtd: vf610_nfc: add Freescale NFC controller configs to Kconfig
  mtd: vf610_nfc: add 32-error correction option for HW ECC
  mtd: vf610_nfc: enable ONFI detection

 configs/vf610twr_defconfig   |   2 +
 doc/README.nand              |  18 ----
 drivers/mtd/nand/Kconfig     |  45 +++++++++
 drivers/mtd/nand/vf610_nfc.c | 232 ++++++++++++++++++++++---------------------
 include/configs/vf610twr.h   |   4 +-
 5 files changed, 168 insertions(+), 133 deletions(-)

-- 
2.3.5

             reply	other threads:[~2015-04-08 14:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 14:44 Stefan Agner [this message]
2015-04-08 14:44 ` [U-Boot] [PATCH v2 1/8] mtd: vf610_nfc: remove caching of page in buffer Stefan Agner
2015-04-08 14:44 ` [U-Boot] [PATCH v2 2/8] mtd: vf610_nfc: remove read on SEQIN Stefan Agner
2015-04-08 14:44 ` [U-Boot] [PATCH v2 3/8] mtd: vf610_nfc: allow bitflips in an empty page Stefan Agner
2015-04-08 14:44 ` [U-Boot] [PATCH v2 4/8] mtd: vf610_nfc: implement OOB only read Stefan Agner
2015-04-08 14:44 ` [U-Boot] [PATCH v2 5/8] mtd: vf610_nfc: use in-band bad block table Stefan Agner
2015-04-08 14:44 ` [U-Boot] [PATCH v2 6/8] mtd: vf610_nfc: add Freescale NFC controller configs to Kconfig Stefan Agner
2015-04-08 14:44 ` [U-Boot] [PATCH v2 7/8] mtd: vf610_nfc: add 32-error correction option for HW ECC Stefan Agner
2015-04-08 14:44 ` [U-Boot] [PATCH v2 8/8] mtd: vf610_nfc: enable ONFI detection Stefan Agner
2015-04-20 23:17   ` Scott Wood
2015-05-08 15:49     ` Stefan Agner

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=1428504281-30214-1-git-send-email-stefan@agner.ch \
    --to=stefan@agner.ch \
    --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.