summaryrefslogtreecommitdiff
path: root/drivers/mtd/maps
diff options
context:
space:
mode:
authorWolfram Sang <w.sang@pengutronix.de>2009-07-17 14:39:23 +0200
committerDavid Woodhouse <David.Woodhouse@intel.com>2009-09-19 13:15:26 -0700
commitfc28c39f0ef59bfb649ddfd633275be8e45c0f9c (patch)
tree7a1e8d0b1bc015b5cc9584db3ac7805269036479 /drivers/mtd/maps
parent223cf6c3b517cf6ef040cafe45af89f3b8adba74 (diff)
downloadlinux-3.10-fc28c39f0ef59bfb649ddfd633275be8e45c0f9c.tar.gz
linux-3.10-fc28c39f0ef59bfb649ddfd633275be8e45c0f9c.tar.bz2
linux-3.10-fc28c39f0ef59bfb649ddfd633275be8e45c0f9c.zip
mtd: maps: add mtd-ram support to physmap_of
Use physmap_of to access RAMs as mtd and add documenation for it. This approach is a lot less intrusive as adding an of-wrapper around plat-ram.c. As most extensions of plat-ram.c (e.g. custom map-functions) can't be mapped to the device tree anyhow, extending physmap_of seems to be the cleanest approach. Tested with a phyCORE-MPC5121e. Signed-off-by: Wolfram Sang <w.sang@pengutronix.de> Cc: Vitaly Wool <vwool@ru.mvista.com> Cc: Artem Bityutskiy <dedekind@infradead.org> Cc: Ken MacLeod <ken@bitsko.slc.ut.us> Cc: Albrecht Dreß <albrecht.dress@arcor.de> Acked-by: Grant Likely <grant.likely@secretlab.ca> Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
Diffstat (limited to 'drivers/mtd/maps')
-rw-r--r--drivers/mtd/maps/physmap_of.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/drivers/mtd/maps/physmap_of.c b/drivers/mtd/maps/physmap_of.c
index e828d58910f..61e4eb48bb2 100644
--- a/drivers/mtd/maps/physmap_of.c
+++ b/drivers/mtd/maps/physmap_of.c
@@ -362,6 +362,10 @@ static struct of_device_id of_flash_match[] = {
.data = (void *)"jedec_probe",
},
{
+ .compatible = "mtd-ram",
+ .data = (void *)"map_ram",
+ },
+ {
.type = "rom",
.compatible = "direct-mapped"
},