2012-08-22 15:40:02 +07:00
|
|
|
#
|
|
|
|
|
# Bus Devices
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
menu "Bus devices"
|
|
|
|
|
|
2015-02-05 17:11:24 +07:00
|
|
|
config ARM_CCI
|
2015-04-04 03:38:43 +07:00
|
|
|
bool
|
|
|
|
|
|
2015-05-26 16:53:14 +07:00
|
|
|
config ARM_CCI_PMU
|
|
|
|
|
bool
|
|
|
|
|
select ARM_CCI
|
|
|
|
|
|
2015-04-04 03:38:43 +07:00
|
|
|
config ARM_CCI400_COMMON
|
|
|
|
|
bool
|
|
|
|
|
select ARM_CCI
|
|
|
|
|
|
|
|
|
|
config ARM_CCI400_PMU
|
|
|
|
|
bool "ARM CCI400 PMU support"
|
2015-05-26 16:53:10 +07:00
|
|
|
depends on (ARM && CPU_V7) || ARM64
|
|
|
|
|
depends on PERF_EVENTS
|
2015-04-04 03:38:43 +07:00
|
|
|
select ARM_CCI400_COMMON
|
2015-05-26 16:53:14 +07:00
|
|
|
select ARM_CCI_PMU
|
2015-04-04 03:38:43 +07:00
|
|
|
help
|
2015-05-26 16:53:10 +07:00
|
|
|
Support for PMU events monitoring on the ARM CCI-400 (cache coherent
|
|
|
|
|
interconnect). CCI-400 supports counting events related to the
|
|
|
|
|
connected slave/master interfaces.
|
2015-04-04 03:38:43 +07:00
|
|
|
|
|
|
|
|
config ARM_CCI400_PORT_CTRL
|
|
|
|
|
bool
|
2015-02-05 17:11:24 +07:00
|
|
|
depends on ARM && OF && CPU_V7
|
2015-04-04 03:38:43 +07:00
|
|
|
select ARM_CCI400_COMMON
|
2015-02-05 17:11:24 +07:00
|
|
|
help
|
2015-04-04 03:38:43 +07:00
|
|
|
Low level power management driver for CCI400 cache coherent
|
|
|
|
|
interconnect for ARM platforms.
|
2015-02-05 17:11:24 +07:00
|
|
|
|
2015-05-26 16:53:15 +07:00
|
|
|
config ARM_CCI500_PMU
|
|
|
|
|
bool "ARM CCI500 PMU support"
|
|
|
|
|
depends on (ARM && CPU_V7) || ARM64
|
|
|
|
|
depends on PERF_EVENTS
|
|
|
|
|
select ARM_CCI_PMU
|
|
|
|
|
help
|
|
|
|
|
Support for PMU events monitoring on the ARM CCI-500 cache coherent
|
|
|
|
|
interconnect. CCI-500 provides 8 independent event counters, which
|
|
|
|
|
can count events pertaining to the slave/master interfaces as well
|
|
|
|
|
as the internal events to the CCI.
|
|
|
|
|
|
|
|
|
|
If unsure, say Y
|
|
|
|
|
|
2015-02-05 17:11:24 +07:00
|
|
|
config ARM_CCN
|
|
|
|
|
bool "ARM CCN driver support"
|
|
|
|
|
depends on ARM || ARM64
|
|
|
|
|
depends on PERF_EVENTS
|
|
|
|
|
help
|
|
|
|
|
PMU (perf) driver supporting the ARM CCN (Cache Coherent Network)
|
|
|
|
|
interconnect.
|
|
|
|
|
|
2014-05-20 03:05:59 +07:00
|
|
|
config BRCMSTB_GISB_ARB
|
|
|
|
|
bool "Broadcom STB GISB bus arbiter"
|
2014-11-26 07:49:49 +07:00
|
|
|
depends on ARM || MIPS
|
2014-05-20 03:05:59 +07:00
|
|
|
help
|
|
|
|
|
Driver for the Broadcom Set Top Box System-on-a-chip internal bus
|
|
|
|
|
arbiter. This driver provides timeout and target abort error handling
|
|
|
|
|
and internal bus master decoding.
|
|
|
|
|
|
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.
|
|
|
|
|
|
2015-03-25 22:39:50 +07:00
|
|
|
config MIPS_CDMM
|
|
|
|
|
bool "MIPS Common Device Memory Map (CDMM) Driver"
|
|
|
|
|
depends on CPU_MIPSR2
|
|
|
|
|
help
|
|
|
|
|
Driver needed for the MIPS Common Device Memory Map bus in MIPS
|
|
|
|
|
cores. This bus is for per-CPU tightly coupled devices such as the
|
|
|
|
|
Fast Debug Channel (FDC).
|
|
|
|
|
|
|
|
|
|
For this to work, either your bootloader needs to enable the CDMM
|
|
|
|
|
region at an unused physical address on the boot CPU, or else your
|
|
|
|
|
platform code needs to implement mips_cdmm_phys_base() (see
|
|
|
|
|
asm/cdmm.h).
|
|
|
|
|
|
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-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
|
|
|
|
2015-02-05 17:11:24 +07:00
|
|
|
config OMAP_OCP2SCP
|
|
|
|
|
tristate "OMAP OCP2SCP DRIVER"
|
|
|
|
|
depends on ARCH_OMAP2PLUS
|
2012-07-13 21:55:52 +07:00
|
|
|
help
|
2015-02-05 17:11:24 +07:00
|
|
|
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.
|
mfd: vexpress: Convert custom func API to regmap
Components of the Versatile Express platform (configuration
microcontrollers on motherboard and daughterboards in particular)
talk to each other over a custom configuration bus. They
provide miscellaneous functions (from clock generator control
to energy sensors) which are represented as platform devices
(and Device Tree nodes). The transactions on the bus can
be generated by different "bridges" in the system, some
of which are universal for the whole platform (for the price
of high transfer latencies), others restricted to a subsystem
(but much faster).
Until now drivers for such functions were using custom "func"
API, which is being replaced in this patch by regmap calls.
This required:
* a rework (and move to drivers/bus directory, as suggested
by Samuel and Arnd) of the config bus core, which is much
simpler now and uses device model infrastructure (class)
to keep track of the bridges; non-DT case (soon to be
retired anyway) is simply covered by a special device
registration function
* the new config-bus driver also takes over device population,
so there is no need for special matching table for
of_platform_populate nor "simple-bus" hack in the arm64
model dtsi file (relevant bindings documentation has
been updated); this allows all the vexpress devices
fit into normal device model, making it possible
to remove plenty of early inits and other hacks in
the near future
* adaptation of the syscfg bridge implementation in the
sysreg driver, again making it much simpler; there is
a special case of the "energy" function spanning two
registers, where they should be both defined in the tree
now, but backward compatibility is maintained in the code
* modification of the relevant drivers:
* hwmon - just a straight-forward API change
* power/reset driver - API change
* regulator - API change plus error handling
simplification
* osc clock driver - this one required larger rework
in order to turn in into a standard platform driver
Signed-off-by: Pawel Moll <pawel.moll@arm.com>
Acked-by: Mark Brown <broonie@linaro.org>
Acked-by: Lee Jones <lee.jones@linaro.org>
Acked-by: Guenter Roeck <linux@roeck-us.net>
Acked-by: Mike Turquette <mturquette@linaro.org>
2014-04-30 22:46:29 +07:00
|
|
|
|
2015-02-05 17:11:28 +07:00
|
|
|
config SIMPLE_PM_BUS
|
|
|
|
|
bool "Simple Power-Managed Bus Driver"
|
|
|
|
|
depends on OF && PM
|
|
|
|
|
depends on ARCH_SHMOBILE || COMPILE_TEST
|
2014-07-23 00:32:59 +07:00
|
|
|
help
|
2015-02-05 17:11:28 +07:00
|
|
|
Driver for transparent busses that don't need a real driver, but
|
|
|
|
|
where the bus controller is part of a PM domain, or under the control
|
|
|
|
|
of a functional clock, and thus relies on runtime PM for managing
|
|
|
|
|
this PM domain and/or clock.
|
|
|
|
|
An example of such a bus controller is the Renesas Bus State
|
|
|
|
|
Controller (BSC, sometimes called "LBSC within Bus Bridge", or
|
|
|
|
|
"External Bus Interface") as found on several Renesas ARM SoCs.
|
2014-07-23 00:32:59 +07:00
|
|
|
|
2015-10-24 01:41:31 +07:00
|
|
|
config SUNXI_RSB
|
|
|
|
|
tristate "Allwinner sunXi Reduced Serial Bus Driver"
|
|
|
|
|
default MACH_SUN8I || MACH_SUN9I
|
|
|
|
|
depends on ARCH_SUNXI
|
|
|
|
|
select REGMAP
|
|
|
|
|
help
|
|
|
|
|
Say y here to enable support for Allwinner's Reduced Serial Bus
|
|
|
|
|
(RSB) support. This controller is responsible for communicating
|
|
|
|
|
with various RSB based devices, such as AXP223, AXP8XX PMICs,
|
|
|
|
|
and AC100/AC200 ICs.
|
|
|
|
|
|
2015-12-09 13:52:59 +07:00
|
|
|
config UNIPHIER_SYSTEM_BUS
|
2016-01-23 21:06:28 +07:00
|
|
|
tristate "UniPhier System Bus driver"
|
2015-12-09 13:52:59 +07:00
|
|
|
depends on ARCH_UNIPHIER && OF
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Support for UniPhier System Bus, a simple external bus. This is
|
|
|
|
|
needed to use on-board devices connected to UniPhier SoCs.
|
|
|
|
|
|
mfd: vexpress: Convert custom func API to regmap
Components of the Versatile Express platform (configuration
microcontrollers on motherboard and daughterboards in particular)
talk to each other over a custom configuration bus. They
provide miscellaneous functions (from clock generator control
to energy sensors) which are represented as platform devices
(and Device Tree nodes). The transactions on the bus can
be generated by different "bridges" in the system, some
of which are universal for the whole platform (for the price
of high transfer latencies), others restricted to a subsystem
(but much faster).
Until now drivers for such functions were using custom "func"
API, which is being replaced in this patch by regmap calls.
This required:
* a rework (and move to drivers/bus directory, as suggested
by Samuel and Arnd) of the config bus core, which is much
simpler now and uses device model infrastructure (class)
to keep track of the bridges; non-DT case (soon to be
retired anyway) is simply covered by a special device
registration function
* the new config-bus driver also takes over device population,
so there is no need for special matching table for
of_platform_populate nor "simple-bus" hack in the arm64
model dtsi file (relevant bindings documentation has
been updated); this allows all the vexpress devices
fit into normal device model, making it possible
to remove plenty of early inits and other hacks in
the near future
* adaptation of the syscfg bridge implementation in the
sysreg driver, again making it much simpler; there is
a special case of the "energy" function spanning two
registers, where they should be both defined in the tree
now, but backward compatibility is maintained in the code
* modification of the relevant drivers:
* hwmon - just a straight-forward API change
* power/reset driver - API change
* regulator - API change plus error handling
simplification
* osc clock driver - this one required larger rework
in order to turn in into a standard platform driver
Signed-off-by: Pawel Moll <pawel.moll@arm.com>
Acked-by: Mark Brown <broonie@linaro.org>
Acked-by: Lee Jones <lee.jones@linaro.org>
Acked-by: Guenter Roeck <linux@roeck-us.net>
Acked-by: Mike Turquette <mturquette@linaro.org>
2014-04-30 22:46:29 +07:00
|
|
|
config VEXPRESS_CONFIG
|
|
|
|
|
bool "Versatile Express configuration bus"
|
|
|
|
|
default y if ARCH_VEXPRESS
|
|
|
|
|
depends on ARM || ARM64
|
2014-05-26 22:25:22 +07:00
|
|
|
depends on OF
|
mfd: vexpress: Convert custom func API to regmap
Components of the Versatile Express platform (configuration
microcontrollers on motherboard and daughterboards in particular)
talk to each other over a custom configuration bus. They
provide miscellaneous functions (from clock generator control
to energy sensors) which are represented as platform devices
(and Device Tree nodes). The transactions on the bus can
be generated by different "bridges" in the system, some
of which are universal for the whole platform (for the price
of high transfer latencies), others restricted to a subsystem
(but much faster).
Until now drivers for such functions were using custom "func"
API, which is being replaced in this patch by regmap calls.
This required:
* a rework (and move to drivers/bus directory, as suggested
by Samuel and Arnd) of the config bus core, which is much
simpler now and uses device model infrastructure (class)
to keep track of the bridges; non-DT case (soon to be
retired anyway) is simply covered by a special device
registration function
* the new config-bus driver also takes over device population,
so there is no need for special matching table for
of_platform_populate nor "simple-bus" hack in the arm64
model dtsi file (relevant bindings documentation has
been updated); this allows all the vexpress devices
fit into normal device model, making it possible
to remove plenty of early inits and other hacks in
the near future
* adaptation of the syscfg bridge implementation in the
sysreg driver, again making it much simpler; there is
a special case of the "energy" function spanning two
registers, where they should be both defined in the tree
now, but backward compatibility is maintained in the code
* modification of the relevant drivers:
* hwmon - just a straight-forward API change
* power/reset driver - API change
* regulator - API change plus error handling
simplification
* osc clock driver - this one required larger rework
in order to turn in into a standard platform driver
Signed-off-by: Pawel Moll <pawel.moll@arm.com>
Acked-by: Mark Brown <broonie@linaro.org>
Acked-by: Lee Jones <lee.jones@linaro.org>
Acked-by: Guenter Roeck <linux@roeck-us.net>
Acked-by: Mike Turquette <mturquette@linaro.org>
2014-04-30 22:46:29 +07:00
|
|
|
select REGMAP
|
|
|
|
|
help
|
|
|
|
|
Platform configuration infrastructure for the ARM Ltd.
|
|
|
|
|
Versatile Express.
|
2012-08-22 15:40:02 +07:00
|
|
|
endmenu
|