forked from ~ljy/RK356X_SDK_RELEASE
blame | history | patch | commit | commitdiff
hc
2024-02-20 ea08eeccae9297f7aabd2ef7f0c2517ac4549acc 
 kernel/drivers/mtd/Kconfig
....@@ -1,5 +1,6 @@
11 menuconfig MTD
22 	tristate "Memory Technology Device (MTD) support"
3
+	imply NVMEM
34 	help
45 	  Memory Technology Devices are flash, RAM and similar chips, often
56 	  used for solid state file systems on embedded devices. This option
....@@ -21,138 +22,6 @@
2122 
2223 	  WARNING: some of the tests will ERASE entire MTD device which they
2324 	  test. Do not use these tests unless you really know what you do.
24
-
25
-config MTD_REDBOOT_PARTS
26
-	tristate "RedBoot partition table parsing"
27
-	help
28
-	  RedBoot is a ROM monitor and bootloader which deals with multiple
29
-	  'images' in flash devices by putting a table one of the erase
30
-	  blocks on the device, similar to a partition table, which gives
31
-	  the offsets, lengths and names of all the images stored in the
32
-	  flash.
33
-
34
-	  If you need code which can detect and parse this table, and register
35
-	  MTD 'partitions' corresponding to each image in the table, enable
36
-	  this option.
37
-
38
-	  You will still need the parsing functions to be called by the driver
39
-	  for your particular device. It won't happen automatically. The
40
-	  SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
41
-	  example.
42
-
43
-if MTD_REDBOOT_PARTS
44
-
45
-config MTD_REDBOOT_DIRECTORY_BLOCK
46
-	int "Location of RedBoot partition table"
47
-	default "-1"
48
-	help
49
-	  This option is the Linux counterpart to the
50
-	  CYGNUM_REDBOOT_FIS_DIRECTORY_BLOCK RedBoot compile time
51
-	  option.
52
-
53
-	  The option specifies which Flash sectors holds the RedBoot
54
-	  partition table.  A zero or positive value gives an absolute
55
-	  erase block number. A negative value specifies a number of
56
-	  sectors before the end of the device.
57
-
58
-	  For example "2" means block number 2, "-1" means the last
59
-	  block and "-2" means the penultimate block.
60
-
61
-config MTD_REDBOOT_PARTS_UNALLOCATED
62
-	bool "Include unallocated flash regions"
63
-	help
64
-	  If you need to register each unallocated flash region as a MTD
65
-	  'partition', enable this option.
66
-
67
-config MTD_REDBOOT_PARTS_READONLY
68
-	bool "Force read-only for RedBoot system images"
69
-	help
70
-	  If you need to force read-only for 'RedBoot', 'RedBoot Config' and
71
-	  'FIS directory' images, enable this option.
72
-
73
-endif # MTD_REDBOOT_PARTS
74
-
75
-config MTD_CMDLINE_PARTS
76
-	tristate "Command line partition table parsing"
77
-	depends on MTD
78
-	help
79
-	  Allow generic configuration of the MTD partition tables via the kernel
80
-	  command line. Multiple flash resources are supported for hardware where
81
-	  different kinds of flash memory are available.
82
-
83
-	  You will still need the parsing functions to be called by the driver
84
-	  for your particular device. It won't happen automatically. The
85
-	  SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
86
-	  example.
87
-
88
-	  The format for the command line is as follows:
89
-
90
-	  mtdparts=<mtddef>[;<mtddef]
91
-	  <mtddef>  := <mtd-id>:<partdef>[,<partdef>]
92
-	  <partdef> := <size>[@offset][<name>][ro]
93
-	  <mtd-id>  := unique id used in mapping driver/device
94
-	  <size>    := standard linux memsize OR "-" to denote all
95
-	  remaining space
96
-	  <name>    := (NAME)
97
-
98
-	  Due to the way Linux handles the command line, no spaces are
99
-	  allowed in the partition definition, including mtd id's and partition
100
-	  names.
101
-
102
-	  Examples:
103
-
104
-	  1 flash resource (mtd-id "sa1100"), with 1 single writable partition:
105
-	  mtdparts=sa1100:-
106
-
107
-	  Same flash, but 2 named partitions, the first one being read-only:
108
-	  mtdparts=sa1100:256k(ARMboot)ro,-(root)
109
-
110
-	  If unsure, say 'N'.
111
-
112
-config MTD_AFS_PARTS
113
-	tristate "ARM Firmware Suite partition parsing"
114
-	depends on (ARM || ARM64)
115
-	help
116
-	  The ARM Firmware Suite allows the user to divide flash devices into
117
-	  multiple 'images'. Each such image has a header containing its name
118
-	  and offset/size etc.
119
-
120
-	  If you need code which can detect and parse these tables, and
121
-	  register MTD 'partitions' corresponding to each image detected,
122
-	  enable this option.
123
-
124
-	  You will still need the parsing functions to be called by the driver
125
-	  for your particular device. It won't happen automatically. The
126
-	  'physmap' map driver (CONFIG_MTD_PHYSMAP) does this, for example.
127
-
128
-config MTD_OF_PARTS
129
-	tristate "OpenFirmware partitioning information support"
130
-	default y
131
-	depends on OF
132
-	help
133
-	  This provides a partition parsing function which derives
134
-	  the partition map from the children of the flash node,
135
-	  as described in Documentation/devicetree/bindings/mtd/partition.txt.
136
-
137
-config MTD_AR7_PARTS
138
-	tristate "TI AR7 partitioning support"
139
-	help
140
-	  TI AR7 partitioning support
141
-
142
-config MTD_BCM63XX_PARTS
143
-	tristate "BCM63XX CFE partitioning support"
144
-	depends on BCM63XX || BMIPS_GENERIC || COMPILE_TEST
145
-	select CRC32
146
-	help
147
-	  This provides partions parsing for BCM63xx devices with CFE
148
-	  bootloaders.
149
-
150
-config MTD_BCM47XX_PARTS
151
-	tristate "BCM47XX partitioning support"
152
-	depends on BCM47XX || ARCH_BCM_5301X
153
-	help
154
-	  This provides partitions parser for devices based on BCM47xx
155
-	  boards.
15625 
15726 menu "Partition parsers"
15827 source "drivers/mtd/parsers/Kconfig"
....@@ -279,12 +148,11 @@
279148 	  This enables read only access to SmartMedia formatted NAND
280149 	  flash. You can mount it with FAT file system.
281150 
282
-
283151 config SM_FTL
284152 	tristate "SmartMedia/xD new translation layer"
285153 	depends on BLOCK
286154 	select MTD_BLKDEVS
287
-	select MTD_NAND_ECC
155
+	select MTD_NAND_ECC_SW_HAMMING
288156 	help
289157 	  This enables EXPERIMENTAL R/W support for SmartMedia/xD
290158 	  FTL (Flash translation layer).
....@@ -301,6 +169,16 @@
301169 	  This enables panic and oops messages to be logged to a circular
302170 	  buffer in a flash partition where it can be read back at some
303171 	  later point.
172
+
173
+config MTD_PSTORE
174
+	tristate "Log panic/oops to an MTD buffer based on pstore"
175
+	depends on PSTORE_BLK
176
+	help
177
+	  This enables panic and oops messages to be logged to a circular
178
+	  buffer in a flash partition where it can be read back as files after
179
+	  mounting pstore filesystem.
180
+
181
+	  If unsure, say N.
304182 
305183 config MTD_SWAP
306184 	tristate "Swap on MTD device support"
....@@ -339,4 +217,6 @@
339217 
340218 source "drivers/mtd/ubi/Kconfig"
341219 
220
+source "drivers/mtd/hyperbus/Kconfig"
221
+
342222 endif # MTD