[linux-2.6-block.git] / arch / arm / mach-ixp4xx / Kconfig

# SPDX-License-Identifier: GPL-2.0-only
if ARCH_IXP4XX

menu "Intel IXP4xx Implementation Options"

comment "IXP4xx Platforms"

config MACH_IXP4XX_OF
	bool
	prompt "Devce Tree IXP4xx boards"
	default y
	select ARM_APPENDED_DTB # Old Redboot bootloaders deployed
	select I2C
	select I2C_IOP3XX
	select PCI
	select SERIAL_OF_PLATFORM
	select TIMER_OF
	select USE_OF
	help
	  Say 'Y' here to support Device Tree-based IXP4xx platforms.

config MACH_NSLU2
	bool
	prompt "Linksys NSLU2"
	select FORCE_PCI
	help
	  Say 'Y' here if you want your kernel to support Linksys's
	  NSLU2 NAS device. For more information on this platform,
	  see http://www.nslu2-linux.org

config MACH_AVILA
	bool "Avila"
	select FORCE_PCI
	help
	  Say 'Y' here if you want your kernel to support the Gateworks
	  Avila Network Platform. For more information on this platform,
	  see <file:Documentation/arm/IXP4xx>.

config MACH_LOFT
    bool "Loft"
    depends on MACH_AVILA
    help
	  Say 'Y' here if you want your kernel to support the Giant
	  Shoulder Inc Loft board (a minor variation on the standard
	  Gateworks Avila Network Platform).

config ARCH_ADI_COYOTE
	bool "Coyote"
	select FORCE_PCI
	help
	  Say 'Y' here if you want your kernel to support the ADI 
	  Engineering Coyote Gateway Reference Platform. For more
	  information on this platform, see <file:Documentation/arm/IXP4xx>.

config MACH_GATEWAY7001
	bool "Gateway 7001"
	select FORCE_PCI
	help
	  Say 'Y' here if you want your kernel to support Gateway's
	  7001 Access Point. For more information on this platform,
	  see http://openwrt.org

config MACH_WG302V2
	bool "Netgear WG302 v2 / WAG302 v2"
	select FORCE_PCI
	help
	  Say 'Y' here if you want your kernel to support Netgear's
	  WG302 v2 or WAG302 v2 Access Points. For more information
	  on this platform, see http://openwrt.org

config ARCH_IXDP425
	bool "IXDP425"
	help
	  Say 'Y' here if you want your kernel to support Intel's 
	  IXDP425 Development Platform (Also known as Richfield).  
	  For more information on this platform, see <file:Documentation/arm/IXP4xx>.

config MACH_IXDPG425
	bool "IXDPG425"
	help
	  Say 'Y' here if you want your kernel to support Intel's
	  IXDPG425 Development Platform (Also known as Montajade).
	  For more information on this platform, see <file:Documentation/arm/IXP4xx>.

config MACH_IXDP465
	bool "IXDP465"
	help
	  Say 'Y' here if you want your kernel to support Intel's
	  IXDP465 Development Platform (Also known as BMP).
	  For more information on this platform, see <file:Documentation/arm/IXP4xx>.

config MACH_GORAMO_MLR
	bool "GORAMO Multi Link Router"
	help
	  Say 'Y' here if you want your kernel to support GORAMO
	  MultiLink router.

config MACH_KIXRP435
	bool "KIXRP435"
	help
	  Say 'Y' here if you want your kernel to support Intel's
	  KIXRP435 Reference Platform.
	  For more information on this platform, see <file:Documentation/arm/IXP4xx>.

#
# IXCDP1100 is the exact same HW as IXDP425, but with a different machine 
# number from the bootloader due to marketing monkeys, so we just enable it 
# by default if IXDP425 is enabled.
#
config ARCH_IXCDP1100
	bool 
	depends on ARCH_IXDP425
	default y

config ARCH_PRPMC1100
	bool "PrPMC1100"
	help
	  Say 'Y' here if you want your kernel to support the Motorola
	  PrPCM1100 Processor Mezanine Module. For more information on
	  this platform, see <file:Documentation/arm/IXP4xx>.

