09 May, 2007
2 commits
-
Delete the allegedly obsolete "bank_size" member of struct mtd_info.
Signed-off-by: Robert P. J. Day
Signed-off-by: David Woodhouse -
Since the header file include/linux/mtd/mtd.h is not exported to user
space, remove the user space check and error.Signed-off-by: Robert P. J. Day
Signed-off-by: David Woodhouse
08 May, 2007
1 commit
-
This patch extends nand.h in order to enable platform NAND driver.
Signed-off-by: Vitaly Wool
Signed-off-by: Thomas Gleixner
Signed-off-by: David Woodhouse
28 Apr, 2007
1 commit
-
Conflicts:
drivers/mtd/Kconfig
Signed-off-by: David Woodhouse
27 Apr, 2007
1 commit
-
UBI (Latin: "where?") manages multiple logical volumes on a single
flash device, specifically supporting NAND flash devices. UBI provides
a flexible partitioning concept which still allows for wear-levelling
across the whole flash device.In a sense, UBI may be compared to the Logical Volume Manager
(LVM). Whereas LVM maps logical sector numbers to physical HDD sector
numbers, UBI maps logical eraseblocks to physical eraseblocks.More information may be found at
http://www.linux-mtd.infradead.org/doc/ubi.htmlPartitioning/Re-partitioning
An UBI volume occupies a certain number of erase blocks. This is
limited by a configured maximum volume size, which could also be
viewed as the partition size. Each individual UBI volume's size can
be changed independently of the other UBI volumes, provided that the
sum of all volume sizes doesn't exceed a certain limit.UBI supports dynamic volumes and static volumes. Static volumes are
read-only and their contents are protected by CRC check sums.Bad eraseblocks handling
UBI transparently handles bad eraseblocks. When a physical
eraseblock becomes bad, it is substituted by a good physical
eraseblock, and the user does not even notice this.Scrubbing
On a NAND flash bit flips can occur on any write operation,
sometimes also on read. If bit flips persist on the device, at first
they can still be corrected by ECC, but once they accumulate,
correction will become impossible. Thus it is best to actively scrub
the affected eraseblock, by first copying it to a free eraseblock
and then erasing the original. The UBI layer performs this type of
scrubbing under the covers, transparently to the UBI volume users.Erase Counts
UBI maintains an erase count header per eraseblock. This frees
higher-level layers (like file systems) from doing this and allows
for centralized erase count management instead. The erase counts are
used by the wear-levelling algorithm in the UBI layer. The algorithm
itself is exchangeable.Booting from NAND
For booting directly from NAND flash the hardware must at least be
capable of fetching and executing a small portion of the NAND
flash. Some NAND flash controllers have this kind of support. They
usually limit the window to a few kilobytes in erase block 0. This
"initial program loader" (IPL) must then contain sufficient logic to
load and execute the next boot phase.Due to bad eraseblocks, which may be randomly scattered over the
flash device, it is problematic to store the "secondary program
loader" (SPL) statically. Also, due to bit-flips it may become
corrupted over time. UBI allows to solve this problem gracefully by
storing the SPL in a small static UBI volume.UBI volumes vs. static partitions
UBI volumes are still very similar to static MTD partitions:
* both consist of eraseblocks (logical eraseblocks in case of UBI
volumes, and physical eraseblocks in case of static partitions;
* both support three basic operations - read, write, erase.But UBI volumes have the following advantages over traditional
static MTD partitions:* there are no eraseblock wear-leveling constraints in case of UBI
volumes, so the user should not care about this;
* there are no bit-flips and bad eraseblocks in case of UBI volumes.So, UBI volumes may be considered as flash devices with relaxed
restrictions.Where can it be found?
Documentation, kernel code and applications can be found in the MTD
gits.What are the applications for?
The applications help to create binary flash images for two purposes: pfi
files (partial flash images) for in-system update of UBI volumes, and plain
binary images, with or without OOB data in case of NAND, for a manufacturing
step. Furthermore some tools are/and will be created that allow flash content
analysis after a system has crashed..Who did UBI?
The original ideas, where UBI is based on, were developed by Andreas
Arnez, Frank Haverkamp and Thomas Gleixner. Josh W. Boyer and some others
were involved too. The implementation of the kernel layer was done by Artem
B. Bityutskiy. The user-space applications and tools were written by Oliver
Lohmann with contributions from Frank Haverkamp, Andreas Arnez, and Artem.
Joern Engel contributed a patch which modifies JFFS2 so that it can be run on
a UBI volume. Thomas Gleixner did modifications to the NAND layer. Alexander
Schmidt made some testing work as well as core functionality improvements.Signed-off-by: Artem B. Bityutskiy
Signed-off-by: Frank Haverkamp
18 Apr, 2007
1 commit
-
Add Micron Manufacturer ID.
Signed-off-by: Shahrom Sharif
Signed-off-by: Thomas Gleixner
Signed-off-by: David Woodhouse
03 Apr, 2007
1 commit
-
Auto unlock sectors on resume for auto locking flash on power up.
Signed-off-by: Rodolfo Giometti
Signed-off-by: Andrew Morton
Signed-off-by: David Woodhouse
23 Mar, 2007
1 commit
-
Delete the unreferenced header file include/linux/mtd/iflash.h.
Signed-off-by: Robert P. J. Day
Signed-off-by: David Woodhouse
09 Mar, 2007
1 commit
-
Classify the page data and oob buffer
and it prevents the memory fragementation (writesize + oobsize)Signed-off-by: Kyungmin Park
Signed-off-by: David Woodhouse
08 Mar, 2007
1 commit
-
During the MTD rework the oobavail parameter of mtd_info structure has become
private. This is not quite correct in terms of integrity and logic. If we have
means to write to OOB area, then we'd like to know upfront how many bytes out
of OOB are spare per page to be able to adapt to specific cases.
The patch inlined adds the public oobavail parameter.Signed-off-by: Vitaly Wool
Signed-off-by: David Woodhouse
09 Feb, 2007
7 commits
-
Add more comment to OOB I/O interface. Read/write are not
symmetric which is confusing and should be documented.Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse -
Remove unused and broken mtd->ecctype and mtd->eccsize fields
from struct mtd_info. Do not remove them from userspace API
data structures (don't want to breake userspace) but mark them
as obsolete by a comment. Any userspace program which uses them
should be half-broken anyway, so this is more about saving
data structure size.Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse -
Remove ugly and weird MTD_PROGREGION_CTRLMODE_VALID() and
MTD_PROGREGION_CTRLMODE_INVALID() macros. There is only one
user of them and they are used locally just for printing.Anyway, this patch is a preparation for removing mtd->ecctype
and mtd->eccsize, but these macros use them. Fix this.Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse -
This patch adds support for 64 bit resources enabled via the
CONFIG_RESOURCES_64BIT option. Now a 64 bit can be passed to the
physmap driver.Signed-off-by: Stefan Roese
Signed-off-by: Lennert Buytenhek
Signed-off-by: David Woodhouse -
Replace the inclusion of linux/mtd/map.h with a forward-declaration
of struct map_info. This allows linux/mtd/physmap.h to be included by
e.g. board code even if the MTD subsystem is disabled.Signed-off-by: Haavard Skinnemoen
Signed-off-by: David Woodhouse -
Fixes kernel-doc warning in mtd/nand.h.
Signed-off-by: Randy Dunlap
Signed-off-by: Andrew Morton
Signed-off-by: David Woodhouse
07 Feb, 2007
1 commit
-
Provide the bad block scan with its own read function so that important error
messages that are not from the the bad block scan, can always be printed.Signed-off-by: Adrian Hunter
Signed-off-by: Kyungmin Park
02 Feb, 2007
1 commit
-
It use blockpage instead of a pair (block, page). It can also cover a small chunk access. 0x00, 0x20, 0x40 and so on.
And in JFFS2 behavior, sometimes it reads two pages alternatively.
e.g., It first reads A page, B page and A page.
So we check another bufferram to find requested page.Signed-off-by: Kyungmin Park
31 Jan, 2007
1 commit
-
- Remove unused fields
- Fix typoSigned-off-by: Kyungmin Park
18 Jan, 2007
2 commits
-
Update copyrights and code cleanup
Signed-off-by: Kyungmin Park
-
- DDP code clean-up
- Reduce block & bufferram operations in DDPSigned-off-by: Kyungmin Park
10 Jan, 2007
2 commits
-
Read-while-load enables higher performance read operations.
Signed-off-by: Adrian Hunter
Signed-off-by: Kyungmin Park -
OneNAND supports up to 4 writes at one NAND page. Add support of this feature.
Signed-off-by: Kyungmin Park
01 Dec, 2006
1 commit
29 Nov, 2006
7 commits
-
This patch adds get_device() and put_device() methods to the MTD description
structure (struct mtd_info). These methods are called by MTD whenever the MTD
device is get or put. They are needed when the underlying driver is something
smarter then just flash chip driver, for example UBI.Signed-off-by: Artem Bityutskiy
-
This patch adds one more function to the MTD interface to make it possible to
open MTD devices by their names, not only numbers. This is very handy in many
situations. Also, MTD device number depend on load order and may vary, while
names are fixed.Signed-off-by: Artem Bityutskiy
-
Many SLC NANDs support up to 4 writes at one NAND page. Add support
of this feature.Signed-off-by: Artem Bityutskiy
-
Signed-off-by: Artem Bityutskiy
-
As was discussed between Ricard Wanderlöf, David Woodhouse, Artem
Bityutskiy and me, the current API for reading/writing OOB is confusing.The thing that introduces confusion is the need to specify ops.len
together with ops.ooblen for reads/writes that concern only OOB not data
area. So, ops.len is overloaded: when ops.datbuf != NULL it serves to
specify the length of the data read, and when ops.datbuf == NULL, it
serves to specify the full OOB read length.The patch inlined below is the slightly updated version of the previous
patch serving the same purpose, but with the new Artem's comments taken
into account.Artem, BTW, thanks a lot for your valuable input!
Signed-off-by: Vitaly Wool
Signed-off-by: David Woodhouse -
Currently, mtd_blkdevs enforces a block size of 512, even if the drivers
can seemingly request a different size. This patch fixes mtd_blkdevs so
block sizes other than 512 work correctly.Signed-off-by: Richard Purdie
Signed-off-by: David Woodhouse
16 Nov, 2006
3 commits
-
Idea from Jarkko Lavinen
Signed-off-by: Jarkko Lavinen
Signed-off-by: Kyungmin Park -
Now you can use mtd lock inferface on OneNAND
The idea is from Nemakal, Vijaya, thanks
Signed-off-by: Kyungmin Park
-
We can use the two methods to wait.
1. polling: read interrupt status register
2. interrupt: use kernel ineterrupt mechanismTo use interrupt method, you first connect onenand interrupt pin to your
platform and configure interrupt properlySigned-off-by: Kyungmin Park
31 Oct, 2006
1 commit
-
Fix the last current kernel-doc warning:
Warning(/var/linsrc/linux-2619-rc3g5//include/linux/mtd/nand.h:416): No description found for parameter 'write_page'Signed-off-by: Randy Dunlap
Cc: David Woodhouse
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
22 Oct, 2006
1 commit
-
Ditch the separate oobrbuf and oobwbuf fields from the chip buffers,
and use only a single buffer immediately after the data. This accommodates
NAND controllers such as the OLPC CAFÉ chip, which can't do scatter/gather
DMA so needs the OOB buffer to be contiguous with the data, for both read
and write.Signed-off-by: David Woodhouse
04 Oct, 2006
1 commit
-
Many files include the filename at the beginning, serveral used a wrong one.
Signed-off-by: Uwe Zeisberger
Signed-off-by: Adrian Bunk
26 Sep, 2006
2 commits
-
OneNAND lock scheme depends on density and process of chip.
Some OneNAND chips support all block unlockSigned-off-by: Kyungmin Park
Signed-off-by: David Woodhouse -
Signed-off-by: David Woodhouse