kernel.git/drivers/mtd/tests/mtd_speedtest.c, branch linux-3.5.y

mtd: introduce mtd_can_have_bb helper

2012-01-09T18:26:24Z

This patch introduces new 'mtd_can_have_bb()' helper function which checks whether the flash can have bad eraseblocks. Then it changes all the direct 'mtd->block_isbad' use cases with 'mtd_can_have_bb()'. Signed-off-by: Artem Bityutskiy Signed-off-by: David Woodhouse

mtd: remove extra retlen assignment

2012-01-09T18:25:56Z

MTD functions always assign the 'retlen' argument to 0 at the very beginning - the callers do not have to do this. I used the following semantic patch to find these places: @@ identifier retlen; expression a, b, c, d, e; constant C; type T; @@ ( - retlen = C; | T -retlen = C + retlen ; ) ... when != retlen when exists ( mtd_read(a, b, c, &retlen, d) | mtd_write(a, b, c, &retlen, d) | mtd_panic_write(a, b, c, &retlen, d) | mtd_point(a, b, c, &retlen, d, e) | mtd_read_fact_prot_reg(a, b, c, &retlen, d) | mtd_write_user_prot_reg(a, b, c, &retlen, d) | mtd_read_user_prot_reg(a, b, c, &retlen, d) | mtd_writev(a, b, c, d, &retlen) ) I ran it twice, because there were cases of double zero assigments in mtd tests. Then I went through the patch to verify that spatch did not find any false positives. Signed-off-by: Artem Bityutskiy Signed-off-by: David Woodhouse

mtd: introduce mtd_block_isbad interface

2012-01-09T18:25:47Z

Signed-off-by: Artem Bityutskiy Signed-off-by: David Woodhouse

mtd: introduce mtd_write interface

2012-01-09T18:25:20Z

Signed-off-by: Artem Bityutskiy Signed-off-by: David Woodhouse

mtd: introduce mtd_read interface

2012-01-09T18:25:19Z

Signed-off-by: Artem Bityutskiy Signed-off-by: David Woodhouse

mtd: introduce mtd_erase interface

2012-01-09T18:25:11Z

This patch is part of a patch-set which changes the MTD interface from 'mtd->func()' form to 'mtd_func()' form. We need this because we want to add common code to to all drivers in the mtd core level, which is impossible with the current interface when MTD clients call driver functions like 'read()' or 'write()' directly. At this point we just introduce a new inline wrapper function, but later some of them are expected to gain more code. E.g., the input parameters check should be moved to the wrappers rather than be duplicated at many drivers. This particular patch introduced the 'mtd_erase()' interface. The following patches add all the other interfaces one by one. Signed-off-by: Artem Bityutskiy Signed-off-by: David Woodhouse

mtd: tests: don't use mtd0 as a default

2011-10-30T12:31:04Z

mtd tests may erase the mtd device, so force the user to specify which mtd device to test by using the module parameter. Disable the default (using mtd0) since this may destroy a vital part of the flash if the module is inserted accidently or carelessly. Reported-by: Roland Kletzing Signed-off-by: Wolfram Sang Signed-off-by: Artem Bityutskiy

mtd: utilize `mtd_is_*()' functions

2011-09-21T06:19:06Z

Signed-off-by: Brian Norris Signed-off-by: Artem Bityutskiy

mtd: speedtest: fix integer overflow

2011-03-11T14:22:49Z

32-bit integers used in 'calc_speed()' may overflow and lead to incorrect results. Use 64-bit integers instead. Signed-off-by: David Lambert Signed-off-by: Artem Bityutskiy Signed-off-by: David Woodhouse

mtd: tests: add multiblock erase test to the mtd_speedtest

2011-03-11T14:22:45Z

New multiblock erase speed test is added to mtd_speedtest. It consists of 2-, 4-, 8-, 16-, 32- and 64-blocks at once multiblock erase tests. Signed-off-by: Roman Tereshonkov Signed-off-by: Artem Bityutskiy Signed-off-by: David Woodhouse