From: Aaron Sierra Date: Wed, 17 Sep 2014 18:08:28 +0000 (-0500) Subject: mtd: physmap_of: Add non-obsolete map_rom probe X-Git-Tag: v3.18-rc1~25^2~9 X-Git-Url: https://git.karo-electronics.de/?a=commitdiff_plain;h=e5bffb59cfbb3371ff00a165a5a48c1f3fdf125a;p=karo-tx-linux.git mtd: physmap_of: Add non-obsolete map_rom probe Previously, the only way to map a NOR device as a simple ROM was to use the obsolete "direct-mapped" compatible binding (which further requires device_type = "nor" and probe-type = "NOR" properties). This patch adds an "mtd-rom" compatible binding to the "map_rom" probe type. Signed-off-by: Aaron Sierra Signed-off-by: Brian Norris --- diff --git a/Documentation/devicetree/bindings/mtd/mtd-physmap.txt b/Documentation/devicetree/bindings/mtd/mtd-physmap.txt index 61c5ec850f2f..6b9f680cb579 100644 --- a/Documentation/devicetree/bindings/mtd/mtd-physmap.txt +++ b/Documentation/devicetree/bindings/mtd/mtd-physmap.txt @@ -4,8 +4,8 @@ Flash chips (Memory Technology Devices) are often used for solid state file systems on embedded devices. - compatible : should contain the specific model of mtd chip(s) - used, if known, followed by either "cfi-flash", "jedec-flash" - or "mtd-ram". + used, if known, followed by either "cfi-flash", "jedec-flash", + "mtd-ram" or "mtd-rom". - reg : Address range(s) of the mtd chip(s) It's possible to (optionally) define multiple "reg" tuples so that non-identical chips can be described in one node. diff --git a/drivers/mtd/maps/physmap_of.c b/drivers/mtd/maps/physmap_of.c index 63d82dae4a78..c1d21cb501ca 100644 --- a/drivers/mtd/maps/physmap_of.c +++ b/drivers/mtd/maps/physmap_of.c @@ -339,6 +339,10 @@ static struct of_device_id of_flash_match[] = { .compatible = "mtd-ram", .data = (void *)"map_ram", }, + { + .compatible = "mtd-rom", + .data = (void *)"map_rom", + }, { .type = "rom", .compatible = "direct-mapped"