Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # For a description of the syntax of this configuration file, | |
3 | # see Documentation/kbuild/kconfig-language.txt. | |
4 | # | |
5 | ||
6 | menu "Firmware Drivers" | |
7 | ||
bff60792 MR |
8 | config ARM_PSCI_FW |
9 | bool | |
10 | ||
8cb7cf56 SH |
11 | config 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 | ||
1da177e4 | 30 | config EDD |
5d18639a | 31 | tristate "BIOS Enhanced Disk Drive calls determine boot disk" |
9b6e3e42 | 32 | depends on X86 |
1da177e4 LT |
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 | ||
8c4dd606 TG |
42 | config 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 | ||
69ac9cd6 | 51 | config FIRMWARE_MEMMAP |
6a108a14 | 52 | bool "Add firmware-provided memory map to sysfs" if EXPERT |
9b6e3e42 | 53 | default X86 |
69ac9cd6 BW |
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 | ||
1da177e4 LT |
61 | config 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 | ||
631dd1a8 JM |
82 | See DIG64_HCDPv20_042804.pdf available from |
83 | <http://www.dig64.org/specifications/> | |
1da177e4 | 84 | |
6c54c28e AS |
85 | config DELL_RBU |
86 | tristate "BIOS update support for DELL systems via sysfs" | |
6c52f137 | 87 | depends on X86 |
6c54c28e | 88 | select FW_LOADER |
d05c39ea | 89 | select FW_LOADER_USER_HELPER |
6c54c28e AS |
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) | |
09509603 | 93 | supporting application to communicate with the BIOS regarding the new |
6c54c28e AS |
94 | image for the image update to take effect. |
95 | See <file:Documentation/dell_rbu.txt> for more details on the driver. | |
90563ec4 DW |
96 | |
97 | config DCDBAS | |
98 | tristate "Dell Systems Management Base Driver" | |
0d078f6f | 99 | depends on X86 |
90563ec4 DW |
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 | ||
4f5c791a LP |
113 | config 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 | ||
948af1f0 MW |
122 | config 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 | ||
cf074402 AB |
133 | config DMI_SCAN_MACHINE_NON_EFI_FALLBACK |
134 | bool | |
135 | ||
138fe4e0 KR |
136 | config ISCSI_IBFT_FIND |
137 | bool "iSCSI Boot Firmware Table Attributes" | |
9d24622c | 138 | depends on X86 && ACPI |
138fe4e0 KR |
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 | ||
146 | config ISCSI_IBFT | |
147 | tristate "iSCSI Boot Firmware Table Attributes module" | |
b33a84a3 | 148 | select ISCSI_BOOT_SYSFS |
3e0f686e | 149 | depends on ISCSI_IBFT_FIND && SCSI && SCSI_LOWLEVEL |
138fe4e0 KR |
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 | ||
4e3d6065 EA |
157 | config 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 | ||
916f743d KG |
164 | config QCOM_SCM |
165 | bool | |
166 | depends on ARM || ARM64 | |
167 | ||
50b956f3 AG |
168 | config QCOM_SCM_32 |
169 | def_bool y | |
170 | depends on QCOM_SCM && ARM | |
171 | ||
172 | config QCOM_SCM_64 | |
173 | def_bool y | |
174 | depends on QCOM_SCM && ARM64 | |
175 | ||
98dd64f3 JW |
176 | config HAVE_ARM_SMCCC |
177 | bool | |
178 | ||
f6e734a8 | 179 | source "drivers/firmware/broadcom/Kconfig" |
74c5b31c | 180 | source "drivers/firmware/google/Kconfig" |
04851772 | 181 | source "drivers/firmware/efi/Kconfig" |
74c5b31c | 182 | |
1da177e4 | 183 | endmenu |