[deliverable/linux.git] / drivers / mtd / Kconfig

menuconfig MTD
	tristate "Memory Technology Device (MTD) support"
	depends on GENERIC_IO
	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_REDBOOT_PARTS
	tristate "RedBoot partition table parsing"
	---help---
	  RedBoot is a ROM monitor and bootloader which deals with multiple
	  'images' in flash devices by putting a table one of the erase
	  blocks on the device, similar to a partition table, which gives
	  the offsets, lengths and names of all the images stored in the
	  flash.

	  If you need code which can detect and parse this table, and register
	  MTD 'partitions' corresponding to each image in the table, 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
	  SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
	  example.

if MTD_REDBOOT_PARTS

config MTD_REDBOOT_DIRECTORY_BLOCK
	int "Location of RedBoot partition table"
	default "-1"
	---help---
	  This option is the Linux counterpart to the
	  CYGNUM_REDBOOT_FIS_DIRECTORY_BLOCK RedBoot compile time
	  option.

	  The option specifies which Flash sectors holds the RedBoot
	  partition table.  A zero or positive value gives an absolute
	  erase block number. A negative value specifies a number of
	  sectors before the end of the device.

	  For example "2" means block number 2, "-1" means the last
	  block and "-2" means the penultimate block.

config MTD_REDBOOT_PARTS_UNALLOCATED
	bool "Include unallocated flash regions"
	help
	  If you need to register each unallocated flash region as a MTD
	  'partition', enable this option.

config MTD_REDBOOT_PARTS_READONLY
	bool "Force read-only for RedBoot system images"
	help
	  If you need to force read-only for 'RedBoot', 'RedBoot Config' and
	  'FIS directory' images, enable this option.

endif # MTD_REDBOOT_PARTS

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
	---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/booting-without-of.txt.

config MTD_AR7_PARTS
	tristate "TI AR7 partitioning support"
	---help---
	  TI AR7 partitioning support

config MTD_BCM63XX_PARTS
	tristate "BCM63XX CFE partitioning support"
	depends on BCM63XX
	select CRC32
	help
	  This provides partions parsing for BCM63xx devices with CFE
	  bootloaders.

config MTD_BCM47XX_PARTS
	tristate "BCM47XX partitioning support"
	depends on BCM47XX
	help
	  This provides partitions parser for devices based on BCM47xx
	  boards.

comment "User Modules And Translation Layers"

config MTD_BLKDEVS
	tristate "Common interface to block layer for MTD 'translation layers'"
	depends on BLOCK
	default n

config MTD_BLOCK
	tristate "Caching block device access to MTD devices"
	depends on BLOCK
	select MTD_BLKDEVS
	---help---
	  Although most flash chips have an erase size too large to be useful
	  as block devices, it is possible to use MTD devices which are based
	  on RAM chips in this manner. This block device is a user of MTD
	  devices performing that function.

	  At the moment, it is also required for the Journalling Flash File
	  System(s) to obtain a handle on the MTD device when it's mounted
	  (although JFFS and JFFS2 don't actually use any of the functionality
	  of the mtdblock device).

	  Later, it may be extended to perform read/erase/modify/write cycles
	  on flash chips to emulate a smaller block size. Needless to say,
	  this is very unsafe, but could be useful for file systems which are
	  almost never written to.

	  You do not need this option for use with the DiskOnChip devices. For
	  those, enable NFTL support (CONFIG_NFTL) instead.

config MTD_BLOCK_RO
	tristate "Readonly block device access to MTD devices"
	depends on MTD_BLOCK!=y && BLOCK
	select MTD_BLKDEVS
	help
	  This allows you to mount read-only file systems (such as cramfs)
	  from an MTD device, without the overhead (and danger) of the caching
	  driver.

	  You do not need this option for use with the DiskOnChip devices. For
	  those, enable NFTL support (CONFIG_NFTL) instead.

