xref: /linux/drivers/mtd/parsers/Kconfig (revision 5a4a335aa8d5181e76b6c5fc3c236ac202287cf0)
1# SPDX-License-Identifier: GPL-2.0-only
2config MTD_AR7_PARTS
3	tristate "TI AR7 partitioning parser"
4	help
5	  TI AR7 partitioning parser support
6
7config MTD_PARSER_IMAGETAG
8	tristate "Parser for BCM963XX Image Tag format partitions"
9	depends on BCM63XX || BMIPS_GENERIC || COMPILE_TEST
10	select CRC32
11	help
12	  Image Tag is the firmware header used by broadcom on their xDSL line
13	  of devices. It is used to describe the offsets and lengths of kernel
14	  and rootfs partitions.
15	  This driver adds support for parsing a partition with an Image Tag
16	  header and creates up to two partitions, kernel and rootfs.
17
18config MTD_AFS_PARTS
19	tristate "ARM Firmware Suite partition parsing"
20	depends on (ARM || ARM64)
21	help
22	  The ARM Firmware Suite allows the user to divide flash devices into
23	  multiple 'images'. Each such image has a header containing its name
24	  and offset/size etc.
25
26	  If you need code which can detect and parse these tables, and
27	  register MTD 'partitions' corresponding to each image detected,
28	  enable this option.
29
30	  You will still need the parsing functions to be called by the driver
31	  for your particular device. It won't happen automatically. The
32	  'physmap' map driver (CONFIG_MTD_PHYSMAP) does this, for example.
33
34config MTD_PARSER_TRX
35	tristate "Parser for TRX format partitions"
36	depends on MTD && (BCM47XX || ARCH_BCM_5301X || COMPILE_TEST)
37	help
38	  TRX is a firmware format used by Broadcom on their devices. It
39	  may contain up to 3/4 partitions (depending on the version).
40	  This driver will parse TRX header and report at least two partitions:
41	  kernel and rootfs.
42
43config MTD_SHARPSL_PARTS
44	tristate "Sharp SL Series NAND flash partition parser"
45	depends on MTD_NAND_SHARPSL || MTD_NAND_TMIO || COMPILE_TEST
46	help
47	  This provides the read-only FTL logic necessary to read the partition
48	  table from the NAND flash of Sharp SL Series (Zaurus) and the MTD
49	  partition parser using this code.
50
51config MTD_REDBOOT_PARTS
52	tristate "RedBoot partition table parsing"
53	help
54	  RedBoot is a ROM monitor and bootloader which deals with multiple
55	  'images' in flash devices by putting a table one of the erase
56	  blocks on the device, similar to a partition table, which gives
57	  the offsets, lengths and names of all the images stored in the
58	  flash.
59
60	  If you need code which can detect and parse this table, and register
61	  MTD 'partitions' corresponding to each image in the table, enable
62	  this option.
63
64	  You will still need the parsing functions to be called by the driver
65	  for your particular device. It won't happen automatically. The
66	  SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
67	  example.
68
69if MTD_REDBOOT_PARTS
70
71config MTD_REDBOOT_DIRECTORY_BLOCK
72	int "Location of RedBoot partition table"
73	default "-1"
74	help
75	  This option is the Linux counterpart to the
76	  CYGNUM_REDBOOT_FIS_DIRECTORY_BLOCK RedBoot compile time
77	  option.
78
79	  The option specifies which Flash sectors holds the RedBoot
80	  partition table.  A zero or positive value gives an absolute
81	  erase block number. A negative value specifies a number of
82	  sectors before the end of the device.
83
84	  For example "2" means block number 2, "-1" means the last
85	  block and "-2" means the penultimate block.
86
87config MTD_REDBOOT_PARTS_UNALLOCATED
88	bool "Include unallocated flash regions"
89	help
90	  If you need to register each unallocated flash region as a MTD
91	  'partition', enable this option.
92
93config MTD_REDBOOT_PARTS_READONLY
94	bool "Force read-only for RedBoot system images"
95	help
96	  If you need to force read-only for 'RedBoot', 'RedBoot Config' and
97	  'FIS directory' images, enable this option.
98
99endif # MTD_REDBOOT_PARTS
100