PageRenderTime 18ms CodeModel.GetById 15ms app.highlight 1ms RepoModel.GetById 0ms app.codeStats 0ms

/drivers/mtd/Kconfig

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