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>

1 files changed, 0 insertions, 6 deletions

diff --git a/drivers/mtd/maps/Kconfig b/drivers/mtd/maps/Kconfig
index 11cc2307c2ca..46eca3b3bcb0 100644
--- a/drivers/mtd/maps/Kconfig
+++ b/drivers/mtd/maps/Kconfig
@@ -41,8 +41,6 @@ config MTD_PHYSMAP_START
           are mapped on your particular target board. Refer to the
           memory map which should hopefully be in the documentation for
           your board.
-          Ignore this option if you use run-time physmap configuration
-          (i.e., run-time calling physmap_configure()).
 
 config MTD_PHYSMAP_LEN
         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
           map which should hopefully be in the documentation for your
           board.
-          Ignore this option if you use run-time physmap configuration
-          (i.e., run-time calling physmap_configure()).
 
 config MTD_PHYSMAP_BANKWIDTH
         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
           bits, you would set the bus width octet value to 4. This is
           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
         tristate "Flash device in physical memory map based on OF description"