xref: /openbmc/linux/arch/arm/mach-ixp4xx/Kconfig (revision ee2f116b) 
1# SPDX-License-Identifier: GPL-2.0-only
2if ARCH_IXP4XX
3
4menu "Intel IXP4xx Implementation Options"
5
6comment "IXP4xx Platforms"
7
8config MACH_IXP4XX_OF
9	bool
10	prompt "Device Tree IXP4xx boards"
11	default y
12	select ARM_APPENDED_DTB # Old Redboot bootloaders deployed
13	select I2C
14	select I2C_IOP3XX
15	select PCI
16	select USE_OF
17	help
18	  Say 'Y' here to support Device Tree-based IXP4xx platforms.
19
20config MACH_AVILA
21	bool "Avila"
22	depends on IXP4XX_PCI_LEGACY
23	help
24	  Say 'Y' here if you want your kernel to support the Gateworks
25	  Avila Network Platform. For more information on this platform,
26	  see <file:Documentation/arm/ixp4xx.rst>.
27
28config MACH_LOFT
29    bool "Loft"
30    depends on MACH_AVILA
31    help
32	  Say 'Y' here if you want your kernel to support the Giant
33	  Shoulder Inc Loft board (a minor variation on the standard
34	  Gateworks Avila Network Platform).
35
36config ARCH_ADI_COYOTE
37	bool "Coyote"
38	depends on IXP4XX_PCI_LEGACY
39	help
40	  Say 'Y' here if you want your kernel to support the ADI
41	  Engineering Coyote Gateway Reference Platform. For more
42	  information on this platform, see <file:Documentation/arm/ixp4xx.rst>.
43
44config MACH_GATEWAY7001
45	bool "Gateway 7001"
46	depends on IXP4XX_PCI_LEGACY
47	help
48	  Say 'Y' here if you want your kernel to support Gateway's
49	  7001 Access Point. For more information on this platform,
50	  see http://openwrt.org
51
52config MACH_WG302V2
53	bool "Netgear WG302 v2 / WAG302 v2"
54	depends on IXP4XX_PCI_LEGACY
55	help
56	  Say 'Y' here if you want your kernel to support Netgear's
57	  WG302 v2 or WAG302 v2 Access Points. For more information
58	  on this platform, see http://openwrt.org
59
60config ARCH_IXDP425
61	bool "IXDP425"
62	depends on IXP4XX_PCI_LEGACY
63	help
64	  Say 'Y' here if you want your kernel to support Intel's
65	  IXDP425 Development Platform (Also known as Richfield).
66	  For more information on this platform, see <file:Documentation/arm/ixp4xx.rst>.
67
68config MACH_IXDPG425
69	bool "IXDPG425"
70	depends on IXP4XX_PCI_LEGACY
71	help
72	  Say 'Y' here if you want your kernel to support Intel's
73	  IXDPG425 Development Platform (Also known as Montajade).
74	  For more information on this platform, see <file:Documentation/arm/ixp4xx.rst>.
75
76config MACH_IXDP465
77	bool "IXDP465"
78	help
79	  Say 'Y' here if you want your kernel to support Intel's
80	  IXDP465 Development Platform (Also known as BMP).
81	  For more information on this platform, see <file:Documentation/arm/ixp4xx.rst>.
82
83config MACH_GORAMO_MLR
84	bool "GORAMO Multi Link Router"
85	help
86	  Say 'Y' here if you want your kernel to support GORAMO
87	  MultiLink router.
88
89config MACH_KIXRP435
90	bool "KIXRP435"
91	help
92	  Say 'Y' here if you want your kernel to support Intel's
93	  KIXRP435 Reference Platform.
94	  For more information on this platform, see <file:Documentation/arm/ixp4xx.rst>.
95
96#
97# IXCDP1100 is the exact same HW as IXDP425, but with a different machine
98# number from the bootloader due to marketing monkeys, so we just enable it
99# by default if IXDP425 is enabled.
100#
101config ARCH_IXCDP1100
102	bool
103	depends on ARCH_IXDP425
104	default y
105
106config ARCH_PRPMC1100
107	bool "PrPMC1100"
108	help
109	  Say 'Y' here if you want your kernel to support the Motorola
110	  PrPCM1100 Processor Mezanine Module. For more information on
111	  this platform, see <file:Documentation/arm/ixp4xx.rst>.
112
113config MACH_DSMG600
114	bool
115	prompt "D-Link DSM-G600 RevA"
116	depends on IXP4XX_PCI_LEGACY
117	help
118	  Say 'Y' here if you want your kernel to support D-Link's
119	  DSM-G600 RevA device. For more information on this platform,
120	  see http://www.nslu2-linux.org/wiki/DSMG600/HomePage
121
122config	ARCH_IXDP4XX
123	bool
124	depends on ARCH_IXDP425 || MACH_IXDP465 || MACH_KIXRP435
125	default y
126
127config MACH_FSG
128	bool
129	prompt "Freecom FSG-3"
130	depends on IXP4XX_PCI_LEGACY
131	help
132	  Say 'Y' here if you want your kernel to support Freecom's
133	  FSG-3 device. For more information on this platform,
134	  see http://www.nslu2-linux.org/wiki/FSG3/HomePage
135
136config MACH_ARCOM_VULCAN
137	bool
138	prompt "Arcom/Eurotech Vulcan"
139	depends on IXP4XX_PCI_LEGACY
140	help
141	  Say 'Y' here if you want your kernel to support Arcom's
142	  Vulcan board.
143
144#
145# Certain registers and IRQs are only enabled if supporting IXP465 CPUs
146#
147config CPU_IXP46X
148	bool
149	depends on MACH_IXDP465
150	default y
151
152config CPU_IXP43X
153	bool
154	depends on MACH_KIXRP435
155	default y
156
157config MACH_GTWX5715
158	bool "Gemtek WX5715 (Linksys WRV54G)"
159	depends on ARCH_IXP4XX
160	depends on IXP4XX_PCI_LEGACY
161	help
162		This board is currently inside the Linksys WRV54G Gateways.
163
164		IXP425 - 266mhz
165		32mb SDRAM
166		8mb Flash
167		miniPCI slot 0 does not have a card connector soldered to the board
168		miniPCI slot 1 has an ISL3880 802.11g card (Prism54)
169		npe0 is connected to a Kendin KS8995M Switch (4 ports)
170		npe1 is the "wan" port
171		"Console" UART is available on J11 as console
172		"High Speed" UART is n/c (as far as I can tell)
173		20 Pin ARM/Xscale JTAG interface on J2
174
175config MACH_DEVIXP
176	bool "Omicron DEVIXP"
177	help
178	  Say 'Y' here if you want your kernel to support the DEVIXP
179	  board from OMICRON electronics GmbH.
180
181config MACH_MICCPT
182	bool "Omicron MICCPT"
183	depends on IXP4XX_PCI_LEGACY
184	help
185	  Say 'Y' here if you want your kernel to support the MICCPT
186	  board from OMICRON electronics GmbH.
187
188config MACH_MIC256
189	bool "Omicron MIC256"
190	help
191	  Say 'Y' here if you want your kernel to support the MIC256
192	  board from OMICRON electronics GmbH.
193
194comment "IXP4xx Options"
195
196config IXP4XX_PCI_LEGACY
197	bool "IXP4xx legacy PCI driver support"
198	depends on PCI
199	help
200	  Selects legacy PCI driver.
201	  Not recommended for new development.
202
203config IXP4XX_INDIRECT_PCI
204	bool "Use indirect PCI memory access"
205	depends on IXP4XX_PCI_LEGACY
206	help
207          IXP4xx provides two methods of accessing PCI memory space:
208
209          1) A direct mapped window from 0x48000000 to 0x4BFFFFFF (64MB).
210             To access PCI via this space, we simply ioremap() the BAR
211             into the kernel and we can use the standard read[bwl]/write[bwl]
212             macros. This is the preferred method due to speed but it
213             limits the system to just 64MB of PCI memory. This can be
214             problematic if using video cards and other memory-heavy devices.
215
216	  2) If > 64MB of memory space is required, the IXP4xx can be
217	     configured to use indirect registers to access the whole PCI
218	     memory space. This currently allows for up to 1 GB (0x10000000
219	     to 0x4FFFFFFF) of memory on the bus. The disadvantage of this
220	     is that every PCI access requires three local register accesses
221	     plus a spinlock, but in some cases the performance hit is
222	     acceptable. In addition, you cannot mmap() PCI devices in this
223	     case due to the indirect nature of the PCI window.
224
225	  By default, the direct method is used. Choose this option if you
226	  need to use the indirect method instead. If you don't know
227	  what you need, leave this option unselected.
228
229endmenu
230
231endif
232