linux-imx

menuconfig MTD

    tristate "Memory Technology Device (MTD) support"

    imply NVMEM

    help

      Memory Technology Devices are flash, RAM and similar chips, often

      used for solid state file systems on embedded devices. This option

      will provide the generic support for MTD drivers to register

      themselves with the kernel and for potential users of MTD devices

      to enumerate the devices which are present and obtain a handle on

      them. It will also allow you to select individual drivers for

      particular hardware and users of MTD devices. If unsure, say N.

​

if MTD

​

config MTD_TESTS

    tristate "MTD tests support (DANGEROUS)"

    depends on m

    help

      This option includes various MTD tests into compilation. The tests

      should normally be compiled as kernel modules. The modules perform

      various checks and verifications when loaded.

​

      WARNING: some of the tests will ERASE entire MTD device which they

      test. Do not use these tests unless you really know what you do.

​

config MTD_CMDLINE_PARTS

    tristate "Command line partition table parsing"

    depends on MTD

    help

      Allow generic configuration of the MTD partition tables via the kernel

      command line. Multiple flash resources are supported for hardware where

      different kinds of flash memory are available.

​

      You will still need the parsing functions to be called by the driver

      for your particular device. It won't happen automatically. The

      SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for

      example.

​

      The format for the command line is as follows:

​

      mtdparts=<mtddef>[;<mtddef]

      <mtddef>  := <mtd-id>:<partdef>[,<partdef>]

      <partdef> := <size>[@offset][<name>][ro]

      <mtd-id>  := unique id used in mapping driver/device

      <size>    := standard linux memsize OR "-" to denote all

      remaining space

      <name>    := (NAME)

​

      Due to the way Linux handles the command line, no spaces are

      allowed in the partition definition, including mtd id's and partition

      names.

​

      Examples:

​

      1 flash resource (mtd-id "sa1100"), with 1 single writable partition:

      mtdparts=sa1100:-

​

      Same flash, but 2 named partitions, the first one being read-only:

      mtdparts=sa1100:256k(ARMboot)ro,-(root)

​

      If unsure, say 'N'.

​

config MTD_AFS_PARTS

    tristate "ARM Firmware Suite partition parsing"

    depends on (ARM || ARM64)

    help

      The ARM Firmware Suite allows the user to divide flash devices into

      multiple 'images'. Each such image has a header containing its name

      and offset/size etc.

​

      If you need code which can detect and parse these tables, and

      register MTD 'partitions' corresponding to each image detected,

      enable this option.

​

      You will still need the parsing functions to be called by the driver

      for your particular device. It won't happen automatically. The

      'physmap' map driver (CONFIG_MTD_PHYSMAP) does this, for example.

​

config MTD_OF_PARTS

    tristate "OpenFirmware partitioning information support"

    default y

    depends on OF

    help

      This provides a partition parsing function which derives

      the partition map from the children of the flash node,

      as described in Documentation/devicetree/bindings/mtd/partition.txt.

​

config MTD_AR7_PARTS

    tristate "TI AR7 partitioning support"

    help

      TI AR7 partitioning support

​