mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-11-28 23:51:33 +00:00
ddf56bc7e3
Many System on Chip(SoC) solutions are complex with multiple processors on the same die dedicated to either general purpose of specialized functions. Many examples do exist in today's SoCs from various vendors. Typical examples are micro controllers such as an ARM M3/M0 doing a offload of specific function such as event integration or power management or controlling camera etc. Traditionally, the responsibility of loading up such a processor with a firmware and communication has been with a High Level Operating System(HLOS) such as Linux. However, there exists classes of products where Linux would need to expect services from such a processor or the delay of Linux and operating system being able to load up such a firmware is unacceptable. To address these needs, we need some minimal capability to load such a system and ensure it is started prior to an Operating System(Linux or any other) is started up. NOTE: This is NOT meant to be a solve-all solution, instead, it tries to address certain class of SoCs and products that need such a solution. A very simple model is introduced here as part of the initial support that supports microcontrollers with internal memory (no MMU, no execution from external memory, or specific image format needs). This basic framework can then (hopefully) be extensible to other complex SoC processor support as need be. Reviewed-by: Simon Glass <sjg@chromium.org> Signed-off-by: Nishanth Menon <nm@ti.com> Acked-by: Simon Glass <sjg@chromium.org>
77 lines
1.4 KiB
Text
77 lines
1.4 KiB
Text
menu "Device Drivers"
|
|
|
|
source "drivers/core/Kconfig"
|
|
|
|
# types of drivers sorted in alphabetical order
|
|
|
|
source "drivers/block/Kconfig"
|
|
|
|
source "drivers/clk/Kconfig"
|
|
|
|
source "drivers/cpu/Kconfig"
|
|
|
|
source "drivers/crypto/Kconfig"
|
|
|
|
source "drivers/demo/Kconfig"
|
|
|
|
source "drivers/dfu/Kconfig"
|
|
|
|
source "drivers/dma/Kconfig"
|
|
|
|
source "drivers/gpio/Kconfig"
|
|
|
|
source "drivers/hwmon/Kconfig"
|
|
|
|
source "drivers/i2c/Kconfig"
|
|
|
|
source "drivers/input/Kconfig"
|
|
|
|
source "drivers/led/Kconfig"
|
|
|
|
source "drivers/misc/Kconfig"
|
|
|
|
source "drivers/mmc/Kconfig"
|
|
|
|
source "drivers/mtd/Kconfig"
|
|
|
|
source "drivers/net/Kconfig"
|
|
|
|
source "drivers/pci/Kconfig"
|
|
|
|
source "drivers/pcmcia/Kconfig"
|
|
|
|
source "drivers/pinctrl/Kconfig"
|
|
|
|
source "drivers/power/Kconfig"
|
|
|
|
source "drivers/ram/Kconfig"
|
|
|
|
source "drivers/remoteproc/Kconfig"
|
|
|
|
source "drivers/rtc/Kconfig"
|
|
|
|
source "drivers/serial/Kconfig"
|
|
|
|
source "drivers/sound/Kconfig"
|
|
|
|
source "drivers/spi/Kconfig"
|
|
|
|
source "drivers/thermal/Kconfig"
|
|
|
|
source "drivers/tpm/Kconfig"
|
|
|
|
source "drivers/usb/Kconfig"
|
|
|
|
source "drivers/video/Kconfig"
|
|
|
|
source "drivers/watchdog/Kconfig"
|
|
|
|
config PHYS_TO_BUS
|
|
bool "Custom physical to bus address mapping"
|
|
help
|
|
Some SoCs use a different address map for CPU physical addresses and
|
|
peripheral DMA master accesses. If yours does, select this option in
|
|
your platform's Kconfig, and implement the appropriate mapping
|
|
functions in your platform's support code.
|
|
|
|
endmenu
|