config MACH_NAS100D
	bool
	prompt "NAS100D"
	select FORCE_PCI
	help
	  Say 'Y' here if you want your kernel to support Iomega's
	  NAS 100d device. For more information on this platform,
	  see http://www.nslu2-linux.org/wiki/NAS100d/HomePage

config MACH_DSMG600
	bool
	prompt "D-Link DSM-G600 RevA"
	select FORCE_PCI
	help
	  Say 'Y' here if you want your kernel to support D-Link's
	  DSM-G600 RevA device. For more information on this platform,
	  see http://www.nslu2-linux.org/wiki/DSMG600/HomePage

config	ARCH_IXDP4XX
	bool
	depends on ARCH_IXDP425 || MACH_IXDP465 || MACH_KIXRP435
	default y

config MACH_FSG
	bool
	prompt "Freecom FSG-3"
	select FORCE_PCI
	help
	  Say 'Y' here if you want your kernel to support Freecom's
	  FSG-3 device. For more information on this platform,
	  see http://www.nslu2-linux.org/wiki/FSG3/HomePage

config MACH_ARCOM_VULCAN
	bool
	prompt "Arcom/Eurotech Vulcan"
	select FORCE_PCI
	help
	  Say 'Y' here if you want your kernel to support Arcom's
	  Vulcan board.

#
# Certain registers and IRQs are only enabled if supporting IXP465 CPUs
#
config CPU_IXP46X
	bool
	depends on MACH_IXDP465
	default y

config CPU_IXP43X
	bool
	depends on MACH_KIXRP435
	default y

config MACH_GTWX5715
	bool "Gemtek WX5715 (Linksys WRV54G)"
	depends on ARCH_IXP4XX
	select FORCE_PCI
	help
		This board is currently inside the Linksys WRV54G Gateways.

		IXP425 - 266mhz
		32mb SDRAM
		8mb Flash
		miniPCI slot 0 does not have a card connector soldered to the board
		miniPCI slot 1 has an ISL3880 802.11g card (Prism54)
		npe0 is connected to a Kendin KS8995M Switch (4 ports)
		npe1 is the "wan" port
		"Console" UART is available on J11 as console
		"High Speed" UART is n/c (as far as I can tell)
		20 Pin ARM/Xscale JTAG interface on J2

config MACH_DEVIXP
	bool "Omicron DEVIXP"
	help
	  Say 'Y' here if you want your kernel to support the DEVIXP
	  board from OMICRON electronics GmbH.

config MACH_MICCPT
	bool "Omicron MICCPT"
	select FORCE_PCI
	help
	  Say 'Y' here if you want your kernel to support the MICCPT
	  board from OMICRON electronics GmbH.

config MACH_MIC256
	bool "Omicron MIC256"
	help
	  Say 'Y' here if you want your kernel to support the MIC256
	  board from OMICRON electronics GmbH.

comment "IXP4xx Options"

config IXP4XX_INDIRECT_PCI
	bool "Use indirect PCI memory access"
	depends on PCI
	help
          IXP4xx provides two methods of accessing PCI memory space:

          1) A direct mapped window from 0x48000000 to 0x4BFFFFFF (64MB).
             To access PCI via this space, we simply ioremap() the BAR
             into the kernel and we can use the standard read[bwl]/write[bwl]
             macros. This is the preferred method due to speed but it
             limits the system to just 64MB of PCI memory. This can be
             problematic if using video cards and other memory-heavy devices.

	  2) If > 64MB of memory space is required, the IXP4xx can be
	     configured to use indirect registers to access the whole PCI
	     memory space. This currently allows for up to 1 GB (0x10000000
	     to 0x4FFFFFFF) of memory on the bus. The disadvantage of this
	     is that every PCI access requires three local register accesses
	     plus a spinlock, but in some cases the performance hit is
	     acceptable. In addition, you cannot mmap() PCI devices in this
	     case due to the indirect nature of the PCI window.

	  By default, the direct method is used. Choose this option if you
	  need to use the indirect method instead. If you don't know
	  what you need, leave this option unselected.

endmenu

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