2005-04-16 22:20:36 +00:00
|
|
|
#
|
|
|
|
|
# For a description of the syntax of this configuration file,
|
|
|
|
|
# see Documentation/kbuild/kconfig-language.txt.
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
menu "Firmware Drivers"
|
|
|
|
|
|
2015-07-31 14:46:16 +00:00
|
|
|
config ARM_PSCI_FW
|
|
|
|
|
bool
|
|
|
|
|
|
drivers: psci: PSCI checker module
On arm and arm64, PSCI is one of the possible firmware interfaces
used for power management. This includes both turning CPUs on and off,
and suspending them (entering idle states).
This patch adds a PSCI checker module that enables basic testing of
PSCI operations during startup. There are two main tests: CPU
hotplugging and suspending.
In the hotplug tests, the hotplug API is used to turn off and on again
all CPUs in the system, and then all CPUs in each cluster, checking
the consistency of the return codes.
In the suspend tests, a high-priority thread is created on each core
and uses low-level cpuidle functionalities to enter suspend, in all
the possible states and multiple times. This should allow a maximum
number of CPUs to enter the same sleep state at the same or slightly
different time.
In essence, the suspend tests use a principle similar to that of the
intel_powerclamp driver (drivers/thermal/intel_powerclamp.c), but the
threads are only kept for the duration of the test (they are already
gone when userspace is started) and it does not require to stop/start
the tick.
While in theory power management PSCI functions (CPU_{ON,OFF,SUSPEND})
could be directly called, this proved too difficult as it would imply
the duplication of all the logic used by the kernel to allow for a
clean shutdown/bringup/suspend of the CPU (the deepest sleep states
implying potentially the shutdown of the CPU).
Note that this file cannot be compiled as a loadable module, since it
uses a number of non-exported identifiers (essentially for
PSCI-specific checks and direct use of cpuidle) and relies on the
absence of userspace to avoid races when calling hotplug and cpuidle
functions.
For now at least, CONFIG_PSCI_CHECKER is mutually exclusive with
CONFIG_TORTURE_TEST, because torture tests may also use hotplug and
cause false positives in the hotplug tests.
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Kevin Hilman <khilman@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: James Morse <james.morse@arm.com>
Cc: Sudeep Holla <sudeep.holla@arm.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Mark Rutland <mark.rutland@arm.com>
Acked-by: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> [torture test config]
Signed-off-by: Kevin Brodsky <kevin.brodsky@arm.com>
[lpieralisi: added cpuidle locking, reworded commit log/kconfig entry]
Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
2016-11-08 17:55:46 +00:00
|
|
|
config ARM_PSCI_CHECKER
|
|
|
|
|
bool "ARM PSCI checker"
|
2017-07-31 08:55:00 +00:00
|
|
|
depends on ARM_PSCI_FW && HOTPLUG_CPU && CPU_IDLE && !TORTURE_TEST
|
drivers: psci: PSCI checker module
On arm and arm64, PSCI is one of the possible firmware interfaces
used for power management. This includes both turning CPUs on and off,
and suspending them (entering idle states).
This patch adds a PSCI checker module that enables basic testing of
PSCI operations during startup. There are two main tests: CPU
hotplugging and suspending.
In the hotplug tests, the hotplug API is used to turn off and on again
all CPUs in the system, and then all CPUs in each cluster, checking
the consistency of the return codes.
In the suspend tests, a high-priority thread is created on each core
and uses low-level cpuidle functionalities to enter suspend, in all
the possible states and multiple times. This should allow a maximum
number of CPUs to enter the same sleep state at the same or slightly
different time.
In essence, the suspend tests use a principle similar to that of the
intel_powerclamp driver (drivers/thermal/intel_powerclamp.c), but the
threads are only kept for the duration of the test (they are already
gone when userspace is started) and it does not require to stop/start
the tick.
While in theory power management PSCI functions (CPU_{ON,OFF,SUSPEND})
could be directly called, this proved too difficult as it would imply
the duplication of all the logic used by the kernel to allow for a
clean shutdown/bringup/suspend of the CPU (the deepest sleep states
implying potentially the shutdown of the CPU).
Note that this file cannot be compiled as a loadable module, since it
uses a number of non-exported identifiers (essentially for
PSCI-specific checks and direct use of cpuidle) and relies on the
absence of userspace to avoid races when calling hotplug and cpuidle
functions.
For now at least, CONFIG_PSCI_CHECKER is mutually exclusive with
CONFIG_TORTURE_TEST, because torture tests may also use hotplug and
cause false positives in the hotplug tests.
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Kevin Hilman <khilman@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: James Morse <james.morse@arm.com>
Cc: Sudeep Holla <sudeep.holla@arm.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Mark Rutland <mark.rutland@arm.com>
Acked-by: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> [torture test config]
Signed-off-by: Kevin Brodsky <kevin.brodsky@arm.com>
[lpieralisi: added cpuidle locking, reworded commit log/kconfig entry]
Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
2016-11-08 17:55:46 +00:00
|
|
|
help
|
|
|
|
|
Run the PSCI checker during startup. This checks that hotplug and
|
|
|
|
|
suspend operations work correctly when using PSCI.
|
|
|
|
|
|
|
|
|
|
The torture tests may interfere with the PSCI checker by turning CPUs
|
|
|
|
|
on and off through hotplug, so for now torture tests and PSCI checker
|
|
|
|
|
are mutually exclusive.
|
|
|
|
|
|
2017-03-28 10:36:07 +00:00
|
|
|
config ARM_SCMI_PROTOCOL
|
|
|
|
|
bool "ARM System Control and Management Interface (SCMI) Message Protocol"
|
|
|
|
|
depends on ARM || ARM64 || COMPILE_TEST
|
|
|
|
|
depends on MAILBOX
|
|
|
|
|
help
|
|
|
|
|
ARM System Control and Management Interface (SCMI) protocol is a
|
|
|
|
|
set of operating system-independent software interfaces that are
|
|
|
|
|
used in system management. SCMI is extensible and currently provides
|
|
|
|
|
interfaces for: Discovery and self-description of the interfaces
|
|
|
|
|
it supports, Power domain management which is the ability to place
|
|
|
|
|
a given device or domain into the various power-saving states that
|
|
|
|
|
it supports, Performance management which is the ability to control
|
|
|
|
|
the performance of a domain that is composed of compute engines
|
|
|
|
|
such as application processors and other accelerators, Clock
|
|
|
|
|
management which is the ability to set and inquire rates on platform
|
|
|
|
|
managed clocks and Sensor management which is the ability to read
|
|
|
|
|
sensor data, and be notified of sensor value.
|
|
|
|
|
|
|
|
|
|
This protocol library provides interface for all the client drivers
|
|
|
|
|
making use of the features offered by the SCMI.
|
|
|
|
|
|
2017-06-14 12:48:26 +00:00
|
|
|
config ARM_SCMI_POWER_DOMAIN
|
|
|
|
|
tristate "SCMI power domain driver"
|
|
|
|
|
depends on ARM_SCMI_PROTOCOL || (COMPILE_TEST && OF)
|
|
|
|
|
default y
|
|
|
|
|
select PM_GENERIC_DOMAINS if PM
|
|
|
|
|
help
|
|
|
|
|
This enables support for the SCMI power domains which can be
|
|
|
|
|
enabled or disabled via the SCP firmware
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called scmi_pm_domain. Note this may needed early in boot
|
|
|
|
|
before rootfs may be available.
|
|
|
|
|
|
2015-03-30 09:59:52 +00:00
|
|
|
config ARM_SCPI_PROTOCOL
|
|
|
|
|
tristate "ARM System Control and Power Interface (SCPI) Message Protocol"
|
2017-01-30 08:52:01 +00:00
|
|
|
depends on ARM || ARM64 || COMPILE_TEST
|
2016-06-05 17:23:21 +00:00
|
|
|
depends on MAILBOX
|
2015-03-30 09:59:52 +00:00
|
|
|
help
|
|
|
|
|
System Control and Power Interface (SCPI) Message Protocol is
|
|
|
|
|
defined for the purpose of communication between the Application
|
|
|
|
|
Cores(AP) and the System Control Processor(SCP). The MHU peripheral
|
|
|
|
|
provides a mechanism for inter-processor communication between SCP
|
|
|
|
|
and AP.
|
|
|
|
|
|
|
|
|
|
SCP controls most of the power managament on the Application
|
|
|
|
|
Processors. It offers control and management of: the core/cluster
|
|
|
|
|
power states, various power domain DVFS including the core/cluster,
|
|
|
|
|
certain system clocks configuration, thermal sensors and many
|
|
|
|
|
others.
|
|
|
|
|
|
|
|
|
|
This protocol library provides interface for all the client drivers
|
|
|
|
|
making use of the features offered by the SCP.
|
|
|
|
|
|
2016-06-02 15:34:03 +00:00
|
|
|
config ARM_SCPI_POWER_DOMAIN
|
|
|
|
|
tristate "SCPI power domain driver"
|
2016-07-06 12:49:46 +00:00
|
|
|
depends on ARM_SCPI_PROTOCOL || (COMPILE_TEST && OF)
|
2016-06-02 15:34:03 +00:00
|
|
|
default y
|
|
|
|
|
select PM_GENERIC_DOMAINS if PM
|
|
|
|
|
help
|
|
|
|
|
This enables support for the SCPI power domains which can be
|
|
|
|
|
enabled or disabled via the SCP firmware
|
|
|
|
|
|
2018-01-08 15:38:09 +00:00
|
|
|
config ARM_SDE_INTERFACE
|
|
|
|
|
bool "ARM Software Delegated Exception Interface (SDEI)"
|
|
|
|
|
depends on ARM64
|
|
|
|
|
help
|
|
|
|
|
The Software Delegated Exception Interface (SDEI) is an ARM
|
|
|
|
|
standard for registering callbacks from the platform firmware
|
|
|
|
|
into the OS. This is typically used to implement RAS notifications.
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config EDD
|
2006-06-25 12:47:46 +00:00
|
|
|
tristate "BIOS Enhanced Disk Drive calls determine boot disk"
|
2009-12-15 02:01:16 +00:00
|
|
|
depends on X86
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
|
Say Y or M here if you want to enable BIOS Enhanced Disk Drive
|
|
|
|
|
Services real mode BIOS calls to determine which disk
|
|
|
|
|
BIOS tries boot from. This information is then exported via sysfs.
|
|
|
|
|
|
|
|
|
|
This option is experimental and is known to fail to boot on some
|
|
|
|
|
obscure configurations. Most disk controller BIOS vendors do
|
|
|
|
|
not yet implement this feature.
|
|
|
|
|
|
2008-04-29 08:02:45 +00:00
|
|
|
config EDD_OFF
|
|
|
|
|
bool "Sets default behavior for EDD detection to off"
|
|
|
|
|
depends on EDD
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Say Y if you want EDD disabled by default, even though it is compiled into the
|
|
|
|
|
kernel. Say N if you want EDD enabled by default. EDD can be dynamically set
|
|
|
|
|
using the kernel parameter 'edd={on|skipmbr|off}'.
|
|
|
|
|
|
2008-06-27 11:12:54 +00:00
|
|
|
config FIRMWARE_MEMMAP
|
2011-01-20 22:44:16 +00:00
|
|
|
bool "Add firmware-provided memory map to sysfs" if EXPERT
|
2009-12-15 02:01:16 +00:00
|
|
|
default X86
|
2008-06-27 11:12:54 +00:00
|
|
|
help
|
|
|
|
|
Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
|
|
|
|
|
That memory map is used for example by kexec to set up parameter area
|
|
|
|
|
for the next kernel, but can also be used for debugging purposes.
|
|
|
|
|
|
|
|
|
|
See also Documentation/ABI/testing/sysfs-firmware-memmap.
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config EFI_PCDP
|
|
|
|
|
bool "Console device selection via EFI PCDP or HCDP table"
|
|
|
|
|
depends on ACPI && EFI && IA64
|
|
|
|
|
default y if IA64
|
|
|
|
|
help
|
|
|
|
|
If your firmware supplies the PCDP table, and you want to
|
|
|
|
|
automatically use the primary console device it describes
|
|
|
|
|
as the Linux console, say Y here.
|
|
|
|
|
|
|
|
|
|
If your firmware supplies the HCDP table, and you want to
|
|
|
|
|
use the first serial port it describes as the Linux console,
|
|
|
|
|
say Y here. If your EFI ConOut path contains only a UART
|
|
|
|
|
device, it will become the console automatically. Otherwise,
|
|
|
|
|
you must specify the "console=hcdp" kernel boot argument.
|
|
|
|
|
|
|
|
|
|
Neither the PCDP nor the HCDP affects naming of serial devices,
|
|
|
|
|
so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending
|
|
|
|
|
on how the driver discovers devices.
|
|
|
|
|
|
|
|
|
|
You must also enable the appropriate drivers (serial, VGA, etc.)
|
|
|
|
|
|
2010-10-18 09:03:14 +00:00
|
|
|
See DIG64_HCDPv20_042804.pdf available from
|
|
|
|
|
<http://www.dig64.org/specifications/>
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2005-09-06 22:17:14 +00:00
|
|
|
config DELL_RBU
|
|
|
|
|
tristate "BIOS update support for DELL systems via sysfs"
|
2005-11-22 05:32:30 +00:00
|
|
|
depends on X86
|
2005-09-06 22:17:14 +00:00
|
|
|
select FW_LOADER
|
2013-05-22 16:28:37 +00:00
|
|
|
select FW_LOADER_USER_HELPER
|
2005-09-06 22:17:14 +00:00
|
|
|
help
|
|
|
|
|
Say m if you want to have the option of updating the BIOS for your
|
|
|
|
|
DELL system. Note you need a Dell OpenManage or Dell Update package (DUP)
|
2006-10-03 20:31:37 +00:00
|
|
|
supporting application to communicate with the BIOS regarding the new
|
2005-09-06 22:17:14 +00:00
|
|
|
image for the image update to take effect.
|
|
|
|
|
See <file:Documentation/dell_rbu.txt> for more details on the driver.
|
2005-09-06 22:17:15 +00:00
|
|
|
|
|
|
|
|
config DCDBAS
|
|
|
|
|
tristate "Dell Systems Management Base Driver"
|
2005-10-30 22:59:20 +00:00
|
|
|
depends on X86
|
2005-09-06 22:17:15 +00:00
|
|
|
help
|
|
|
|
|
The Dell Systems Management Base Driver provides a sysfs interface
|
|
|
|
|
for systems management software to perform System Management
|
|
|
|
|
Interrupts (SMIs) and Host Control Actions (system power cycle or
|
|
|
|
|
power off after OS shutdown) on certain Dell systems.
|
|
|
|
|
|
|
|
|
|
See <file:Documentation/dcdbas.txt> for more details on the driver
|
|
|
|
|
and the Dell systems on which Dell systems management software makes
|
|
|
|
|
use of this driver.
|
|
|
|
|
|
|
|
|
|
Say Y or M here to enable the driver for use by Dell systems
|
|
|
|
|
management software such as Dell OpenManage.
|
|
|
|
|
|
2007-05-08 20:07:02 +00:00
|
|
|
config DMIID
|
|
|
|
|
bool "Export DMI identification via sysfs to userspace"
|
|
|
|
|
depends on DMI
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to query SMBIOS/DMI system identification
|
|
|
|
|
information from userspace through /sys/class/dmi/id/ or if you want
|
|
|
|
|
DMI-based module auto-loading.
|
|
|
|
|
|
2011-02-23 01:53:21 +00:00
|
|
|
config DMI_SYSFS
|
|
|
|
|
tristate "DMI table support in sysfs"
|
|
|
|
|
depends on SYSFS && DMI
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Say Y or M here to enable the exporting of the raw DMI table
|
|
|
|
|
data via sysfs. This is useful for consuming the data without
|
|
|
|
|
requiring any access to /dev/mem at all. Tables are found
|
|
|
|
|
under /sys/firmware/dmi when this option is enabled and
|
|
|
|
|
loaded.
|
|
|
|
|
|
2014-01-23 23:54:39 +00:00
|
|
|
config DMI_SCAN_MACHINE_NON_EFI_FALLBACK
|
|
|
|
|
bool
|
|
|
|
|
|
2008-04-10 02:50:41 +00:00
|
|
|
config ISCSI_IBFT_FIND
|
|
|
|
|
bool "iSCSI Boot Firmware Table Attributes"
|
2013-12-06 08:52:19 +00:00
|
|
|
depends on X86 && ACPI
|
2008-04-10 02:50:41 +00:00
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
This option enables the kernel to find the region of memory
|
|
|
|
|
in which the ISCSI Boot Firmware Table (iBFT) resides. This
|
|
|
|
|
is necessary for iSCSI Boot Firmware Table Attributes module to work
|
|
|
|
|
properly.
|
|
|
|
|
|
|
|
|
|
config ISCSI_IBFT
|
|
|
|
|
tristate "iSCSI Boot Firmware Table Attributes module"
|
2010-04-12 18:06:18 +00:00
|
|
|
select ISCSI_BOOT_SYSFS
|
2010-10-14 01:07:16 +00:00
|
|
|
depends on ISCSI_IBFT_FIND && SCSI && SCSI_LOWLEVEL
|
2008-04-10 02:50:41 +00:00
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
This option enables support for detection and exposing of iSCSI
|
|
|
|
|
Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
|
|
|
|
|
detect iSCSI boot parameters dynamically during system boot, say Y.
|
|
|
|
|
Otherwise, say N.
|
|
|
|
|
|
2015-02-26 10:08:06 +00:00
|
|
|
config RASPBERRYPI_FIRMWARE
|
|
|
|
|
tristate "Raspberry Pi Firmware Driver"
|
|
|
|
|
depends on BCM2835_MBOX
|
|
|
|
|
help
|
|
|
|
|
This option enables support for communicating with the firmware on the
|
|
|
|
|
Raspberry Pi.
|
|
|
|
|
|
2016-01-28 14:23:11 +00:00
|
|
|
config FW_CFG_SYSFS
|
|
|
|
|
tristate "QEMU fw_cfg device support in sysfs"
|
|
|
|
|
depends on SYSFS && (ARM || ARM64 || PPC_PMAC || SPARC || X86)
|
2016-02-11 14:23:51 +00:00
|
|
|
depends on HAS_IOPORT_MAP
|
2016-01-28 14:23:11 +00:00
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Say Y or M here to enable the exporting of the QEMU firmware
|
|
|
|
|
configuration (fw_cfg) file entries via sysfs. Entries are
|
|
|
|
|
found under /sys/firmware/fw_cfg when this option is enabled
|
|
|
|
|
and loaded.
|
|
|
|
|
|
|
|
|
|
config FW_CFG_SYSFS_CMDLINE
|
|
|
|
|
bool "QEMU fw_cfg device parameter parsing"
|
|
|
|
|
depends on FW_CFG_SYSFS
|
|
|
|
|
help
|
|
|
|
|
Allow the qemu_fw_cfg device to be initialized via the kernel
|
|
|
|
|
command line or using a module parameter.
|
|
|
|
|
WARNING: Using incorrect parameters (base address in particular)
|
|
|
|
|
may crash your system.
|
|
|
|
|
|
2015-02-26 21:49:09 +00:00
|
|
|
config QCOM_SCM
|
|
|
|
|
bool
|
|
|
|
|
depends on ARM || ARM64
|
2016-06-17 17:40:43 +00:00
|
|
|
select RESET_CONTROLLER
|
2015-02-26 21:49:09 +00:00
|
|
|
|
2015-09-11 21:01:16 +00:00
|
|
|
config QCOM_SCM_32
|
|
|
|
|
def_bool y
|
|
|
|
|
depends on QCOM_SCM && ARM
|
|
|
|
|
|
|
|
|
|
config QCOM_SCM_64
|
|
|
|
|
def_bool y
|
|
|
|
|
depends on QCOM_SCM && ARM64
|
|
|
|
|
|
2017-08-14 22:46:18 +00:00
|
|
|
config QCOM_SCM_DOWNLOAD_MODE_DEFAULT
|
|
|
|
|
bool "Qualcomm download mode enabled by default"
|
|
|
|
|
depends on QCOM_SCM
|
|
|
|
|
help
|
|
|
|
|
A device with "download mode" enabled will upon an unexpected
|
|
|
|
|
warm-restart enter a special debug mode that allows the user to
|
|
|
|
|
"download" memory content over USB for offline postmortem analysis.
|
|
|
|
|
The feature can be enabled/disabled on the kernel command line.
|
|
|
|
|
|
|
|
|
|
Say Y here to enable "download mode" by default.
|
|
|
|
|
|
2016-10-18 23:08:34 +00:00
|
|
|
config TI_SCI_PROTOCOL
|
|
|
|
|
tristate "TI System Control Interface (TISCI) Message Protocol"
|
|
|
|
|
depends on TI_MESSAGE_MANAGER
|
|
|
|
|
help
|
|
|
|
|
TI System Control Interface (TISCI) Message Protocol is used to manage
|
|
|
|
|
compute systems such as ARM, DSP etc with the system controller in
|
|
|
|
|
complex System on Chip(SoC) such as those found on certain keystone
|
|
|
|
|
generation SoC from TI.
|
|
|
|
|
|
|
|
|
|
System controller provides various facilities including power
|
|
|
|
|
management function support.
|
|
|
|
|
|
|
|
|
|
This protocol library is used by client drivers to use the features
|
|
|
|
|
provided by the system controller.
|
|
|
|
|
|
2016-01-04 14:37:32 +00:00
|
|
|
config HAVE_ARM_SMCCC
|
|
|
|
|
bool
|
|
|
|
|
|
2015-06-10 21:05:08 +00:00
|
|
|
source "drivers/firmware/broadcom/Kconfig"
|
2011-04-30 00:39:19 +00:00
|
|
|
source "drivers/firmware/google/Kconfig"
|
2013-02-08 15:48:51 +00:00
|
|
|
source "drivers/firmware/efi/Kconfig"
|
2016-08-27 13:43:43 +00:00
|
|
|
source "drivers/firmware/meson/Kconfig"
|
2016-08-19 17:05:04 +00:00
|
|
|
source "drivers/firmware/tegra/Kconfig"
|
2011-04-30 00:39:19 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
endmenu
|
