linux.git/drivers/mtd/devices/mtd_dataflash.c, branch v2.6.29

mtd_dataflash: fix probing of AT45DB321C chips.

2009-03-10T22:55:11+00:00

Commit 771999b65f79264acde4b855e5d35696eca5e80c ("[MTD] DataFlash: bugfix,
binary page sizes now handled") broke support for probing AT45DB321C flash
chips.  These chips do not support the "page size" status bit, so if we
match the JEDEC id return early.

[akpm@linux-foundation.org: coding-style fixes]
Signed-off-by: Will Newton 
Cc: David Woodhouse 
Acked-by: David Brownell 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[MTD] struct device - replace bus_id with dev_name(), dev_set_name()

2008-12-23T10:00:14+00:00

Signed-off-by: Kay Sievers 
Signed-off-by: Greg Kroah-Hartman 
Signed-off-by: David Woodhouse

[MTD] fix dataflash 64-bit divisions

2008-12-19T16:23:18+00:00

MTD has recently been upgraded for 64-bit support, see commit
number 69423d99fc182a81f3c5db3eb5c140acc6fc64be in the
mtd-2.6.git tree (git://git.infradead.org/mtd-2.6.git)
or see this URL:
http://git.infradead.org/mtd-2.6.git?a=commit;h=69423d99fc182a81f3c5db3eb5c140acc6fc64be

Some variables in MTD data structures which were 32-bit
became 64-bit. Namely, the 'size' field in 'struct mtd_info'
and the 'addr'/'len' fields in 'struct erase_info'. This
means we have to use 'do_div' to divide them.

This patch fixes the following linking error:
ERROR: "__udivdi3" [drivers/mtd/devices/mtd_dataflash.ko] undefined!
ERROR: "__umoddi3" [drivers/mtd/devices/mtd_dataflash.ko] undefined!

This patch changes divisions of 64-bit variable so that they use
'do_div'. This patch also change some print placeholders to
get rid of gcc warnings.

Signed-off-by: Artem Bityutskiy 
Cc: David Brownell 
Cc: Nicolas Pitre 
Signed-off-by: David Woodhouse

[MTD] make dataflash write-verify be optional

2008-08-07T10:49:00+00:00

This adds a WRITE_VERIFY Kconfig option to the DataFlash driver,
closely mirroring the similar NAND and ONENAND options, giving
an option to disable some code that's currently always enabled.

Removing this step probably saves a millisecond or so per page
when writing data, which will add up quickly since these pages
are small (the largest is 1 KiB).  It doesn't seem to add a
lot in terms of reliability, and wouldn't detect errors which
crop up when transferring data to the on-chip SRAM buffer.

Signed-off-by: David Brownell 
Acked-by: Haavard Skinnemoen 
Acked-by: Andrew Victor 
Signed-off-by: David Woodhouse

[MTD] Compile fix for dataflash OTP support

2008-08-07T10:23:38+00:00

> > linux-next-20080805/drivers/mtd/devices/mtd_dataflash.c: In function 'add_dataflash_otp':
> > linux-next-20080805/drivers/mtd/devices/mtd_dataflash.c:670: error: too many arguments to function 'otp_setup'

Whoops, sorry ... I see what was going on.  My bad.

Signed-off-by: David Brownell 
Signed-off-by: David Woodhouse

[MTD] dataflash OTP support

2008-08-01T20:47:47+00:00

Now that we can tell when we have one of the newer DataFlash chips,
optionally expose the 128 bytes of OTP memory they provide.  Tested
on at45db642 revision B and D chips.

Switch mtdchar over to a generic HAVE_MTD_OTP flag instead of adding
another #ifdef for each type of chip whose driver has OTP support.

Signed-off-by: David Brownell 
Cc: Bryan Wu 
Cc: Michael Hennerich 
Signed-off-by: Andrew Morton 
Signed-off-by: David Woodhouse

[MTD] DataFlash: bugfix, binary page sizes now handled

2008-07-30T13:20:32+00:00

The wrong version of the "teach dataflash about binary density" patch
just got merged (v2 not v3) ... this restores the missing updates:

  * Fix the cmdlinepart *regression* that caused testing failures (!!)
    by restoring the original part labels in relevant cases.

  * Don't reference things that don't exist (!)
	- An opcode that doesn't even exist for DataFlash
	- The part is "at45db642" not "at45db641"
	- ID zero in this JEDEC table

  * Make the JEDEC probe routine report and handle errors better:
	- If the SPI calls fail, return the error codes.
	- Don't depend on ordering of table entries.
	- Unrecognized ids are different from parts that have no ID.
          We won't actually know how to handle them correctly; display
	  the ID and ignore the chip.

  * Move the original block comment about the "legacy" chip ID scheme
    back next to the code to which it applies ... not next to the new
    JEDEC query code, which uses an entirely different strategy.

  * Don't print a guessed erasesize; /proc/mtd has the real value.

And add a few more comments.

Signed-off-by: David Brownell 
Cc: Bryan Wu 
Cc: Michael Hennerich 
Signed-off-by: Andrew Morton 
Signed-off-by: David Woodhouse

[MTD] DataFlash: use proper types

2008-06-04T16:43:22+00:00

Signed-off-by: David Woodhouse

[MTD] DataFlash: fix bug - ATMEL AT45DF321D spi flash card fails to be copied to (v2)

2008-06-04T16:39:38+00:00

 - Add support for binary page size DataFlashes.
 - The driver now prints out pagesize and erasesize.
   Printout valuable information for creating flash filesystems.

Signed-off-by: Michael Hennerich 
Cc: David Brownell 
Signed-off-by: Bryan Wu 
Signed-off-by: David Woodhouse

[MTD] mtd_dataflash: Incorrect compare-after-write check

2007-11-28T11:55:32+00:00

After writing to a Dataflash page, the built-in compare operation is
used to check that the page was successfully written.  A logic bug in
checking the results of the comparison currently causes the compare to
never fail.

This bug was originally in the legacy at91_dataflash.c driver.

Signed-off-by: Andrew Victor 
Acked-by: David Brownell 
Signed-off-by: David Woodhouse