config FTL
	tristate "FTL (Flash Translation Layer) support"
	depends on BLOCK
	select MTD_BLKDEVS
	---help---
	  This provides support for the original Flash Translation Layer which
	  is part of the PCMCIA specification. It uses a kind of pseudo-
	  file system on a flash device to emulate a block device with
	  512-byte sectors, on top of which you put a 'normal' file system.

	  You may find that the algorithms used in this code are patented
	  unless you live in the Free World where software patents aren't
	  legal - in the USA you are only permitted to use this on PCMCIA
	  hardware, although under the terms of the GPL you're obviously
	  permitted to copy, modify and distribute the code as you wish. Just
	  not use it.

config NFTL
	tristate "NFTL (NAND Flash Translation Layer) support"
	depends on BLOCK
	select MTD_BLKDEVS
	---help---
	  This provides support for the NAND Flash Translation Layer which is
	  used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
	  file system on a flash device to emulate a block device with
	  512-byte sectors, on top of which you put a 'normal' file system.

	  You may find that the algorithms used in this code are patented
	  unless you live in the Free World where software patents aren't
	  legal - in the USA you are only permitted to use this on DiskOnChip
	  hardware, although under the terms of the GPL you're obviously
	  permitted to copy, modify and distribute the code as you wish. Just
	  not use it.

config NFTL_RW
	bool "Write support for NFTL"
	depends on NFTL
	help
	  Support for writing to the NAND Flash Translation Layer, as used
	  on the DiskOnChip.

config INFTL
	tristate "INFTL (Inverse NAND Flash Translation Layer) support"
	depends on BLOCK
	select MTD_BLKDEVS
	---help---
	  This provides support for the Inverse NAND Flash Translation
	  Layer which is used on M-Systems' newer DiskOnChip devices. It
	  uses a kind of pseudo-file system on a flash device to emulate
	  a block device with 512-byte sectors, on top of which you put
	  a 'normal' file system.

	  You may find that the algorithms used in this code are patented
	  unless you live in the Free World where software patents aren't
	  legal - in the USA you are only permitted to use this on DiskOnChip
	  hardware, although under the terms of the GPL you're obviously
	  permitted to copy, modify and distribute the code as you wish. Just
	  not use it.

config RFD_FTL
        tristate "Resident Flash Disk (Flash Translation Layer) support"
	depends on BLOCK
	select MTD_BLKDEVS
	---help---
	  This provides support for the flash translation layer known
	  as the Resident Flash Disk (RFD), as used by the Embedded BIOS
	  of General Software. There is a blurb at:

		http://www.gensw.com/pages/prod/bios/rfd.htm

config SSFDC
	tristate "NAND SSFDC (SmartMedia) read only translation layer"
	depends on BLOCK
	select MTD_BLKDEVS
	help
	  This enables read only access to SmartMedia formatted NAND
	  flash. You can mount it with FAT file system.


config SM_FTL
	tristate "SmartMedia/xD new translation layer"
	depends on BLOCK
	select MTD_BLKDEVS
	select MTD_NAND_ECC
	help
	  This enables EXPERIMENTAL R/W support for SmartMedia/xD
	  FTL (Flash translation layer).
	  Write support is only lightly tested, therefore this driver
	  isn't recommended to use with valuable data (anyway if you have
	  valuable data, do backups regardless of software/hardware you
	  use, because you never know what will eat your data...)
	  If you only need R/O access, you can use older R/O driver
	  (CONFIG_SSFDC)

config MTD_OOPS
	tristate "Log panic/oops to an MTD buffer"
	help
	  This enables panic and oops messages to be logged to a circular
	  buffer in a flash partition where it can be read back at some
	  later point.

config MTD_SWAP
	tristate "Swap on MTD device support"
	depends on MTD && SWAP
	select MTD_BLKDEVS
	help
	  Provides volatile block device driver on top of mtd partition
          suitable for swapping.  The mapping of written blocks is not saved.
	  The driver provides wear leveling by storing erase counter into the
	  OOB.

source "drivers/mtd/chips/Kconfig"

source "drivers/mtd/maps/Kconfig"

source "drivers/mtd/devices/Kconfig"

source "drivers/mtd/nand/Kconfig"

source "drivers/mtd/onenand/Kconfig"

source "drivers/mtd/lpddr/Kconfig"

source "drivers/mtd/ubi/Kconfig"

