Kconfig: drivers: restyle remaining
Restyle all Kconfigs for the rest of "drivers": Menu entries : no space left Menu attributes: 1 TAB Help text : 1 TAB + 2 spaces Replace '---help---' by 'help' Signed-off-by: Johan Jonker <jbx6244@gmail.com> [trini: Add missing indentation on a few more multi-paragraph help texts] Signed-off-by: Tom Rini <trini@konsulko.com>
This commit is contained in:
+1
-1
@@ -5,7 +5,7 @@ config ADC
|
||||
This enables ADC API for drivers, which allows driving ADC features
|
||||
by single and multi-channel methods for:
|
||||
- start/stop/get data for conversion of a single-channel selected by
|
||||
a number or multi-channels selected by a bitmask
|
||||
a number or multi-channels selected by a bitmask
|
||||
- get data mask (ADC resolution)
|
||||
ADC reference Voltage supply options:
|
||||
- methods for get Vdd/Vss reference Voltage values with polarity
|
||||
|
||||
@@ -68,10 +68,10 @@ config BLKMAP
|
||||
bool "Composable virtual block devices (blkmap)"
|
||||
depends on BLK
|
||||
help
|
||||
Create virtual block devices that are backed by various sources,
|
||||
e.g. RAM, or parts of an existing block device. Though much more
|
||||
rudimentary, it borrows a lot of ideas from Linux's device mapper
|
||||
subsystem.
|
||||
Create virtual block devices that are backed by various sources,
|
||||
e.g. RAM, or parts of an existing block device. Though much more
|
||||
rudimentary, it borrows a lot of ideas from Linux's device mapper
|
||||
subsystem.
|
||||
|
||||
Example use-cases:
|
||||
- Treat a region of RAM as a block device, i.e. a RAM disk. This let's
|
||||
|
||||
@@ -68,7 +68,7 @@ config BOOTCOUNT_ENV
|
||||
saveenv on all reboots, the environment variable
|
||||
"upgrade_available" is used. If "upgrade_available" is
|
||||
0, "bootcount" is always 0. If "upgrade_available" is 1,
|
||||
"bootcount" is incremented in the environment.
|
||||
"bootcount" is incremented in the environment.
|
||||
So the Userspace Application must set the "upgrade_available"
|
||||
and "bootcount" variables to 0, if the system booted successfully.
|
||||
|
||||
@@ -83,7 +83,7 @@ config BOOTCOUNT_AT91
|
||||
depends on AT91SAM9XE
|
||||
|
||||
config DM_BOOTCOUNT
|
||||
bool "Boot counter in a device-model device"
|
||||
bool "Boot counter in a device-model device"
|
||||
help
|
||||
Enables reading/writing the bootcount in a device-model based
|
||||
backing store. If an entry in /chosen/u-boot,bootcount-device
|
||||
|
||||
+2
-2
@@ -134,8 +134,8 @@ config CLK_CDCE9XX
|
||||
bool "Enable CDCD9XX clock driver"
|
||||
depends on CLK && ARCH_OMAP2PLUS
|
||||
help
|
||||
Enable the clock synthesizer driver for CDCE913/925/937/949
|
||||
series of chips.
|
||||
Enable the clock synthesizer driver for CDCE913/925/937/949
|
||||
series of chips.
|
||||
|
||||
config CLK_ICS8N3QV01
|
||||
bool "Enable ICS8N3QV01 VCXO driver"
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
config CLK_OWL
|
||||
bool "Actions Semi OWL clock drivers"
|
||||
depends on CLK && ARCH_OWL
|
||||
help
|
||||
Enable support for clock managemet unit present in Actions Semi
|
||||
bool "Actions Semi OWL clock drivers"
|
||||
depends on CLK && ARCH_OWL
|
||||
help
|
||||
Enable support for clock managemet unit present in Actions Semi
|
||||
Owl series S900/S700 SoCs.
|
||||
|
||||
|
||||
|
||||
@@ -61,11 +61,11 @@ config CLK_RCAR_GEN3
|
||||
Enable this to support the clocks on Renesas R-Car Gen3 and Gen4 SoCs.
|
||||
|
||||
config CLK_R8A774A1
|
||||
bool "Renesas R8A774A1 clock driver"
|
||||
bool "Renesas R8A774A1 clock driver"
|
||||
def_bool y if R8A774A1
|
||||
depends on CLK_RCAR_GEN3
|
||||
help
|
||||
Enable this to support the clocks on Renesas R8A774A1 SoC.
|
||||
depends on CLK_RCAR_GEN3
|
||||
help
|
||||
Enable this to support the clocks on Renesas R8A774A1 SoC.
|
||||
|
||||
config CLK_R8A774B1
|
||||
bool "Renesas R8A774B1 clock driver"
|
||||
|
||||
@@ -15,11 +15,11 @@ config ASPEED_ACRY
|
||||
bool "ASPEED RSA and ECC Engine"
|
||||
depends on ASPEED_AST2600
|
||||
help
|
||||
Select this option to enable a driver for using the RSA/ECC engine in
|
||||
the ASPEED BMC SoCs.
|
||||
Select this option to enable a driver for using the RSA/ECC engine in
|
||||
the ASPEED BMC SoCs.
|
||||
|
||||
Enabling this allows the use of RSA/ECC operations in hardware without requiring the
|
||||
software implementations. It also improves performance and saves code size.
|
||||
Enabling this allows the use of RSA/ECC operations in hardware without requiring the
|
||||
software implementations. It also improves performance and saves code size.
|
||||
|
||||
config ASPEED_CPTRA_SHA
|
||||
bool "Caliptra SHA ACC for Aspeed AST27xx SoCs"
|
||||
|
||||
@@ -27,27 +27,27 @@ config CAAM_64BIT
|
||||
config SYS_FSL_HAS_SEC
|
||||
bool
|
||||
help
|
||||
Enable Freescale Secure Boot and Trusted Architecture
|
||||
Enable Freescale Secure Boot and Trusted Architecture
|
||||
|
||||
config SYS_FSL_SEC_COMPAT_2
|
||||
bool
|
||||
help
|
||||
Secure boot and trust architecture compatible version 2
|
||||
Secure boot and trust architecture compatible version 2
|
||||
|
||||
config SYS_FSL_SEC_COMPAT_4
|
||||
bool
|
||||
help
|
||||
Secure boot and trust architecture compatible version 4
|
||||
Secure boot and trust architecture compatible version 4
|
||||
|
||||
config SYS_FSL_SEC_COMPAT_5
|
||||
bool
|
||||
help
|
||||
Secure boot and trust architecture compatible version 5
|
||||
Secure boot and trust architecture compatible version 5
|
||||
|
||||
config SYS_FSL_SEC_COMPAT_6
|
||||
bool
|
||||
help
|
||||
Secure boot and trust architecture compatible version 6
|
||||
Secure boot and trust architecture compatible version 6
|
||||
|
||||
config SYS_FSL_SEC_BE
|
||||
bool "Big-endian access to Freescale Secure Boot"
|
||||
|
||||
@@ -21,12 +21,12 @@ if SYS_FSL_DDR || SYS_FSL_MMDC
|
||||
config SYS_FSL_DDR_BE
|
||||
bool
|
||||
help
|
||||
Access DDR registers in big-endian
|
||||
Access DDR registers in big-endian
|
||||
|
||||
config SYS_FSL_DDR_LE
|
||||
bool
|
||||
help
|
||||
Access DDR registers in little-endian
|
||||
Access DDR registers in little-endian
|
||||
|
||||
config FSL_DDR_BIST
|
||||
bool
|
||||
|
||||
@@ -3,14 +3,14 @@
|
||||
if ARCH_K3
|
||||
|
||||
config TI_K3_NAVSS_UDMA
|
||||
bool "Texas Instruments UDMA"
|
||||
depends on ARCH_K3
|
||||
select DEVRES
|
||||
select DMA
|
||||
select TI_K3_NAVSS_RINGACC
|
||||
select TI_K3_PSIL
|
||||
help
|
||||
Support for UDMA used in K3 devices.
|
||||
bool "Texas Instruments UDMA"
|
||||
depends on ARCH_K3
|
||||
select DEVRES
|
||||
select DMA
|
||||
select TI_K3_NAVSS_RINGACC
|
||||
select TI_K3_PSIL
|
||||
help
|
||||
Support for UDMA used in K3 devices.
|
||||
endif
|
||||
|
||||
config TI_K3_PSIL
|
||||
|
||||
+24
-24
@@ -294,9 +294,9 @@ config MAX7320_GPIO
|
||||
bool "MAX7320 I2C GPIO Expander driver"
|
||||
depends on DM_GPIO && DM_I2C
|
||||
help
|
||||
Support for MAX7320 I2C 8/16-bit GPIO expander.
|
||||
original maxim device has 8 push/pull outputs,
|
||||
some clones offers 16bit.
|
||||
Support for MAX7320 I2C 8/16-bit GPIO expander.
|
||||
original maxim device has 8 push/pull outputs,
|
||||
some clones offers 16bit.
|
||||
|
||||
config MAX77663_GPIO
|
||||
bool "MAX77663 GPIO cell of PMIC driver"
|
||||
@@ -313,23 +313,23 @@ config MCP230XX_GPIO
|
||||
help
|
||||
Support for Microchip's MCP230XX I2C and SPI connected GPIO devices.
|
||||
The following chips are supported:
|
||||
- MCP23008
|
||||
- MCP23017
|
||||
- MCP23018
|
||||
- MCP23S08
|
||||
- MCP23S17
|
||||
- MCP23S18
|
||||
- MCP23008
|
||||
- MCP23017
|
||||
- MCP23018
|
||||
- MCP23S08
|
||||
- MCP23S17
|
||||
- MCP23S18
|
||||
|
||||
config MSCC_SGPIO
|
||||
bool "Microsemi Serial GPIO driver"
|
||||
depends on DM_GPIO && SOC_VCOREIII
|
||||
help
|
||||
Support for the VCoreIII SoC serial GPIO device. By using a
|
||||
serial interface, the SIO controller significantly extends
|
||||
the number of available GPIOs with a minimum number of
|
||||
additional pins on the device. The primary purpose of the
|
||||
SIO controller is to connect control signals from SFP
|
||||
modules and to act as an LED controller.
|
||||
serial interface, the SIO controller significantly extends
|
||||
the number of available GPIOs with a minimum number of
|
||||
additional pins on the device. The primary purpose of the
|
||||
SIO controller is to connect control signals from SFP
|
||||
modules and to act as an LED controller.
|
||||
|
||||
config MSM_GPIO
|
||||
bool "Qualcomm GPIO driver"
|
||||
@@ -404,8 +404,8 @@ config PCF8575_GPIO
|
||||
bool "PCF8575 I2C GPIO Expander driver"
|
||||
depends on DM_GPIO && DM_I2C
|
||||
help
|
||||
Support for PCF8575 I2C 16-bit GPIO expander. Most of these
|
||||
chips are from NXP and TI.
|
||||
Support for PCF8575 I2C 16-bit GPIO expander. Most of these
|
||||
chips are from NXP and TI.
|
||||
|
||||
config RCAR_GPIO
|
||||
bool "Renesas R-Car GPIO driver"
|
||||
@@ -459,9 +459,9 @@ config SUNXI_GPIO
|
||||
config SUNXI_NEW_PINCTRL
|
||||
bool
|
||||
depends on SUNXI_GPIO
|
||||
---help---
|
||||
The Allwinner D1 and other new SoCs use a different register map
|
||||
for the GPIO block, which we need to know about in the SPL.
|
||||
help
|
||||
The Allwinner D1 and other new SoCs use a different register map
|
||||
for the GPIO block, which we need to know about in the SPL.
|
||||
|
||||
config XILINX_GPIO
|
||||
bool "Xilinx GPIO driver"
|
||||
@@ -728,15 +728,15 @@ config SLG7XL45106_I2C_GPO
|
||||
bool "slg7xl45106 i2c gpo expander"
|
||||
depends on DM_GPIO && ARCH_ZYNQMP
|
||||
help
|
||||
Support for slg7xl45106 i2c gpo expander. It is an i2c based
|
||||
8-bit gpo expander, all gpo lines are controlled by writing
|
||||
value into data register.
|
||||
Support for slg7xl45106 i2c gpo expander. It is an i2c based
|
||||
8-bit gpo expander, all gpo lines are controlled by writing
|
||||
value into data register.
|
||||
|
||||
config GPIO_SCMI
|
||||
bool "SCMI GPIO pinctrl driver"
|
||||
depends on DM_GPIO && PINCTRL_SCMI
|
||||
help
|
||||
Support pinctrl GPIO over the SCMI interface.
|
||||
Support pinctrl GPIO over the SCMI interface.
|
||||
|
||||
config ADP5585_GPIO
|
||||
bool "ADP5585 GPIO driver"
|
||||
@@ -761,6 +761,6 @@ config MPFS_GPIO
|
||||
bool "Enable Polarfire SoC GPIO driver"
|
||||
depends on DM_GPIO
|
||||
help
|
||||
Enable to support the GPIO driver on Polarfire SoC
|
||||
Enable to support the GPIO driver on Polarfire SoC
|
||||
|
||||
endif
|
||||
|
||||
+1
-1
@@ -133,7 +133,7 @@ config LED_GPIO
|
||||
|
||||
config SPL_LED_GPIO
|
||||
bool "LED support for GPIO-connected LEDs in SPL"
|
||||
depends on SPL_LED && SPL_DM_GPIO
|
||||
depends on SPL_LED && SPL_DM_GPIO
|
||||
help
|
||||
This option is an SPL-variant of the LED_GPIO option.
|
||||
See the help of LED_GPIO for details.
|
||||
|
||||
@@ -44,15 +44,15 @@ config STM32_OMM
|
||||
This driver manages the muxing between the 2 OSPI busses and
|
||||
the 2 output ports. There are 4 possible muxing configurations:
|
||||
- direct mode (no multiplexing): OSPI1 output is on port 1 and OSPI2
|
||||
output is on port 2
|
||||
output is on port 2
|
||||
- OSPI1 and OSPI2 are multiplexed over the same output port 1
|
||||
- swapped mode (no multiplexing), OSPI1 output is on port 2,
|
||||
OSPI2 output is on port 1
|
||||
OSPI2 output is on port 1
|
||||
- OSPI1 and OSPI2 are multiplexed over the same output port 2
|
||||
It also manages :
|
||||
- the split of the memory area shared between the 2 OSPI instances.
|
||||
- chip select selection override.
|
||||
- the time between 2 transactions in multiplexed mode.
|
||||
- the split of the memory area shared between the 2 OSPI instances.
|
||||
- chip select selection override.
|
||||
- the time between 2 transactions in multiplexed mode.
|
||||
|
||||
config TI_AEMIF
|
||||
tristate "Texas Instruments AEMIF driver"
|
||||
@@ -71,9 +71,9 @@ config TI_GPMC
|
||||
depends on MEMORY && CLK && OF_CONTROL
|
||||
help
|
||||
This driver is for the General Purpose Memory Controller (GPMC)
|
||||
present on Texas Instruments SoCs (e.g. OMAP2+). GPMC allows
|
||||
interfacing to a variety of asynchronous as well as synchronous
|
||||
memory drives like NOR, NAND, OneNAND, SRAM.
|
||||
present on Texas Instruments SoCs (e.g. OMAP2+). GPMC allows
|
||||
interfacing to a variety of asynchronous as well as synchronous
|
||||
memory drives like NOR, NAND, OneNAND, SRAM.
|
||||
|
||||
if TI_GPMC
|
||||
config TI_GPMC_DEBUG
|
||||
|
||||
+3
-3
@@ -1,4 +1,4 @@
|
||||
config MFD_ATMEL_SMC
|
||||
bool "Atmel Static Memory Controller driver"
|
||||
help
|
||||
Say yes here to support Atmel Static Memory Controller driver.
|
||||
bool "Atmel Static Memory Controller driver"
|
||||
help
|
||||
Say yes here to support Atmel Static Memory Controller driver.
|
||||
|
||||
@@ -71,9 +71,9 @@ config ATSHA204A
|
||||
select BITREVERSE
|
||||
depends on MISC
|
||||
help
|
||||
Enable support for I2C connected Atmel's ATSHA204A
|
||||
CryptoAuthentication module found for example on the Turris Omnia
|
||||
board.
|
||||
Enable support for I2C connected Atmel's ATSHA204A
|
||||
CryptoAuthentication module found for example on the Turris Omnia
|
||||
board.
|
||||
|
||||
config GATEWORKS_SC
|
||||
bool "Gateworks System Controller Support"
|
||||
@@ -94,7 +94,7 @@ config QCOM_GENI
|
||||
etc.
|
||||
|
||||
config ROCKCHIP_EFUSE
|
||||
bool "Rockchip e-fuse support"
|
||||
bool "Rockchip e-fuse support"
|
||||
depends on MISC
|
||||
help
|
||||
Enable (read-only) access for the e-fuse block found in Rockchip
|
||||
|
||||
+4
-4
@@ -332,7 +332,7 @@ config MMC_MESON_GX
|
||||
bool "Meson GX EMMC controller support"
|
||||
depends on ARCH_MESON
|
||||
help
|
||||
Support for EMMC host controller on Meson GX ARM SoCs platform (S905)
|
||||
Support for EMMC host controller on Meson GX ARM SoCs platform (S905)
|
||||
|
||||
config MMC_OWL
|
||||
bool "Actions OWL Multimedia Card Interface support"
|
||||
@@ -659,8 +659,8 @@ config MMC_SDHCI_MSM
|
||||
depends on MMC_SDHCI && ARCH_SNAPDRAGON
|
||||
help
|
||||
Enables support for SDHCI 2.0 controller present on some Qualcomm
|
||||
Snapdragon devices. This device is compatible with eMMC v4.5 and
|
||||
SD 3.0 specifications. Both SD and eMMC devices are supported.
|
||||
Snapdragon devices. This device is compatible with eMMC v4.5 and
|
||||
SD 3.0 specifications. Both SD and eMMC devices are supported.
|
||||
Card-detect gpios are not supported.
|
||||
|
||||
config MMC_SDHCI_MV
|
||||
@@ -852,7 +852,7 @@ config FTSDC010_SDIO
|
||||
bool "Support ftsdc010 sdio"
|
||||
depends on FTSDC010
|
||||
help
|
||||
This can enable ftsdc010 sdio function.
|
||||
This can enable ftsdc010 sdio function.
|
||||
|
||||
config MMC_MTK
|
||||
bool "MediaTek SD/MMC Card Interface support"
|
||||
|
||||
+6
-6
@@ -5,17 +5,17 @@ config MULTIPLEXER
|
||||
depends on DM
|
||||
select DEVRES
|
||||
help
|
||||
The mux framework is a minimalistic subsystem that handles multiplexer
|
||||
controllers. It provides the same API as Linux and mux drivers should
|
||||
be portable with a minimum effort.
|
||||
The mux framework is a minimalistic subsystem that handles multiplexer
|
||||
controllers. It provides the same API as Linux and mux drivers should
|
||||
be portable with a minimum effort.
|
||||
|
||||
if MULTIPLEXER
|
||||
|
||||
config SPL_MUX_MMIO
|
||||
bool "MMIO register bitfield-controlled Multiplexer"
|
||||
depends on MULTIPLEXER && SYSCON
|
||||
help
|
||||
MMIO register bitfield-controlled Multiplexer controller.
|
||||
depends on MULTIPLEXER && SYSCON
|
||||
help
|
||||
MMIO register bitfield-controlled Multiplexer controller.
|
||||
|
||||
The driver builds multiplexer controllers for bitfields in a syscon
|
||||
register. For N bit wide bitfields, there will be 2^N possible
|
||||
|
||||
+8
-8
@@ -101,11 +101,11 @@ config PCI_ENHANCED_ALLOCATION
|
||||
devices in place of traditional BARS for allocation of resources.
|
||||
|
||||
config PCI_ARID
|
||||
bool "Enable Alternate Routing-ID support for PCI"
|
||||
help
|
||||
Say Y here if you want to enable Alternate Routing-ID capability
|
||||
support on PCI devices. This helps to skip some devices in BDF
|
||||
scan that are not present.
|
||||
bool "Enable Alternate Routing-ID support for PCI"
|
||||
help
|
||||
Say Y here if you want to enable Alternate Routing-ID capability
|
||||
support on PCI devices. This helps to skip some devices in BDF
|
||||
scan that are not present.
|
||||
|
||||
config PCI_SCAN_SHOW
|
||||
bool "Show PCI devices during startup"
|
||||
@@ -287,7 +287,7 @@ config PCI_IOMMU_EXTRA_MAPPINGS
|
||||
the node describing the PCI controller.
|
||||
The intent is to cover SR-IOV scenarios which need mappings for VFs
|
||||
and PCI hot-plug scenarios. More documentation can be found under:
|
||||
arch/arm/cpu/armv8/fsl-layerscape/doc/README.pci_iommu_extra
|
||||
arch/arm/cpu/armv8/fsl-layerscape/doc/README.pci_iommu_extra
|
||||
|
||||
config PCIE_LAYERSCAPE_EP
|
||||
bool "Layerscape PCIe Endpoint mode support"
|
||||
@@ -440,8 +440,8 @@ config PCIE_XILINX_NWL
|
||||
bool "Xilinx NWL PCIe controller"
|
||||
depends on ARCH_ZYNQMP
|
||||
help
|
||||
Say 'Y' here if you want support for Xilinx / AMD NWL PCIe
|
||||
controller as Root Port.
|
||||
Say 'Y' here if you want support for Xilinx / AMD NWL PCIe
|
||||
controller as Root Port.
|
||||
|
||||
config PCIE_PLDA_COMMON
|
||||
bool
|
||||
|
||||
@@ -9,10 +9,10 @@ config PCI_ENDPOINT
|
||||
bool "PCI Endpoint Support"
|
||||
depends on DM
|
||||
help
|
||||
Enable this configuration option to support configurable PCI
|
||||
endpoints. This should be enabled if the platform has a PCI
|
||||
controllers that can operate in endpoint mode (as a device
|
||||
connected to PCI host or bridge).
|
||||
Enable this configuration option to support configurable PCI
|
||||
endpoints. This should be enabled if the platform has a PCI
|
||||
controllers that can operate in endpoint mode (as a device
|
||||
connected to PCI host or bridge).
|
||||
|
||||
config PCIE_CADENCE_EP
|
||||
bool "Cadence PCIe endpoint controller"
|
||||
|
||||
+9
-9
@@ -72,14 +72,14 @@ config AB8500_USB_PHY
|
||||
Support for the USB OTG PHY in ST-Ericsson AB8500.
|
||||
|
||||
config APPLE_ATCPHY
|
||||
bool "Apple Type-C PHY Driver"
|
||||
depends on PHY && ARCH_APPLE
|
||||
default y
|
||||
help
|
||||
Support for the Apple Type-C PHY.
|
||||
bool "Apple Type-C PHY Driver"
|
||||
depends on PHY && ARCH_APPLE
|
||||
default y
|
||||
help
|
||||
Support for the Apple Type-C PHY.
|
||||
|
||||
This is a dummy driver since the PHY is initialized
|
||||
sufficiently by previous stage firmware.
|
||||
This is a dummy driver since the PHY is initialized
|
||||
sufficiently by previous stage firmware.
|
||||
|
||||
config BCM6318_USBH_PHY
|
||||
bool "BCM6318 USBH PHY support"
|
||||
@@ -249,14 +249,14 @@ config MT7620_USB_PHY
|
||||
depends on PHY
|
||||
depends on SOC_MT7620
|
||||
help
|
||||
Support the intergated USB PHY in MediaTek MT7620 SoC
|
||||
Support the intergated USB PHY in MediaTek MT7620 SoC
|
||||
|
||||
config MT76X8_USB_PHY
|
||||
bool "MediaTek MT76x8 (7628/88) USB PHY support"
|
||||
depends on PHY
|
||||
depends on SOC_MT7628
|
||||
help
|
||||
Support the USB PHY in MT76x8 SoCs
|
||||
Support the USB PHY in MT76x8 SoCs
|
||||
|
||||
This PHY is found on MT76x8 devices supporting USB.
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@ config MSM8916_USB_PHY
|
||||
bool
|
||||
select PHY
|
||||
help
|
||||
Support the Qualcomm MSM8916 USB PHY
|
||||
Support the Qualcomm MSM8916 USB PHY
|
||||
|
||||
This PHY is found on qualcomm dragonboard410c development board.
|
||||
|
||||
|
||||
@@ -4,19 +4,19 @@ menuconfig ASPEED_RAM
|
||||
depends on ARCH_ASPEED || TARGET_ASPEED_AST2700_IBEX
|
||||
default ARCH_ASPEED
|
||||
help
|
||||
Configuration options for DDR SDRAM on ASPEED systems.
|
||||
Configuration options for DDR SDRAM on ASPEED systems.
|
||||
|
||||
RAM initialisation is always built in for the platform. This menu
|
||||
allows customisation of the configuration used.
|
||||
RAM initialisation is always built in for the platform. This menu
|
||||
allows customisation of the configuration used.
|
||||
|
||||
config ASPEED_DDR4_DUALX8
|
||||
bool "Enable Dual X8 DDR4 die"
|
||||
depends on ASPEED_RAM
|
||||
help
|
||||
Say Y if dual X8 DDR4 die is used on the board. The ASPEED DDRM
|
||||
SRAM controller needs to know if the memory chip mounted on the
|
||||
board is dual x8 die or not, otherwise it may get the wrong
|
||||
size of the memory space.
|
||||
Say Y if dual X8 DDR4 die is used on the board. The ASPEED DDRM
|
||||
SRAM controller needs to know if the memory chip mounted on the
|
||||
board is dual x8 die or not, otherwise it may get the wrong
|
||||
size of the memory space.
|
||||
|
||||
config ASPEED_BYPASS_SELFTEST
|
||||
depends on ASPEED_RAM
|
||||
|
||||
@@ -2,14 +2,14 @@ config RAM_OCTEON
|
||||
bool "Ram drivers for Octeon SoCs"
|
||||
depends on RAM && ARCH_OCTEON
|
||||
help
|
||||
This enables support for RAM drivers for Octeon SoCs.
|
||||
This enables support for RAM drivers for Octeon SoCs.
|
||||
|
||||
if RAM_OCTEON
|
||||
|
||||
config RAM_OCTEON_DDR4
|
||||
bool "Octeon III DDR4 RAM support"
|
||||
help
|
||||
This enables support for DDR4 RAM suppoort for Octeon III. This does
|
||||
not include support for Octeon CN70XX.
|
||||
This enables support for DDR4 RAM suppoort for Octeon III. This does
|
||||
not include support for Octeon CN70XX.
|
||||
|
||||
endif # RAM_OCTEON
|
||||
|
||||
@@ -6,43 +6,43 @@ config STM32MP1_DDR
|
||||
select SPL_RAM if SPL
|
||||
default y
|
||||
help
|
||||
activate STM32MP1 DDR controller driver for STM32MP1 soc
|
||||
family: support for LPDDR2, LPDDR3 and DDR3
|
||||
the SDRAM parameters for controleur and phy need to be provided
|
||||
in device tree (computed by DDR tuning tools)
|
||||
activate STM32MP1 DDR controller driver for STM32MP1 soc
|
||||
family: support for LPDDR2, LPDDR3 and DDR3
|
||||
the SDRAM parameters for controleur and phy need to be provided
|
||||
in device tree (computed by DDR tuning tools)
|
||||
|
||||
config STM32MP1_DDR_INTERACTIVE
|
||||
bool "STM32MP1 DDR driver : interactive support"
|
||||
depends on STM32MP1_DDR
|
||||
help
|
||||
activate interactive support in STM32MP1 DDR controller driver
|
||||
used for DDR tuning tools
|
||||
to enter in intercative mode type 'd' during SPL DDR driver
|
||||
initialisation
|
||||
activate interactive support in STM32MP1 DDR controller driver
|
||||
used for DDR tuning tools
|
||||
to enter in intercative mode type 'd' during SPL DDR driver
|
||||
initialisation
|
||||
|
||||
config STM32MP1_DDR_INTERACTIVE_FORCE
|
||||
bool "STM32MP1 DDR driver : force interactive mode"
|
||||
depends on STM32MP1_DDR_INTERACTIVE
|
||||
help
|
||||
force interactive mode in STM32MP1 DDR controller driver
|
||||
skip the polling of character 'd' in console
|
||||
useful when SPL is loaded in sysram
|
||||
directly by programmer
|
||||
force interactive mode in STM32MP1 DDR controller driver
|
||||
skip the polling of character 'd' in console
|
||||
useful when SPL is loaded in sysram
|
||||
directly by programmer
|
||||
|
||||
config STM32MP1_DDR_TESTS
|
||||
bool "STM32MP1 DDR driver : tests support"
|
||||
depends on STM32MP1_DDR_INTERACTIVE
|
||||
default y
|
||||
help
|
||||
activate test support for interactive support in
|
||||
STM32MP1 DDR controller driver: command test
|
||||
activate test support for interactive support in
|
||||
STM32MP1 DDR controller driver: command test
|
||||
|
||||
config STM32MP1_DDR_TUNING
|
||||
bool "STM32MP1 DDR driver : support of tuning"
|
||||
depends on STM32MP1_DDR_INTERACTIVE
|
||||
default y
|
||||
help
|
||||
activate tuning command in STM32MP1 DDR interactive mode
|
||||
used for DDR tuning tools
|
||||
- DQ Deskew algorithm
|
||||
- DQS Trimming
|
||||
activate tuning command in STM32MP1 DDR interactive mode
|
||||
used for DDR tuning tools
|
||||
- DQ Deskew algorithm
|
||||
- DQS Trimming
|
||||
|
||||
@@ -11,26 +11,26 @@ config DM_REBOOT_MODE
|
||||
depends on DM
|
||||
select DEVRES
|
||||
help
|
||||
Enable support for reboot mode control. This will allow users to
|
||||
adjust the boot process based on reboot mode parameter
|
||||
passed to U-Boot.
|
||||
Enable support for reboot mode control. This will allow users to
|
||||
adjust the boot process based on reboot mode parameter
|
||||
passed to U-Boot.
|
||||
|
||||
config DM_REBOOT_MODE_GPIO
|
||||
bool "Use GPIOs as reboot mode backend"
|
||||
depends on DM_REBOOT_MODE
|
||||
help
|
||||
Use GPIOs to control the reboot mode. This will allow users to boot
|
||||
a device in a specific mode by using a GPIO that can be controlled
|
||||
outside U-Boot.
|
||||
Use GPIOs to control the reboot mode. This will allow users to boot
|
||||
a device in a specific mode by using a GPIO that can be controlled
|
||||
outside U-Boot.
|
||||
|
||||
config DM_REBOOT_MODE_RTC
|
||||
bool "Use RTC as reboot mode backend"
|
||||
depends on DM_RTC
|
||||
depends on DM_REBOOT_MODE
|
||||
help
|
||||
Use RTC non volatile memory to control the reboot mode. This will allow users to boot
|
||||
a device in a specific mode by using a register(s) that can be controlled
|
||||
outside U-Boot (e.g. Kernel).
|
||||
Use RTC non volatile memory to control the reboot mode. This will allow users to boot
|
||||
a device in a specific mode by using a register(s) that can be controlled
|
||||
outside U-Boot (e.g. Kernel).
|
||||
|
||||
config REBOOT_MODE_NVMEM
|
||||
bool "Use NVMEM reboot mode"
|
||||
|
||||
+2
-2
@@ -44,8 +44,8 @@ config VPL_DM_RTC
|
||||
config RTC_ENABLE_32KHZ_OUTPUT
|
||||
bool "Enable RTC 32Khz output"
|
||||
help
|
||||
Some real-time clocks support the output of 32kHz square waves (such as ds3231),
|
||||
the config symbol choose Real Time Clock device 32Khz output feature.
|
||||
Some real-time clocks support the output of 32kHz square waves (such as ds3231),
|
||||
the config symbol choose Real Time Clock device 32Khz output feature.
|
||||
|
||||
config RTC_ARMADA38X
|
||||
bool "Enable Armada 38x Marvell SoC RTC"
|
||||
|
||||
@@ -759,11 +759,11 @@ config MVEBU_A3700_UART
|
||||
config MCFUART
|
||||
bool "Freescale ColdFire UART support"
|
||||
depends on M68K
|
||||
help
|
||||
Choose this option to add support for UART driver on the ColdFire
|
||||
SoC's family. The serial communication channel provides a full-duplex
|
||||
asynchronous/synchronous receiver and transmitter deriving an
|
||||
operating frequency from the internal bus clock or an external clock.
|
||||
help
|
||||
Choose this option to add support for UART driver on the ColdFire
|
||||
SoC's family. The serial communication channel provides a full-duplex
|
||||
asynchronous/synchronous receiver and transmitter deriving an
|
||||
operating frequency from the internal bus clock or an external clock.
|
||||
|
||||
config MXC_UART
|
||||
bool "IMX serial port support"
|
||||
@@ -1027,9 +1027,9 @@ config OCTEON_SERIAL_BOOTCMD
|
||||
select SYS_CONSOLE_IS_IN_ENV
|
||||
select CONSOLE_MUX
|
||||
help
|
||||
This driver supports remote input over the PCIe bus from a host
|
||||
to U-Boot for entering commands. It is utilized by the host
|
||||
commands 'oct-remote-load' and 'oct-remote-bootcmd'.
|
||||
This driver supports remote input over the PCIe bus from a host
|
||||
to U-Boot for entering commands. It is utilized by the host
|
||||
commands 'oct-remote-load' and 'oct-remote-bootcmd'.
|
||||
|
||||
config OCTEON_SERIAL_PCIE_CONSOLE
|
||||
bool "MIPS Octeon PCIe remote console"
|
||||
|
||||
+15
-15
@@ -4,22 +4,22 @@ menuconfig SMEM
|
||||
if SMEM
|
||||
|
||||
config SANDBOX_SMEM
|
||||
bool "Sandbox Shared Memory Manager (SMEM)"
|
||||
depends on SANDBOX && DM
|
||||
help
|
||||
enable SMEM support for sandbox. This is an emulation of a real SMEM
|
||||
manager.
|
||||
The sandbox driver allocates a shared memory from the heap and
|
||||
initialzies it on start.
|
||||
bool "Sandbox Shared Memory Manager (SMEM)"
|
||||
depends on SANDBOX && DM
|
||||
help
|
||||
enable SMEM support for sandbox. This is an emulation of a real SMEM
|
||||
manager.
|
||||
The sandbox driver allocates a shared memory from the heap and
|
||||
initialzies it on start.
|
||||
|
||||
config MSM_SMEM
|
||||
bool "Qualcomm Shared Memory Manager (SMEM)"
|
||||
depends on DM
|
||||
depends on ARCH_SNAPDRAGON || ARCH_IPQ40XX
|
||||
select DEVRES
|
||||
help
|
||||
Enable support for the Qualcomm Shared Memory Manager.
|
||||
The driver provides an interface to items in a heap shared among all
|
||||
processors in a Qualcomm platform.
|
||||
bool "Qualcomm Shared Memory Manager (SMEM)"
|
||||
depends on DM
|
||||
depends on ARCH_SNAPDRAGON || ARCH_IPQ40XX
|
||||
select DEVRES
|
||||
help
|
||||
Enable support for the Qualcomm Shared Memory Manager.
|
||||
The driver provides an interface to items in a heap shared among all
|
||||
processors in a Qualcomm platform.
|
||||
|
||||
endif # menu "SMEM Support"
|
||||
|
||||
@@ -21,8 +21,8 @@ config TI_KEYSTONE_SERDES
|
||||
bool "Keystone SerDes driver for ethernet"
|
||||
depends on ARCH_KEYSTONE
|
||||
help
|
||||
SerDes driver for Keystone SoC used for ethernet support on TI
|
||||
K2 platforms.
|
||||
SerDes driver for Keystone SoC used for ethernet support on TI
|
||||
K2 platforms.
|
||||
|
||||
config TI_PRUSS
|
||||
bool "Support for TI's K3 based Pruss driver"
|
||||
|
||||
+14
-14
@@ -2,10 +2,10 @@ menuconfig SPI
|
||||
bool "SPI Support"
|
||||
help
|
||||
The "Serial Peripheral Interface" is a low level synchronous
|
||||
protocol. Chips that support SPI can have data transfer rates
|
||||
up to several tens of Mbit/sec. Chips are addressed with a
|
||||
controller and a chipselect. Most SPI slaves don't support
|
||||
dynamic device discovery; some are even write-only or read-only.
|
||||
protocol. Chips that support SPI can have data transfer rates
|
||||
up to several tens of Mbit/sec. Chips are addressed with a
|
||||
controller and a chipselect. Most SPI slaves don't support
|
||||
dynamic device discovery; some are even write-only or read-only.
|
||||
|
||||
SPI is widely used by microcontrollers to talk with sensors,
|
||||
eeprom and flash memory, codecs and various other controller
|
||||
@@ -200,11 +200,11 @@ config CADENCE_XSPI
|
||||
by using the Auto Command work mode.
|
||||
|
||||
config CF_SPI
|
||||
bool "ColdFire SPI driver"
|
||||
depends on M68K
|
||||
help
|
||||
Enable the ColdFire SPI driver. This driver can be used on
|
||||
some m68k SoCs.
|
||||
bool "ColdFire SPI driver"
|
||||
depends on M68K
|
||||
help
|
||||
Enable the ColdFire SPI driver. This driver can be used on
|
||||
some m68k SoCs.
|
||||
|
||||
config CV1800B_SPIF
|
||||
bool "Sophgo cv1800b SPI Flash Controller driver"
|
||||
@@ -352,7 +352,7 @@ config MTK_SNOR
|
||||
select DEVRES
|
||||
help
|
||||
Enable the Mediatek SPINOR controller driver. This driver has
|
||||
better read/write performance with NOR.
|
||||
better read/write performance with NOR.
|
||||
|
||||
config MTK_SNFI_SPI
|
||||
bool "Mediatek SPI memory controller driver"
|
||||
@@ -544,8 +544,8 @@ config SPI_SIFIVE
|
||||
config SOFT_SPI
|
||||
bool "Soft SPI driver"
|
||||
help
|
||||
Enable Soft SPI driver. This driver is to use GPIO simulate
|
||||
the SPI protocol.
|
||||
Enable Soft SPI driver. This driver is to use GPIO simulate
|
||||
the SPI protocol.
|
||||
|
||||
config SPI_SN_F_OSPI
|
||||
tristate "Socionext F_OSPI SPI flash controller"
|
||||
@@ -673,8 +673,8 @@ config ZYNQMP_GQSPI
|
||||
config SPI_STACKED_PARALLEL
|
||||
bool "Enable support for stacked or parallel memories"
|
||||
help
|
||||
Enable support for stacked/or parallel memories. This functionality
|
||||
may appear on Xilinx hardware. By default this is disabled.
|
||||
Enable support for stacked/or parallel memories. This functionality
|
||||
may appear on Xilinx hardware. By default this is disabled.
|
||||
|
||||
endif # if DM_SPI
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ menu "SPMI support"
|
||||
config SPMI
|
||||
bool "Enable SPMI bus support"
|
||||
depends on DM
|
||||
---help---
|
||||
help
|
||||
Select this to enable to support SPMI bus.
|
||||
SPMI (System Power Management Interface) bus is used
|
||||
to connect PMIC devices on various SoCs.
|
||||
@@ -11,13 +11,13 @@ config SPMI
|
||||
config SPMI_MSM
|
||||
bool "Support Qualcomm SPMI bus"
|
||||
depends on SPMI
|
||||
---help---
|
||||
help
|
||||
Support SPMI bus implementation found on Qualcomm Snapdragon SoCs.
|
||||
|
||||
config SPMI_SANDBOX
|
||||
bool "Support for Sandbox SPMI bus"
|
||||
depends on SPMI
|
||||
---help---
|
||||
help
|
||||
Demo SPMI bus implementation. Emulates part of PM8916 as single
|
||||
slave (0) on bus. It has 4 GPIO peripherals, pid 0xC0-0xC3.
|
||||
slave (0) on bus. It has 4 GPIO peripherals, pid 0xC0-0xC3.
|
||||
endmenu
|
||||
|
||||
+12
-12
@@ -13,9 +13,9 @@ config IMX_THERMAL
|
||||
depends on MX6 || MX7
|
||||
help
|
||||
Support for Temperature Monitor (TEMPMON) found on Freescale i.MX SoCs.
|
||||
It supports one critical trip point and one passive trip point. The
|
||||
cpufreq is used as the cooling device to throttle CPUs when the
|
||||
passive trip is crossed.
|
||||
It supports one critical trip point and one passive trip point. The
|
||||
cpufreq is used as the cooling device to throttle CPUs when the
|
||||
passive trip is crossed.
|
||||
|
||||
config IMX_SCU_THERMAL
|
||||
bool "Temperature sensor driver for NXP i.MX8"
|
||||
@@ -29,7 +29,7 @@ config IMX_SCU_THERMAL
|
||||
config IMX_TMU
|
||||
bool "Thermal Management Unit driver for NXP i.MX8M / i.MX93 and QorIQ"
|
||||
depends on ARCH_IMX8M || IMX93 || FSL_LAYERSCAPE
|
||||
help
|
||||
help
|
||||
Support for the NXP Thermal Management Unit (TMU) sensors on
|
||||
i.MX8M, i.MX93 and on QorIQ/Layerscape SoCs (LX2160A,
|
||||
LS1028A, LS1088A, ...).
|
||||
@@ -45,16 +45,16 @@ config RCAR_GEN3_THERMAL
|
||||
driver into the U-Boot thermal framework.
|
||||
|
||||
config TI_DRA7_THERMAL
|
||||
bool "Temperature sensor driver for TI dra7xx SOCs"
|
||||
help
|
||||
Enable thermal support for the Texas Instruments DRA752 SoC family.
|
||||
The driver supports reading CPU temperature.
|
||||
bool "Temperature sensor driver for TI dra7xx SOCs"
|
||||
help
|
||||
Enable thermal support for the Texas Instruments DRA752 SoC family.
|
||||
The driver supports reading CPU temperature.
|
||||
|
||||
config TI_LM74_THERMAL
|
||||
bool "Temperature sensor driver for TI LM74 chip"
|
||||
help
|
||||
Enable thermal support for the Texas Instruments LM74 chip.
|
||||
The driver supports reading CPU temperature.
|
||||
bool "Temperature sensor driver for TI LM74 chip"
|
||||
help
|
||||
Enable thermal support for the Texas Instruments LM74 chip.
|
||||
The driver supports reading CPU temperature.
|
||||
|
||||
config DM_THERMAL_JC42
|
||||
bool "JEDEC JC-42.4/TSE2004av SPD temperature sensor"
|
||||
|
||||
+2
-2
@@ -19,7 +19,7 @@ config UFS_AMD_VERSAL2
|
||||
config UFS_CADENCE
|
||||
bool "Cadence platform driver for UFS"
|
||||
depends on UFS
|
||||
help
|
||||
help
|
||||
This selects the platform driver for the Cadence UFS host
|
||||
controller present on present TI's J721e devices.
|
||||
|
||||
@@ -51,7 +51,7 @@ config UFS_PCI
|
||||
config UFS_QCOM
|
||||
bool "Qualcomm Host Controller driver for UFS"
|
||||
depends on UFS && ARCH_SNAPDRAGON
|
||||
help
|
||||
help
|
||||
This selects the platform driver for the UFS host
|
||||
controller present on Qualcomm Snapdragon SoCs.
|
||||
|
||||
|
||||
@@ -384,10 +384,10 @@ config WDT_SBSA
|
||||
bool "SBSA watchdog timer support"
|
||||
depends on WDT
|
||||
help
|
||||
Select this to enable SBSA watchdog timer.
|
||||
This driver can operate ARM SBSA Generic Watchdog as a single stage.
|
||||
In the single stage mode, when the timeout is reached, your system
|
||||
will be reset by WS1. The first signal (WS0) is ignored.
|
||||
Select this to enable SBSA watchdog timer.
|
||||
This driver can operate ARM SBSA Generic Watchdog as a single stage.
|
||||
In the single stage mode, when the timeout is reached, your system
|
||||
will be reset by WS1. The first signal (WS0) is ignored.
|
||||
|
||||
config WDT_SIEMENS_PMIC
|
||||
bool "Enable PMIC Watchdog Timer support for Siemens platforms"
|
||||
|
||||
Reference in New Issue
Block a user