2012-08-22 15:40:02 +07:00
|
|
|
#
|
|
|
|
|
# Bus Devices
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
menu "Bus devices"
|
|
|
|
|
|
2013-05-28 13:20:07 +07:00
|
|
|
config IMX_WEIM
|
|
|
|
|
bool "Freescale EIM DRIVER"
|
|
|
|
|
depends on ARCH_MXC
|
|
|
|
|
help
|
2013-06-29 11:27:54 +07:00
|
|
|
Driver for i.MX WEIM controller.
|
2013-05-28 13:20:07 +07:00
|
|
|
The WEIM(Wireless External Interface Module) works like a bus.
|
|
|
|
|
You can attach many different devices on it, such as NOR, onenand.
|
|
|
|
|
|
bus: introduce an Marvell EBU MBus driver
The Marvell EBU SoCs have a configurable physical address space
layout: the physical ranges of memory used to address PCI(e)
interfaces, NOR flashes, SRAM and various other types of memory are
configurable by software, through a mechanism of so-called 'address
decoding windows'.
This new driver mvebu-mbus consolidates the existing code to address
the configuration of these memory ranges, which is spread into
mach-mvebu, mach-orion5x, mach-mv78xx0, mach-dove and mach-kirkwood.
Following patches convert each Marvell EBU SoC family to use this
driver, therefore removing the old code that was configuring the
address decoding windows.
It is worth mentioning that the MVEBU_MBUS Kconfig option is
intentionally added as a blind option. The new driver implements and
exports the mv_mbus_dram_info() function, which is used by various
Marvell drivers throughout the tree to get access to window
configuration parameters that they require. This function is also
implemented in arch/arm/plat-orion/addr-map.c, which ultimately gets
removed at the end of this patch series. So, in order to preserve
bisectability, we want to ensure that *either* this new driver, *or*
the legacy code in plat-orion/addr-map.c gets compiled in.
By making MVEBU_MBUS a blind option, we are sure that only a platform
that does 'select MVEBU_MBUS' will get this new driver compiled
in. Therefore, throughout the next patches that convert the Marvell
sub-architectures one after the other to this new driver, we add the
'select MVEBU_MBUS' and also ensure to remove plat-orion/addr-map.c
from the build for this specific sub-architecture. This ensures that
bisectability is preserved.
Ealier versions of this driver had a DT binding, but since those were
not yet agreed upon, they were removed. The driver still uses
of_device_id to find the SoC specific details according to the string
passed to mvebu_mbus_init(). The plan is to re-introduce a proper DT
binding as a followup set of patches.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Jason Cooper <jason@lakedaemon.net>
2013-03-21 23:59:14 +07:00
|
|
|
config MVEBU_MBUS
|
|
|
|
|
bool
|
|
|
|
|
depends on PLAT_ORION
|
|
|
|
|
help
|
|
|
|
|
Driver needed for the MBus configuration on Marvell EBU SoCs
|
|
|
|
|
(Kirkwood, Dove, Orion5x, MV78XX0 and Armada 370/XP).
|
|
|
|
|
|
2012-08-22 15:40:02 +07:00
|
|
|
config OMAP_OCP2SCP
|
|
|
|
|
tristate "OMAP OCP2SCP DRIVER"
|
2012-12-17 03:28:46 +07:00
|
|
|
depends on ARCH_OMAP2PLUS
|
2012-08-22 15:40:02 +07:00
|
|
|
help
|
|
|
|
|
Driver to enable ocp2scp module which transforms ocp interface
|
|
|
|
|
protocol to scp protocol. In OMAP4, USB PHY is connected via
|
|
|
|
|
OCP2SCP and in OMAP5, both USB PHY and SATA PHY is connected via
|
|
|
|
|
OCP2SCP.
|
|
|
|
|
|
2012-09-14 16:20:34 +07:00
|
|
|
config OMAP_INTERCONNECT
|
|
|
|
|
tristate "OMAP INTERCONNECT DRIVER"
|
|
|
|
|
depends on ARCH_OMAP2PLUS
|
|
|
|
|
|
|
|
|
|
help
|
|
|
|
|
Driver to enable OMAP interconnect error handling driver.
|
2012-07-13 21:55:52 +07:00
|
|
|
|
|
|
|
|
config ARM_CCI
|
|
|
|
|
bool "ARM CCI driver support"
|
|
|
|
|
depends on ARM
|
|
|
|
|
help
|
|
|
|
|
Driver supporting the CCI cache coherent interconnect for ARM
|
|
|
|
|
platforms.
|
2012-08-22 15:40:02 +07:00
|
|
|
endmenu
|