endif # MTD
Commit	Line	Data
	1	menuconfig MTD
	2	tristate "Memory Technology Device (MTD) support"
	3	depends on GENERIC_IO
	4	help
	5	Memory Technology Devices are flash, RAM and similar chips, often
	6	used for solid state file systems on embedded devices. This option
	7	will provide the generic support for MTD drivers to register
	8	themselves with the kernel and for potential users of MTD devices
	9	to enumerate the devices which are present and obtain a handle on
	10	them. It will also allow you to select individual drivers for
	11	particular hardware and users of MTD devices. If unsure, say N.
	12
	13	if MTD
	14
	15	config MTD_TESTS
	16	tristate "MTD tests support (DANGEROUS)"
	17	depends on m
	18	help
	19	This option includes various MTD tests into compilation. The tests
	20	should normally be compiled as kernel modules. The modules perform
	21	various checks and verifications when loaded.
	22
	23	WARNING: some of the tests will ERASE entire MTD device which they
	24	test. Do not use these tests unless you really know what you do.
	25
	26	config MTD_REDBOOT_PARTS
	27	tristate "RedBoot partition table parsing"
	28	---help---
	29	RedBoot is a ROM monitor and bootloader which deals with multiple
	30	'images' in flash devices by putting a table one of the erase
	31	blocks on the device, similar to a partition table, which gives
	32	the offsets, lengths and names of all the images stored in the
	33	flash.
	34
	35	If you need code which can detect and parse this table, and register
	36	MTD 'partitions' corresponding to each image in the table, enable
	37	this option.
	38
	39	You will still need the parsing functions to be called by the driver
	40	for your particular device. It won't happen automatically. The
	41	SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
	42	example.
	43
	44	if MTD_REDBOOT_PARTS
	45
	46	config MTD_REDBOOT_DIRECTORY_BLOCK
	47	int "Location of RedBoot partition table"
	48	default "-1"
	49	---help---
	50	This option is the Linux counterpart to the
	51	CYGNUM_REDBOOT_FIS_DIRECTORY_BLOCK RedBoot compile time
	52	option.
	53
	54	The option specifies which Flash sectors holds the RedBoot
	55	partition table. A zero or positive value gives an absolute
	56	erase block number. A negative value specifies a number of
	57	sectors before the end of the device.
	58
	59	For example "2" means block number 2, "-1" means the last
	60	block and "-2" means the penultimate block.
	61
	62	config MTD_REDBOOT_PARTS_UNALLOCATED
	63	bool "Include unallocated flash regions"
	64	help
	65	If you need to register each unallocated flash region as a MTD
	66	'partition', enable this option.
	67
	68	config MTD_REDBOOT_PARTS_READONLY
	69	bool "Force read-only for RedBoot system images"
	70	help
	71	If you need to force read-only for 'RedBoot', 'RedBoot Config' and
	72	'FIS directory' images, enable this option.
	73
	74	endif # MTD_REDBOOT_PARTS
	75
	76	config MTD_CMDLINE_PARTS
	77	tristate "Command line partition table parsing"
	78	depends on MTD
	79	---help---
	80	Allow generic configuration of the MTD partition tables via the kernel
	81	command line. Multiple flash resources are supported for hardware where
	82	different kinds of flash memory are available.
	83
	84	You will still need the parsing functions to be called by the driver
	85	for your particular device. It won't happen automatically. The
	86	SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
	87	example.
	88
	89	The format for the command line is as follows:
	90
	91	mtdparts=<mtddef>[;<mtddef]
	92	<mtddef> := <mtd-id>:<partdef>[,<partdef>]
	93	<partdef> := <size>[@offset][<name>][ro]
	94	<mtd-id> := unique id used in mapping driver/device
	95	<size> := standard linux memsize OR "-" to denote all
	96	remaining space
	97	<name> := (NAME)
	98
	99	Due to the way Linux handles the command line, no spaces are
	100	allowed in the partition definition, including mtd id's and partition
	101	names.
	102
	103	Examples:
	104
	105	1 flash resource (mtd-id "sa1100"), with 1 single writable partition:
	106	mtdparts=sa1100:-
	107
	108	Same flash, but 2 named partitions, the first one being read-only:
	109	mtdparts=sa1100:256k(ARMboot)ro,-(root)
	110
	111	If unsure, say 'N'.
	112
	113	config MTD_AFS_PARTS
	114	tristate "ARM Firmware Suite partition parsing"
	115	depends on ARM
	116	---help---
	117	The ARM Firmware Suite allows the user to divide flash devices into
	118	multiple 'images'. Each such image has a header containing its name
	119	and offset/size etc.
	120
	121	If you need code which can detect and parse these tables, and
	122	register MTD 'partitions' corresponding to each image detected,
	123	enable this option.
	124
	125	You will still need the parsing functions to be called by the driver
	126	for your particular device. It won't happen automatically. The
	127	'physmap' map driver (CONFIG_MTD_PHYSMAP) does this, for example.
	128
	129	config MTD_OF_PARTS
	130	tristate "OpenFirmware partitioning information support"
	131	default y
	132	depends on OF
	133	help
	134	This provides a partition parsing function which derives
	135	the partition map from the children of the flash node,
	136	as described in Documentation/devicetree/booting-without-of.txt.
	137
	138	config MTD_AR7_PARTS
	139	tristate "TI AR7 partitioning support"
	140	---help---
	141	TI AR7 partitioning support
	142
	143	config MTD_BCM63XX_PARTS
	144	tristate "BCM63XX CFE partitioning support"
	145	depends on BCM63XX
	146	select CRC32
	147	help
	148	This provides partions parsing for BCM63xx devices with CFE
	149	bootloaders.
	150
	151	config MTD_BCM47XX_PARTS
	152	tristate "BCM47XX partitioning support"
	153	depends on BCM47XX
	154	help
	155	This provides partitions parser for devices based on BCM47xx
	156	boards.
	157
	158	comment "User Modules And Translation Layers"
	159
	160	config MTD_BLKDEVS
	161	tristate "Common interface to block layer for MTD 'translation layers'"
	162	depends on BLOCK
	163	default n
	164
	165	config MTD_BLOCK
	166	tristate "Caching block device access to MTD devices"
	167	depends on BLOCK
	168	select MTD_BLKDEVS
	169	---help---
	170	Although most flash chips have an erase size too large to be useful
	171	as block devices, it is possible to use MTD devices which are based
	172	on RAM chips in this manner. This block device is a user of MTD
	173	devices performing that function.
	174
	175	At the moment, it is also required for the Journalling Flash File
	176	System(s) to obtain a handle on the MTD device when it's mounted
	177	(although JFFS and JFFS2 don't actually use any of the functionality
	178	of the mtdblock device).
	179
	180	Later, it may be extended to perform read/erase/modify/write cycles
	181	on flash chips to emulate a smaller block size. Needless to say,
	182	this is very unsafe, but could be useful for file systems which are
	183	almost never written to.
	184
	185	You do not need this option for use with the DiskOnChip devices. For
	186	those, enable NFTL support (CONFIG_NFTL) instead.
	187
	188	config MTD_BLOCK_RO
	189	tristate "Readonly block device access to MTD devices"
	190	depends on MTD_BLOCK!=y && BLOCK
	191	select MTD_BLKDEVS
	192	help
	193	This allows you to mount read-only file systems (such as cramfs)
	194	from an MTD device, without the overhead (and danger) of the caching
	195	driver.
	196
	197	You do not need this option for use with the DiskOnChip devices. For
	198	those, enable NFTL support (CONFIG_NFTL) instead.
	199
	200	config FTL
	201	tristate "FTL (Flash Translation Layer) support"
	202	depends on BLOCK
	203	select MTD_BLKDEVS
	204	---help---
	205	This provides support for the original Flash Translation Layer which
	206	is part of the PCMCIA specification. It uses a kind of pseudo-
	207	file system on a flash device to emulate a block device with
	208	512-byte sectors, on top of which you put a 'normal' file system.
	209
	210	You may find that the algorithms used in this code are patented
	211	unless you live in the Free World where software patents aren't
	212	legal - in the USA you are only permitted to use this on PCMCIA
	213	hardware, although under the terms of the GPL you're obviously
	214	permitted to copy, modify and distribute the code as you wish. Just
	215	not use it.
	216
	217	config NFTL
	218	tristate "NFTL (NAND Flash Translation Layer) support"
	219	depends on BLOCK
	220	select MTD_BLKDEVS
	221	---help---
	222	This provides support for the NAND Flash Translation Layer which is
	223	used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
	224	file system on a flash device to emulate a block device with
	225	512-byte sectors, on top of which you put a 'normal' file system.
	226
	227	You may find that the algorithms used in this code are patented
	228	unless you live in the Free World where software patents aren't
	229	legal - in the USA you are only permitted to use this on DiskOnChip
	230	hardware, although under the terms of the GPL you're obviously
	231	permitted to copy, modify and distribute the code as you wish. Just
	232	not use it.
	233
	234	config NFTL_RW
	235	bool "Write support for NFTL"
	236	depends on NFTL
	237	help
	238	Support for writing to the NAND Flash Translation Layer, as used
	239	on the DiskOnChip.
	240
	241	config INFTL
	242	tristate "INFTL (Inverse NAND Flash Translation Layer) support"
	243	depends on BLOCK
	244	select MTD_BLKDEVS
	245	---help---
	246	This provides support for the Inverse NAND Flash Translation
	247	Layer which is used on M-Systems' newer DiskOnChip devices. It
	248	uses a kind of pseudo-file system on a flash device to emulate
	249	a block device with 512-byte sectors, on top of which you put
	250	a 'normal' file system.
	251
	252	You may find that the algorithms used in this code are patented
	253	unless you live in the Free World where software patents aren't
	254	legal - in the USA you are only permitted to use this on DiskOnChip
	255	hardware, although under the terms of the GPL you're obviously
	256	permitted to copy, modify and distribute the code as you wish. Just
	257	not use it.
	258
	259	config RFD_FTL
	260	tristate "Resident Flash Disk (Flash Translation Layer) support"
	261	depends on BLOCK
	262	select MTD_BLKDEVS
	263	---help---
	264	This provides support for the flash translation layer known
	265	as the Resident Flash Disk (RFD), as used by the Embedded BIOS
	266	of General Software. There is a blurb at:
	267
	268	http://www.gensw.com/pages/prod/bios/rfd.htm
	269
	270	config SSFDC
	271	tristate "NAND SSFDC (SmartMedia) read only translation layer"
	272	depends on BLOCK
	273	select MTD_BLKDEVS
	274	help
	275	This enables read only access to SmartMedia formatted NAND
	276	flash. You can mount it with FAT file system.
	277
	278
	279	config SM_FTL
	280	tristate "SmartMedia/xD new translation layer"
	281	depends on BLOCK
	282	select MTD_BLKDEVS
	283	select MTD_NAND_ECC
	284	help
	285	This enables EXPERIMENTAL R/W support for SmartMedia/xD
	286	FTL (Flash translation layer).
	287	Write support is only lightly tested, therefore this driver
	288	isn't recommended to use with valuable data (anyway if you have
	289	valuable data, do backups regardless of software/hardware you
	290	use, because you never know what will eat your data...)
	291	If you only need R/O access, you can use older R/O driver
	292	(CONFIG_SSFDC)
	293
	294	config MTD_OOPS
	295	tristate "Log panic/oops to an MTD buffer"
	296	help
	297	This enables panic and oops messages to be logged to a circular
	298	buffer in a flash partition where it can be read back at some
	299	later point.
	300
	301	config MTD_SWAP
	302	tristate "Swap on MTD device support"
	303	depends on MTD && SWAP
	304	select MTD_BLKDEVS
	305	help
	306	Provides volatile block device driver on top of mtd partition
	307	suitable for swapping. The mapping of written blocks is not saved.
	308	The driver provides wear leveling by storing erase counter into the
	309	OOB.
	310
	311	source "drivers/mtd/chips/Kconfig"
	312
	313	source "drivers/mtd/maps/Kconfig"
	314
	315	source "drivers/mtd/devices/Kconfig"
	316
	317	source "drivers/mtd/nand/Kconfig"
	318
	319	source "drivers/mtd/onenand/Kconfig"
	320
	321	source "drivers/mtd/lpddr/Kconfig"
	322
	323	source "drivers/mtd/ubi/Kconfig"
	324
	325	endif # MTD