Move manufacturer ID search to display correct ID in case of buswidth
mismatch.
Signed-off-by: NKyungmin Park <kyungmin.park@samsung.com>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

Signed-off-by: NBen Dooks <ben@simtec.co.uk>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

The change to the generic probe to look for the
smallest width of chip first is causing some problems
on boards with a single 16bit device.

The problem seems to be the jedec_match() is truncating
the device-id read from the table to match against the
one read from the hardware, causing a match against the
partial id of some chips with 16bit IDs (such as the
SST39LF160)

This fixes things for my own board, but something may
need to be done if the same problem is exhibited for
chips with an 8bit ID
Signed-off-by: NBen Dooks <ben@simtec.co.uk>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

When scanning NAND for bad blocks, don't read the whole page, read
only needed OOB bytes instead. Also check the return code of the
nand_read_raw() function. Correctly free the this->bbt array in
case of failure. Tested with Large page NAND.

Fix debugging message.
Signed-off-by: NArtem B. Bityuckiy <dedekind@infradead.org>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

Small bugfix. Sometimes it may be handy not to have bbt.
So, this->bbt might be NULL.
Signed-off-by: NArtem B. Bityuckiy <dedekind@infradead.org>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

This patch replaces the current CONFIG_JFFS2_FS_NAND, CONFIG_JFFS2_FS_NOR_ECC
and CONFIG_JFFS2_FS_DATAFLASH with a single configuration option -
CONFIG_JFFS2_FS_WRITEBUFFER.

The only functional change of this patch is that the slower div/mod
calculations for SECTOR_ADDR(), PAGE_DIV() and PAGE_MOD() are now always
used when CONFIG_JFFS2_FS_WRITEBUFFER is enabled.
Signed-off-by: NAndrew Victor <andrew@sanpeople.com>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

For Dataflash, can_mark_obsolete = false and the NAND write buffering
code (wbuf.c) is used.

Since the DataFlash chip will automatically erase pages when writing,
the cleanmarkers are not needed - so cleanmarker_oob = false and
cleanmarker_size = 0

DataFlash page-sizes are not a power of two (they're multiples of 528
bytes).  The SECTOR_ADDR macro (added in the previous core patch) is
replaced with a (slower) div/mod version if CONFIG_JFFS2_FS_DATAFLASH is
selected.
Signed-off-by: NAndrew Victor <andrew@sanpeople.com>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

DataFlash page-sizes are not a power of two (they're multiples of 528
bytes).  There are a few places in JFFS2 code where sector_size is used
as a bitmask.  A new macro (SECTOR_ADDR) was defined to calculate these
sector addresses. For non-DataFlash devices, the original (faster)
bitmask operation is still used.

In scan.c, the EMPTY_SCAN_SIZE was a constant of 1024.
Since this could be larger than the sector size of the DataFlash, this
is now basically set to MIN(sector_size, 1024).

Addition of a jffs2_is_writebuffered() macro.
Signed-off-by: NAndrew Victor <andrew@sanpeople.com>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

Signed-off-by: NNicolas Pitre <nico@cam.org>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

This is implemented using a ioctl to switch the MTD char device into
one of the different OTP "modes", at which point read/write/seek can
operate on the selected OTP area.  Also some extra ioctls to query
for size and lock protection segments or groups.  Some example user
space utilities are provided.
Signed-off-by: NNicolas Pitre <nico@cam.org>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

This enables support for reading, writing and locking so called
"Protection Registers" present on some flash chips.
A subset of them are pre-programmed at the factory with a
unique set of values. The rest is user-programmable.
Signed-off-by: NNicolas Pitre <nico@cam.org>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

Prevent deadlock when checking erased block for
space allocation during wbuf recovery.
Signed-off-by: NEstelle Hammache <estelle.hammache@st.com>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

add structure definition for OTP region info
Signed-off-by: NNicolas Pitre <nico@cam.org>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

* Removed table entry for AM29BDS643D, since device ID clashes with AM29DL640G
and both chips support CFI.
Signed-off-by: NJonas Holmberg <jonas.holmberg@axis.com>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

make NAND code work on NOR flash again
Signed-off-by: NDavid Woodhouse <dwmw2@infradead.org>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

Make NFTL devices work on big endian machines.
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

Remove commented ugliness
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

Using the CONFIG_ options from KConfig seems to work better :8
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

Code beautification and block filing correction for optimization.
Signed-off-by: NEstelle Hammache <estelle.hammache@st.com>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

Try larger numbers of chips before smaller
numbers of chips across the bus width.

