2014-04-23 23:46:17 +00:00
|
|
|
menu "SOC (System On Chip) specific Drivers"
|
|
|
|
|
|
2017-02-26 03:09:57 +00:00
|
|
|
source "drivers/soc/actions/Kconfig"
|
2017-06-23 08:28:18 +00:00
|
|
|
source "drivers/soc/amlogic/Kconfig"
|
2017-02-16 10:31:06 +00:00
|
|
|
source "drivers/soc/atmel/Kconfig"
|
2015-12-17 00:26:47 +00:00
|
|
|
source "drivers/soc/bcm/Kconfig"
|
2016-11-09 03:14:08 +00:00
|
|
|
source "drivers/soc/fsl/Kconfig"
|
2017-03-28 15:19:45 +00:00
|
|
|
source "drivers/soc/imx/Kconfig"
|
2015-03-17 10:14:34 +00:00
|
|
|
source "drivers/soc/mediatek/Kconfig"
|
2014-04-24 16:31:21 +00:00
|
|
|
source "drivers/soc/qcom/Kconfig"
|
soc: renesas: Rework Kconfig and Makefile logic
The goals are to:
- Allow precise control over and automatic selection of which
(sub)drivers are used for which SoC,
- Allow adding support for new SoCs easily,
- Allow compile-testing of all (sub)drivers,
- Keep driver selection logic in the subsystem-specific Kconfig,
independent from the architecture-specific Kconfig (i.e. no "select"
from arch/arm64/Kconfig.platforms), to avoid dependencies.
This is implemented by:
- Introducing Kconfig symbols for all drivers and sub-drivers,
- Introducing the Kconfig symbol SOC_RENESAS, which is enabled
automatically when building for a Renesas ARM platform, and which
enables all required drivers without interaction of the user, based
on SoC-specific ARCH_* symbols,
- Allowing the user to enable any Kconfig symbol manually if
COMPILE_TEST is enabled,
- Using the new Kconfig symbols instead of the ARCH_* symbols to
control compilation in the Makefile,
- Always entering drivers/soc/renesas/ during the build.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
2017-05-19 08:35:10 +00:00
|
|
|
source "drivers/soc/renesas/Kconfig"
|
2015-09-08 06:18:22 +00:00
|
|
|
source "drivers/soc/rockchip/Kconfig"
|
2015-12-18 03:32:16 +00:00
|
|
|
source "drivers/soc/samsung/Kconfig"
|
2015-06-01 09:04:26 +00:00
|
|
|
source "drivers/soc/sunxi/Kconfig"
|
2015-09-09 13:29:22 +00:00
|
|
|
source "drivers/soc/tegra/Kconfig"
|
2014-02-28 15:47:50 +00:00
|
|
|
source "drivers/soc/ti/Kconfig"
|
ARM: ux500: move soc_id driver to drivers/soc
As the ux500 id code is basically a standalone driver, we can move it
out of the arch code into drivers/soc/ux500.
This is a user-visible change, as it moves all the devices in sysfs
from /sys/devices/soc0/ to /sys/devices/ and leaves the soc0 node as a
separate device.
Originally the idea was to put all on-chip devices under the soc node,
and ux500 was the first platform to have this device, but later platforms
almost all didn't follow that pattern, so this makes the platform do
the same thing as everyone else.
Since the platform is really obsolete now, I am optimistic that nothing
will break after moving the devices around.
As the SoC driver no longer has access to the private header files,
I'm changing the code to instead look up the address of the backupram
from devicetree, which is a good idea anyway.
Finally, having a separate Kconfig symbol means the driver is now
optional and could even be a loadable module rather than always being
built-in if we allowed that for soc_device.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
[Fixup mising Makefile, fixup BB_UID_BASE to fc0]
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
2016-06-22 14:32:36 +00:00
|
|
|
source "drivers/soc/ux500/Kconfig"
|
2014-07-25 13:04:52 +00:00
|
|
|
source "drivers/soc/versatile/Kconfig"
|
2017-12-19 13:15:25 +00:00
|
|
|
source "drivers/soc/xilinx/Kconfig"
|
2017-01-06 09:16:03 +00:00
|
|
|
source "drivers/soc/zte/Kconfig"
|
2014-04-24 16:31:21 +00:00
|
|
|
|
2014-04-23 23:46:17 +00:00
|
|
|
endmenu
|
