2019-05-19 12:07:45 +00:00
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
2005-04-16 22:20:36 +00:00
|
|
|
if ARCH_IXP4XX
|
|
|
|
|
|
|
|
menu "Intel IXP4xx Implementation Options"
|
|
|
|
|
|
|
|
comment "IXP4xx Platforms"
|
|
|
|
|
2019-01-27 13:08:36 +00:00
|
|
|
config MACH_IXP4XX_OF
|
|
|
|
bool
|
2020-12-07 15:51:06 +00:00
|
|
|
prompt "Device Tree IXP4xx boards"
|
2019-01-27 13:08:36 +00:00
|
|
|
default y
|
|
|
|
select ARM_APPENDED_DTB # Old Redboot bootloaders deployed
|
|
|
|
select I2C
|
|
|
|
select I2C_IOP3XX
|
|
|
|
select PCI
|
|
|
|
select USE_OF
|
|
|
|
help
|
|
|
|
Say 'Y' here to support Device Tree-based IXP4xx platforms.
|
|
|
|
|
2007-06-02 14:44:08 +00:00
|
|
|
config MACH_GATEWAY7001
|
|
|
|
bool "Gateway 7001"
|
2021-04-29 21:34:10 +00:00
|
|
|
depends on IXP4XX_PCI_LEGACY
|
2007-06-02 14:44:08 +00:00
|
|
|
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
|
|
|
|
|
2009-05-23 21:58:30 +00:00
|
|
|
config MACH_GORAMO_MLR
|
|
|
|
bool "GORAMO Multi Link Router"
|
2021-07-21 15:16:04 +00:00
|
|
|
depends on IXP4XX_PCI_LEGACY
|
2009-05-23 21:58:30 +00:00
|
|
|
help
|
|
|
|
Say 'Y' here if you want your kernel to support GORAMO
|
|
|
|
MultiLink router.
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
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
|
2019-04-14 18:51:10 +00:00
|
|
|
this platform, see <file:Documentation/arm/ixp4xx.rst>.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
comment "IXP4xx Options"
|
|
|
|
|
2021-04-29 21:34:10 +00:00
|
|
|
config IXP4XX_PCI_LEGACY
|
|
|
|
bool "IXP4xx legacy PCI driver support"
|
|
|
|
depends on PCI
|
|
|
|
help
|
|
|
|
Selects legacy PCI driver.
|
|
|
|
Not recommended for new development.
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config IXP4XX_INDIRECT_PCI
|
|
|
|
bool "Use indirect PCI memory access"
|
2021-04-29 21:34:10 +00:00
|
|
|
depends on IXP4XX_PCI_LEGACY
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
IXP4xx provides two methods of accessing PCI memory space:
|
|
|
|
|
2009-11-15 17:02:10 +00:00
|
|
|
1) A direct mapped window from 0x48000000 to 0x4BFFFFFF (64MB).
|
2005-04-16 22:20:36 +00:00
|
|
|
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
|
2009-11-15 17:02:10 +00:00
|
|
|
limits the system to just 64MB of PCI memory. This can be
|
2006-11-30 04:22:59 +00:00
|
|
|
problematic if using video cards and other memory-heavy devices.
|
2009-11-15 17:02:10 +00:00
|
|
|
|
|
|
|
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.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
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
|