This means we'll avoid misdetecting a 2 x16 array as 1 x32 if the
high 16-bits happen to read as zeros in the QRY area.
Signed-off-by: NRussell King <linux@arm.linux.org.uk>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

avoid segfault when nextblock was refiled because of a write failure
- avoid filing blocks on the clean list when they have wasted
space
Signed-off-by: NEstelle Hammache <estelle.hammache@st.com>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

- block refiling when writing directly to flash a buffer
which is bigger than wbuf
- retry cases for flushing wbuf
Signed-off-by: NEstelle Hammache <estelle.hammache@st.com>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

Correction of retry case to avoid silent failure of rmdir
when jffs2_wbuf_recover GCs the previous entry (+ corresponding
dnode case).
Signed-off-by: NEstelle Hammache <estelle.hammache@st.com>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

Added routine to perform extra error status checks on erase and write
failures to determine if errors are correctable.
Added option to prevent JFFS2 from using virtual erase blocks.
Performed minor cleanup on whitespace and comments.
Signed-off-by: NDavid A. Marlin <dmarlin@redhat.com>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

Add optional hardware specific callback routine to perform extra error
status checks on erase and write failures for devices with hardware ECC.
Signed-off-by: NDavid A. Marlin <dmarlin@redhat.com>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

Driver for generic RAM blocks which are exported by an platform_device
from the device driver system.
Signed-off-by: NBen Dooks <ben@simtec.co.uk>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

Replace some literals with defined symbols.
Signed-off-by: NDavid A. Marlin <dmarlin@redhat.com>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

Correct Poodle default partition size
Signed-off-by: NRichard Purdie <rpurdie@rpsys.net>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

Avoid "Eep. No valid nodes for ino #1" message for just-created filesystem.
Signed-off-by: NTodd Poynor <tpoynor@mvista.com>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

Replace yield by msleep. M.Wilcox stared at it and frowned
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

Ensure the whole device is added if there are no partitions found on the
device, so that at least the flash can be read/written.

Replace some of the constants with their SZ_xxx counterparts
Signed-off-by: NBen Dooks <ben@simtec.co.uk>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

Add routine to perform device recovery (deplete) procedure.
Clean up some compiler warnings.
Signed-off-by: NDavid A. Marlin <dmarlin@redhat.com>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

Added workaround for Renesas AG-AND chips "disturb" issue 
for Bad Block Table. 
Added support for the device recovery command sequence 
for Renesas AG-AND chips.
Signed-off-by: NDavid A. Marlin <dmarlin@redhat.com>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

Added extended commands for AG-AND device and added 
option for BBT_AUTO_REFRESH.
Signed-off-by: NDavid A. Marlin <dmarlin@redhat.com>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

For the case that mtd partitions are enabled it would cause a 0-pointer 
dereferencing in mtdpart.c:mtd_erase_callback()
Signed-off-by: NHerbert Valerio Riedel <hvr@inso.tuwien.ac.at>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

Add error checks to read/write functions and add an eraseblock size.
Makes slram a suitable device for JFFS2.
Signed-off-by: NJosh Boyer <jdub@us.ibm.com>
Signed-off-by: NThomas Gleixner <tglx@linutronix.de>

Prevent the topdown allocator from allocating mmap areas all the way
down to address zero.

We still allow a MAP_FIXED mapping of page 0 (needed for various things,
ranging from Wine and DOSEMU to people who want to allow speculative
loads off a NULL pointer).

Tested by Chris Wright.
Signed-off-by: NLinus Torvalds <torvalds@osdl.org>

Avoid console spam with ext3 aborted journal.

ext3 usually reports error conditions that it detects in its environment.
But when its journal gets aborted due to such errors, it can sometimes
continue to report that condition forever, spamming the console to such
an extent that the initial first cause of the journal abort can be lost.

When the journal aborts, we put the filesystem into readonly mode.  Most
subsequent filesystem operations will get rejected immediately by checks
for MS_RDONLY either in the filesystem or in the VFS.  But some paths do
not have such checks --- for example, if we continue to write to a file
handle that was opened before the fs went readonly.  (We only check for
the ROFS condition when the file is first opened.)  In these cases, we
can continue to generate log errors similar to

EXT3-fs error (device $DEV) in start_transaction: Journal has aborted

for each subsequent write.

There is really no point in generating these errors after the initial
error has been fully reported.  Specifically, if we're starting a
completely new filesystem operation, and the filesystem is *already*
readonly (ie. the ext3 layer has already detected and handled the
underlying jbd abort), and we see an EROFS error, then there is simply
no point in reporting it again.
Signed-off-by: NStephen Tweedie <sct@redhat.com>
Signed-off-by: NLinus Torvalds <torvalds@osdl.org>