Loading...
1#
2# For a description of the syntax of this configuration file,
3# see Documentation/kbuild/kconfig-language.txt.
4#
5
6menu "Firmware Drivers"
7
8config EDD
9 tristate "BIOS Enhanced Disk Drive calls determine boot disk"
10 depends on X86
11 help
12 Say Y or M here if you want to enable BIOS Enhanced Disk Drive
13 Services real mode BIOS calls to determine which disk
14 BIOS tries boot from. This information is then exported via sysfs.
15
16 This option is experimental and is known to fail to boot on some
17 obscure configurations. Most disk controller BIOS vendors do
18 not yet implement this feature.
19
20config EDD_OFF
21 bool "Sets default behavior for EDD detection to off"
22 depends on EDD
23 default n
24 help
25 Say Y if you want EDD disabled by default, even though it is compiled into the
26 kernel. Say N if you want EDD enabled by default. EDD can be dynamically set
27 using the kernel parameter 'edd={on|skipmbr|off}'.
28
29config FIRMWARE_MEMMAP
30 bool "Add firmware-provided memory map to sysfs" if EXPERT
31 default X86
32 help
33 Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
34 That memory map is used for example by kexec to set up parameter area
35 for the next kernel, but can also be used for debugging purposes.
36
37 See also Documentation/ABI/testing/sysfs-firmware-memmap.
38
39config EFI_VARS
40 tristate "EFI Variable Support via sysfs"
41 depends on EFI
42 default n
43 help
44 If you say Y here, you are able to get EFI (Extensible Firmware
45 Interface) variable information via sysfs. You may read,
46 write, create, and destroy EFI variables through this interface.
47
48 Note that using this driver in concert with efibootmgr requires
49 at least test release version 0.5.0-test3 or later, which is
50 available from Matt Domsch's website located at:
51 <http://linux.dell.com/efibootmgr/testing/efibootmgr-0.5.0-test3.tar.gz>
52
53 Subsequent efibootmgr releases may be found at:
54 <http://linux.dell.com/efibootmgr>
55
56config EFI_PCDP
57 bool "Console device selection via EFI PCDP or HCDP table"
58 depends on ACPI && EFI && IA64
59 default y if IA64
60 help
61 If your firmware supplies the PCDP table, and you want to
62 automatically use the primary console device it describes
63 as the Linux console, say Y here.
64
65 If your firmware supplies the HCDP table, and you want to
66 use the first serial port it describes as the Linux console,
67 say Y here. If your EFI ConOut path contains only a UART
68 device, it will become the console automatically. Otherwise,
69 you must specify the "console=hcdp" kernel boot argument.
70
71 Neither the PCDP nor the HCDP affects naming of serial devices,
72 so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending
73 on how the driver discovers devices.
74
75 You must also enable the appropriate drivers (serial, VGA, etc.)
76
77 See DIG64_HCDPv20_042804.pdf available from
78 <http://www.dig64.org/specifications/>
79
80config DELL_RBU
81 tristate "BIOS update support for DELL systems via sysfs"
82 depends on X86
83 select FW_LOADER
84 help
85 Say m if you want to have the option of updating the BIOS for your
86 DELL system. Note you need a Dell OpenManage or Dell Update package (DUP)
87 supporting application to communicate with the BIOS regarding the new
88 image for the image update to take effect.
89 See <file:Documentation/dell_rbu.txt> for more details on the driver.
90
91config DCDBAS
92 tristate "Dell Systems Management Base Driver"
93 depends on X86
94 help
95 The Dell Systems Management Base Driver provides a sysfs interface
96 for systems management software to perform System Management
97 Interrupts (SMIs) and Host Control Actions (system power cycle or
98 power off after OS shutdown) on certain Dell systems.
99
100 See <file:Documentation/dcdbas.txt> for more details on the driver
101 and the Dell systems on which Dell systems management software makes
102 use of this driver.
103
104 Say Y or M here to enable the driver for use by Dell systems
105 management software such as Dell OpenManage.
106
107config DMIID
108 bool "Export DMI identification via sysfs to userspace"
109 depends on DMI
110 default y
111 help
112 Say Y here if you want to query SMBIOS/DMI system identification
113 information from userspace through /sys/class/dmi/id/ or if you want
114 DMI-based module auto-loading.
115
116config DMI_SYSFS
117 tristate "DMI table support in sysfs"
118 depends on SYSFS && DMI
119 default n
120 help
121 Say Y or M here to enable the exporting of the raw DMI table
122 data via sysfs. This is useful for consuming the data without
123 requiring any access to /dev/mem at all. Tables are found
124 under /sys/firmware/dmi when this option is enabled and
125 loaded.
126
127config ISCSI_IBFT_FIND
128 bool "iSCSI Boot Firmware Table Attributes"
129 depends on X86
130 default n
131 help
132 This option enables the kernel to find the region of memory
133 in which the ISCSI Boot Firmware Table (iBFT) resides. This
134 is necessary for iSCSI Boot Firmware Table Attributes module to work
135 properly.
136
137config ISCSI_IBFT
138 tristate "iSCSI Boot Firmware Table Attributes module"
139 select ISCSI_BOOT_SYSFS
140 depends on ISCSI_IBFT_FIND && SCSI && SCSI_LOWLEVEL
141 default n
142 help
143 This option enables support for detection and exposing of iSCSI
144 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
145 detect iSCSI boot parameters dynamically during system boot, say Y.
146 Otherwise, say N.
147
148config SIGMA
149 tristate "SigmaStudio firmware loader"
150 depends on I2C
151 select CRC32
152 default n
153 help
154 Enable helper functions for working with Analog Devices SigmaDSP
155 parts and binary firmwares produced by Analog Devices SigmaStudio.
156
157 If unsure, say N here. Drivers that need these helpers will select
158 this option automatically.
159
160source "drivers/firmware/google/Kconfig"
161
162endmenu
1#
2# For a description of the syntax of this configuration file,
3# see Documentation/kbuild/kconfig-language.txt.
4#
5
6menu "Firmware Drivers"
7
8config ARM_PSCI_FW
9 bool
10
11config ARM_SCPI_PROTOCOL
12 tristate "ARM System Control and Power Interface (SCPI) Message Protocol"
13 depends on ARM_MHU
14 help
15 System Control and Power Interface (SCPI) Message Protocol is
16 defined for the purpose of communication between the Application
17 Cores(AP) and the System Control Processor(SCP). The MHU peripheral
18 provides a mechanism for inter-processor communication between SCP
19 and AP.
20
21 SCP controls most of the power managament on the Application
22 Processors. It offers control and management of: the core/cluster
23 power states, various power domain DVFS including the core/cluster,
24 certain system clocks configuration, thermal sensors and many
25 others.
26
27 This protocol library provides interface for all the client drivers
28 making use of the features offered by the SCP.
29
30config EDD
31 tristate "BIOS Enhanced Disk Drive calls determine boot disk"
32 depends on X86
33 help
34 Say Y or M here if you want to enable BIOS Enhanced Disk Drive
35 Services real mode BIOS calls to determine which disk
36 BIOS tries boot from. This information is then exported via sysfs.
37
38 This option is experimental and is known to fail to boot on some
39 obscure configurations. Most disk controller BIOS vendors do
40 not yet implement this feature.
41
42config EDD_OFF
43 bool "Sets default behavior for EDD detection to off"
44 depends on EDD
45 default n
46 help
47 Say Y if you want EDD disabled by default, even though it is compiled into the
48 kernel. Say N if you want EDD enabled by default. EDD can be dynamically set
49 using the kernel parameter 'edd={on|skipmbr|off}'.
50
51config FIRMWARE_MEMMAP
52 bool "Add firmware-provided memory map to sysfs" if EXPERT
53 default X86
54 help
55 Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
56 That memory map is used for example by kexec to set up parameter area
57 for the next kernel, but can also be used for debugging purposes.
58
59 See also Documentation/ABI/testing/sysfs-firmware-memmap.
60
61config EFI_PCDP
62 bool "Console device selection via EFI PCDP or HCDP table"
63 depends on ACPI && EFI && IA64
64 default y if IA64
65 help
66 If your firmware supplies the PCDP table, and you want to
67 automatically use the primary console device it describes
68 as the Linux console, say Y here.
69
70 If your firmware supplies the HCDP table, and you want to
71 use the first serial port it describes as the Linux console,
72 say Y here. If your EFI ConOut path contains only a UART
73 device, it will become the console automatically. Otherwise,
74 you must specify the "console=hcdp" kernel boot argument.
75
76 Neither the PCDP nor the HCDP affects naming of serial devices,
77 so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending
78 on how the driver discovers devices.
79
80 You must also enable the appropriate drivers (serial, VGA, etc.)
81
82 See DIG64_HCDPv20_042804.pdf available from
83 <http://www.dig64.org/specifications/>
84
85config DELL_RBU
86 tristate "BIOS update support for DELL systems via sysfs"
87 depends on X86
88 select FW_LOADER
89 select FW_LOADER_USER_HELPER
90 help
91 Say m if you want to have the option of updating the BIOS for your
92 DELL system. Note you need a Dell OpenManage or Dell Update package (DUP)
93 supporting application to communicate with the BIOS regarding the new
94 image for the image update to take effect.
95 See <file:Documentation/dell_rbu.txt> for more details on the driver.
96
97config DCDBAS
98 tristate "Dell Systems Management Base Driver"
99 depends on X86
100 help
101 The Dell Systems Management Base Driver provides a sysfs interface
102 for systems management software to perform System Management
103 Interrupts (SMIs) and Host Control Actions (system power cycle or
104 power off after OS shutdown) on certain Dell systems.
105
106 See <file:Documentation/dcdbas.txt> for more details on the driver
107 and the Dell systems on which Dell systems management software makes
108 use of this driver.
109
110 Say Y or M here to enable the driver for use by Dell systems
111 management software such as Dell OpenManage.
112
113config DMIID
114 bool "Export DMI identification via sysfs to userspace"
115 depends on DMI
116 default y
117 help
118 Say Y here if you want to query SMBIOS/DMI system identification
119 information from userspace through /sys/class/dmi/id/ or if you want
120 DMI-based module auto-loading.
121
122config DMI_SYSFS
123 tristate "DMI table support in sysfs"
124 depends on SYSFS && DMI
125 default n
126 help
127 Say Y or M here to enable the exporting of the raw DMI table
128 data via sysfs. This is useful for consuming the data without
129 requiring any access to /dev/mem at all. Tables are found
130 under /sys/firmware/dmi when this option is enabled and
131 loaded.
132
133config DMI_SCAN_MACHINE_NON_EFI_FALLBACK
134 bool
135
136config ISCSI_IBFT_FIND
137 bool "iSCSI Boot Firmware Table Attributes"
138 depends on X86 && ACPI
139 default n
140 help
141 This option enables the kernel to find the region of memory
142 in which the ISCSI Boot Firmware Table (iBFT) resides. This
143 is necessary for iSCSI Boot Firmware Table Attributes module to work
144 properly.
145
146config ISCSI_IBFT
147 tristate "iSCSI Boot Firmware Table Attributes module"
148 select ISCSI_BOOT_SYSFS
149 depends on ISCSI_IBFT_FIND && SCSI && SCSI_LOWLEVEL
150 default n
151 help
152 This option enables support for detection and exposing of iSCSI
153 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
154 detect iSCSI boot parameters dynamically during system boot, say Y.
155 Otherwise, say N.
156
157config RASPBERRYPI_FIRMWARE
158 tristate "Raspberry Pi Firmware Driver"
159 depends on BCM2835_MBOX
160 help
161 This option enables support for communicating with the firmware on the
162 Raspberry Pi.
163
164config FW_CFG_SYSFS
165 tristate "QEMU fw_cfg device support in sysfs"
166 depends on SYSFS && (ARM || ARM64 || PPC_PMAC || SPARC || X86)
167 depends on HAS_IOPORT_MAP
168 default n
169 help
170 Say Y or M here to enable the exporting of the QEMU firmware
171 configuration (fw_cfg) file entries via sysfs. Entries are
172 found under /sys/firmware/fw_cfg when this option is enabled
173 and loaded.
174
175config FW_CFG_SYSFS_CMDLINE
176 bool "QEMU fw_cfg device parameter parsing"
177 depends on FW_CFG_SYSFS
178 help
179 Allow the qemu_fw_cfg device to be initialized via the kernel
180 command line or using a module parameter.
181 WARNING: Using incorrect parameters (base address in particular)
182 may crash your system.
183
184config QCOM_SCM
185 bool
186 depends on ARM || ARM64
187
188config QCOM_SCM_32
189 def_bool y
190 depends on QCOM_SCM && ARM
191
192config QCOM_SCM_64
193 def_bool y
194 depends on QCOM_SCM && ARM64
195
196config HAVE_ARM_SMCCC
197 bool
198
199source "drivers/firmware/broadcom/Kconfig"
200source "drivers/firmware/google/Kconfig"
201source "drivers/firmware/efi/Kconfig"
202
203endmenu