Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Maxim Levitsky <maximlevitsky@gmail.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, joern <joern@logfs.org>,
	linux-mtd <linux-mtd@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Alex Dubov <oakad@yahoo.com>
Subject: [PATCH 0/6] MTD: Many fixes and preparation for SmartMedia support in nand subsystem
Date: Fri, 22 Jan 2010 17:56:21 +0200	[thread overview]
Message-ID: <1264175781.24012.42.camel@maxim-laptop> (raw)

Hello,

This patch series add few fixes and changes to nand subsystem.

First patch, fixes the MTD_OOB_PLACE support in nand.
I want to use ->read_oob to read both raw oob and data and use ecc.
MTD_OOB_PLACE should do that, but due to a wrong check it will refuse to
work.

Second patch, probably the most important patch in this series.
I changed behavier of MTD_OOB_RAW to match the one of MTD_OOB_PLACE
minus ecc validation.
This way it is easy to use both modes in same code.
This mode is only used in one place, in scan_read_raw in nand_bbt.c
I edited this function to achieve exactly same effect as was before.

Third patch is another bugfix that I need to be able to write several
pages in one go. ->write_oob should do that, but it was incorrectly
implemented.
I need this and former patch to add support for 256 byte nand chips in
the smartmedia FTL very elegantly.

Fourth patch exports few functions from nand_base.c, so one can write
custom ->block_mark_bad, and ->block_is_bad functions.
I use these functions in next patch.

Fifth patch, adds small helper module for nand drivers for SmartMedia/xD
readers. It contains bad block handlers and ecc layer.

And last patch, adds some workarounds to nand core to make xD work with
it.

It adds new ID table (which is similiar to current ID table, but
dfferent in that it has IDS for readonly SmartMedia devices, and it has
special settings for new xD cards that share ID with regular nand
devices, but unfortunely don't report proper information in READ ID
command, and have other problems.)

It also adds a workaround for broken writeprotect status.
Older smartmedia devices had a special seal for writeprotect, aka a
additional connector. This should be handled by nand driver itself.
Newer xD cards have no write protect support at all.

Best regards,
Maxim Levitsky

             reply	other threads:[~2010-01-22 15:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-22 15:56 Maxim Levitsky [this message]
2010-01-22 15:57 ` [PATCH 1/6] MTD: nand: make MTD_OOB_PLACE work correctly Maxim Levitsky
2010-01-22 15:58 ` [PATCH 2/6] MTD: nand: make reads using MTD_OOB_RAW affect only ECC validation Maxim Levitsky
2010-01-22 15:59 ` [PATCH 3/6] MTD: nand: fix bug that prevented write of more that one page by ->write_oob Maxim Levitsky
2010-01-22 16:00 ` [PATCH 4/6] MTD: export few functions from nand_base.c Maxim Levitsky
2010-01-22 16:01 ` [PATCH 5/6] MTD: common module for smartmedia/xD support Maxim Levitsky
2010-01-22 16:02 ` [PATCH 6/6] MTD: add few workarounds to nand system for SmartMedia/xD chips Maxim Levitsky

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=1264175781.24012.42.camel@maxim-laptop \
    --to=maximlevitsky@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=joern@logfs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=oakad@yahoo.com \
    --cc=tglx@linutronix.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