From: Sascha Hauer <s.hauer@pengutronix.de>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 0/2] drivers/mtd: add a core
Date: Tue, 13 Dec 2011 10:21:47 +0100 [thread overview]
Message-ID: <20111213092147.GC27267@pengutronix.de> (raw)
In-Reply-To: <1323710046-4455-1-git-send-email-robert.jarzmik@free.fr>
Hi Robert,
On Mon, Dec 12, 2011 at 06:14:04PM +0100, Robert Jarzmik wrote:
> This patchset aims at bringing a common core to all mtd
> devices. This minimal core provides :
> - add_mtd_device()
> - del_mtd_device()
>
> The add_mtd_device() creates 2 character devices, as
> explained in the second commit.
>
> This core will be used by drivers/mtd/devices/* (soon to
> come), and hopefully drivers/mtd/nand/* if we agree on
> add_mtd_device() functionality.
>
> The core should provide read/write/erase capability which
> suits all the devices (ie. nand, nor and bare).
>
> If no agreement emerges, this core will be moved into
> drivers/mtd/devices.
>
> The nand devices are left as they were, and not converted to
> the new core. This conversion will only be possible after
> some feedback about the needs of nand legacy drivers.
The mtd core looks mostly looks like a duplicate of
drivers/mtd/nand/nand.c. The differences are:
- nand.c contains a 'all 0xff' check in its write function. This
is to make sure not to actually write data when it's all 0xff.
Some nand chips need this because they can't be written twice
even if we write with all 1.
- The nand_oob device is replaced with a device containing both
oob and data.
I created the nand_oob device mainly for debugging purposes. It can be
convenient to be able to see the oob data. As this has no practical
use besides debugging it can be easily replaced with an interleaved
data/oob device. The oob device is quite inconvenient to use anyway
since it requires some calculating to get the oob data for a given
page.
So if no protests from other side come we can:
- git mv drivers/mtd/nand/nand.c drivers/mtd/core.c
- replace the oob device with the data+oob device
- apply whatever other fixes you need
I should be able to test the result on raw nand devices.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-12-13 9:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 17:14 Robert Jarzmik
2011-12-12 17:14 ` [PATCH 1/2] drivers/mtd: introduce {add,del}_nand_device Robert Jarzmik
2011-12-12 17:14 ` [PATCH 2/2] drivers/mtd: add a core mtd handler Robert Jarzmik
2011-12-13 9:21 ` Sascha Hauer [this message]
2011-12-13 10:46 ` [PATCH 0/2] drivers/mtd: add a core Robert Jarzmik
2011-12-13 11:11 ` Sascha Hauer
2011-12-13 10:51 ` Robert Jarzmik
2011-12-13 11:29 ` Sascha Hauer
2011-12-13 12:35 ` Robert Jarzmik
2011-12-13 18:58 ` Sascha Hauer
2011-12-14 10:01 ` Robert Jarzmik
2011-12-14 11:02 ` Sascha Hauer
2011-12-14 14:20 ` Robert Jarzmik
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=20111213092147.GC27267@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=robert.jarzmik@free.fr \
/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