浏览代码

mtd: drop physmap_configure

physmap_configure() and physmap_set_partitions() have no users in kernel.
Out of kernel users should have been converted to regular platform device
long ago. Drop support for this obsolete API.

Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Dmitry Eremin-Solenikov 14 年之前
父节点
当前提交
13e0fe49f6
共有 3 个文件被更改,包括 0 次插入38 次删除
  1. 0 6
      drivers/mtd/maps/Kconfig
  2. 0 15
      drivers/mtd/maps/physmap.c
  3. 0 17
      include/linux/mtd/physmap.h

+ 0 - 6
drivers/mtd/maps/Kconfig

@@ -41,8 +41,6 @@ config MTD_PHYSMAP_START
 	  are mapped on your particular target board. Refer to the
 	  are mapped on your particular target board. Refer to the
 	  memory map which should hopefully be in the documentation for
 	  memory map which should hopefully be in the documentation for
 	  your board.
 	  your board.
-	  Ignore this option if you use run-time physmap configuration
-	  (i.e., run-time calling physmap_configure()).
 
 
 config MTD_PHYSMAP_LEN
 config MTD_PHYSMAP_LEN
 	hex "Physical length of flash mapping"
 	hex "Physical length of flash mapping"
@@ -55,8 +53,6 @@ config MTD_PHYSMAP_LEN
 	  than the total amount of flash present. Refer to the memory
 	  than the total amount of flash present. Refer to the memory
 	  map which should hopefully be in the documentation for your
 	  map which should hopefully be in the documentation for your
 	  board.
 	  board.
-	  Ignore this option if you use run-time physmap configuration
-	  (i.e., run-time calling physmap_configure()).
 
 
 config MTD_PHYSMAP_BANKWIDTH
 config MTD_PHYSMAP_BANKWIDTH
 	int "Bank width in octets"
 	int "Bank width in octets"
@@ -67,8 +63,6 @@ config MTD_PHYSMAP_BANKWIDTH
 	  in octets. For example, if you have a data bus width of 32
 	  in octets. For example, if you have a data bus width of 32
 	  bits, you would set the bus width octet value to 4. This is
 	  bits, you would set the bus width octet value to 4. This is
 	  used internally by the CFI drivers.
 	  used internally by the CFI drivers.
-	  Ignore this option if you use run-time physmap configuration
-	  (i.e., run-time calling physmap_configure()).
 
 
 config MTD_PHYSMAP_OF
 config MTD_PHYSMAP_OF
 	tristate "Flash device in physical memory map based on OF description"
 	tristate "Flash device in physical memory map based on OF description"

+ 0 - 15
drivers/mtd/maps/physmap.c

@@ -245,21 +245,6 @@ static struct platform_device physmap_flash = {
 	.num_resources	= 1,
 	.num_resources	= 1,
 	.resource	= &physmap_flash_resource,
 	.resource	= &physmap_flash_resource,
 };
 };
-
-void physmap_configure(unsigned long addr, unsigned long size,
-		int bankwidth, void (*set_vpp)(struct map_info *, int))
-{
-	physmap_flash_resource.start = addr;
-	physmap_flash_resource.end = addr + size - 1;
-	physmap_flash_data.width = bankwidth;
-	physmap_flash_data.set_vpp = set_vpp;
-}
-
-void physmap_set_partitions(struct mtd_partition *parts, int num_parts)
-{
-	physmap_flash_data.nr_parts = num_parts;
-	physmap_flash_data.parts = parts;
-}
 #endif
 #endif
 
 
 static int __init physmap_init(void)
 static int __init physmap_init(void)

+ 0 - 17
include/linux/mtd/physmap.h

@@ -32,21 +32,4 @@ struct physmap_flash_data {
 	struct mtd_partition	*parts;
 	struct mtd_partition	*parts;
 };
 };
 
 
-/*
- * Board needs to specify the exact mapping during their setup time.
- */
-void physmap_configure(unsigned long addr, unsigned long size,
-		int bankwidth, void (*set_vpp)(struct map_info *, int) );
-
-/*
- * Machines that wish to do flash partition may want to call this function in
- * their setup routine.
- *
- *	physmap_set_partitions(mypartitions, num_parts);
- *
- * Note that one can always override this hard-coded partition with
- * command line partition (you need to enable CONFIG_MTD_CMDLINE_PARTS).
- */
-void physmap_set_partitions(struct mtd_partition *parts, int num_parts);
-
 #endif /* __LINUX_MTD_PHYSMAP__ */
 #endif /* __LINUX_MTD_PHYSMAP__ */