add wifi6 8852be driver

hc

2024-12-19 9370bb92b2d16684ee45cf24e879c93c509162da

 kernel/drivers/mtd/maps/Kconfig
..
..
@@ -1,3 +1,4 @@
1
+# SPDX-License-Identifier: GPL-2.0-only
1
2
 menu "Mapping drivers for chip access"
2
3
 	depends on MTD!=n
3
4
 	depends on HAS_IOMEM
..
..
@@ -10,7 +11,7 @@
10
11
 
11
12
 config MTD_PHYSMAP
12
13
 	tristate "Flash device in physical memory map"
13
-	depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM || MTD_LPDDR
14
+	depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM || MTD_RAM || MTD_LPDDR
14
15
 	help
15
16
 	  This provides a 'mapping' driver which allows the NOR Flash and
16
17
 	  ROM driver code to communicate with chips which are mapped
..
..
@@ -66,15 +67,26 @@
66
67
 	  used internally by the CFI drivers.
67
68
 
68
69
 config MTD_PHYSMAP_OF
69
-	tristate "Memory device in physical memory map based on OF description"
70
-	depends on OF && (MTD_CFI || MTD_JEDECPROBE || MTD_ROM || MTD_RAM)
70
+	bool "Memory device in physical memory map based on OF description"
71
+	depends on OF && MTD_PHYSMAP
71
72
 	help
72
73
 	  This provides a 'mapping' driver which allows the NOR Flash, ROM
73
74
 	  and RAM driver code to communicate with chips which are mapped
74
75
 	  physically into the CPU's memory. The mapping description here is
75
76
 	  taken from OF device tree.
76
77
 
77
-config MTD_PHYSMAP_OF_VERSATILE
78
+config MTD_PHYSMAP_BT1_ROM
79
+	bool "Baikal-T1 Boot ROMs OF-based physical memory map handling"
80
+	depends on MTD_PHYSMAP_OF
81
+	depends on MIPS_BAIKAL_T1 || COMPILE_TEST
82
+	select MTD_COMPLEX_MAPPINGS
83
+	select MULTIPLEXER
84
+	select MUX_MMIO
85
+	help
86
+	  This provides some extra DT physmap parsing for the Baikal-T1
87
+	  platforms, some detection and setting up ROMs-specific accessors.
88
+
89
+config MTD_PHYSMAP_VERSATILE
78
90
 	bool "ARM Versatile OF-based physical memory map handling"
79
91
 	depends on MTD_PHYSMAP_OF
80
92
 	depends on MFD_SYSCON
..
..
@@ -84,15 +96,36 @@
84
96
 	  platforms, basically to add a VPP (write protection) callback so
85
97
 	  the flash can be taken out of write protection.
86
98
 
87
-config MTD_PHYSMAP_OF_GEMINI
99
+config MTD_PHYSMAP_GEMINI
88
100
 	bool "Cortina Gemini OF-based physical memory map handling"
89
101
 	depends on MTD_PHYSMAP_OF
90
102
 	depends on MFD_SYSCON
103
+	select MTD_COMPLEX_MAPPINGS
91
104
 	default ARCH_GEMINI
92
105
 	help
93
106
 	  This provides some extra DT physmap parsing for the Gemini
94
107
 	  platforms, some detection and setting up parallel mode on the
95
108
 	  external interface.
109
+
110
+config MTD_PHYSMAP_IXP4XX
111
+	bool "Intel IXP4xx OF-based physical memory map handling"
112
+	depends on MTD_PHYSMAP_OF
113
+	depends on ARM
114
+	select MTD_COMPLEX_MAPPINGS
115
+	select MTD_CFI_BE_BYTE_SWAP if CPU_BIG_ENDIAN
116
+	default ARCH_IXP4XX
117
+	help
118
+	  This provides some extra DT physmap parsing for the Intel IXP4xx
119
+	  platforms, some elaborate endianness handling in particular.
120
+
121
+config MTD_PHYSMAP_GPIO_ADDR
122
+	bool "GPIO-assisted Flash Chip Support"
123
+	depends on MTD_PHYSMAP
124
+	depends on GPIOLIB || COMPILE_TEST
125
+	depends on MTD_COMPLEX_MAPPINGS
126
+	help
127
+	  Extend the physmap driver to allow flashes to be partially
128
+	  physically addressed and assisted by GPIOs.
96
129
 
97
130
 config MTD_PMC_MSP_EVM
98
131
 	tristate "CFI Flash device mapped on PMC-Sierra MSP"
..
..
@@ -288,11 +321,11 @@
288
321
 	help
289
322
 	  This provides a driver for the flash accessed using Intel's
290
323
 	  21285 bridge used with Intel's StrongARM processors. More info at
291
-	  <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
324
+	  <https://www.intel.com/design/bridge/docs/21285_documentation.htm>.
292
325
 
293
326
 config MTD_IXP4XX
294
327
 	tristate "CFI Flash device mapped on Intel IXP4xx based systems"
295
-	depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
328
+	depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX && MTD_CFI_ADV_OPTIONS
296
329
 	help
297
330
 	  This enables MTD access to flash devices on platforms based
298
331
 	  on Intel's IXP4xx family of network processors such as the
..
..
@@ -333,16 +366,6 @@
333
366
 	  anything about themselves are assumed to be MTD cards.
334
367
 
335
368
 	  If unsure, say N.
336
-
337
-config MTD_GPIO_ADDR
338
-	tristate "GPIO-assisted Flash Chip Support"
339
-	depends on GPIOLIB || COMPILE_TEST
340
-	depends on MTD_COMPLEX_MAPPINGS
341
-	help
342
-	  Map driver which allows flashes to be partially physically addressed
343
-	  and assisted by GPIOs.
344
-
345
-	  If compiled as a module, it will be called gpio-addr-flash.
346
369
 
347
370
 config MTD_UCLINUX
348
371
 	bool "Generic uClinux RAM/ROM filesystem support"
..
..
@@ -399,14 +422,5 @@
399
422
 	  and/or MTD_PLATRAM according to the devices on your module.
400
423
 
401
424
 	  When built as a module, it will be called pismo.ko
402
-
403
-config MTD_LATCH_ADDR
404
-	tristate "Latch-assisted Flash Chip Support"
405
-	depends on MTD_COMPLEX_MAPPINGS
406
-	help
407
-	  Map driver which allows flashes to be partially physically addressed
408
-	  and have the upper address lines set by a board specific code.
409
-
410
-	  If compiled as a module, it will be called latch-addr-flash.
411
425
 
412
426
 endmenu