linux-toradex.git/drivers/mtd/rfd_ftl.c, branch v3.12-rc2

mtd: do not use mtd->sync directly

2012-01-09T18:26:21+00:00

This patch teaches 'mtd_sync()' to do nothing when the MTD driver does
not have the '->sync()' method, which allows us to remove all direct
'mtd->sync' accesses.

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

mtd: introduce mtd_sync interface

2012-01-09T18:25:35+00:00

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

mtd: introduce mtd_write interface

2012-01-09T18:25:20+00:00

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

mtd: introduce mtd_read interface

2012-01-09T18:25:19+00:00

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

mtd: introduce mtd_erase interface

2012-01-09T18:25:11+00:00

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: Add module.h to drivers users that were implicitly using it.

2011-10-31T23:31:12+00:00

We are cleaning up the implicit presence of module.h that these
drivers are taking advantage of.  Fix them in advance of the
cleanup operation.

Signed-off-by: Paul Gortmaker

mtd: Update copyright notices

2010-08-08T19:58:20+00:00

Signed-off-by: David Woodhouse

mtd: blktrans: Hotplug fixes

2010-02-26T17:05:26+00:00

* Add locking where it was missing.

* Don't do a get_mtd_device in blktrans_open because it would lead to a
  deadlock; instead do that in add_mtd_blktrans_dev.

* Only free the mtd_blktrans_dev structure when the last user exits.

* Flush request queue on device removal.

* Track users, and call tr->release in del_mtd_blktrans_dev
  Due to that ->open and release aren't called more that once.

Now it is safe to call del_mtd_blktrans_dev while the device is still in use.

Signed-off-by: Maxim Levitsky 
Signed-off-by: David Woodhouse

[MTD] remove private wrapper of endian helpers in rfd_ftl.c

2008-12-10T15:39:09+00:00

Base versions handle constant folding just fine.

Signed-off-by: Harvey Harrison 
Signed-off-by: David Woodhouse

[MTD] update internal API to support 64-bit device size

2008-12-10T13:37:21+00:00

MTD internal API presently uses 32-bit values to represent
device size.  This patch updates them to 64-bits but leaves
the external API unchanged.  Extending the external API
is a separate issue for several reasons.  First, no one
needs it at the moment.  Secondly, whether the implementation
is done with IOCTLs, sysfs or both is still debated.  Thirdly
external API changes require the internal API to be accepted
first.

Note that although the MTD API will be able to support 64-bit
device sizes, existing drivers do not and are not required
to do so, although NAND base has been updated.

In general, changing from 32-bit to 64-bit values cause little
or no changes to the majority of the code with the following
exceptions:
    	- printk message formats
    	- division and modulus of 64-bit values
    	- NAND base support
	- 32-bit local variables used by mtdpart and mtdconcat
	- naughtily assuming one structure maps to another
	in MEMERASE ioctl

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