Gitiles
Code Review Sign In
gerrit-public.fairphone.software / kernel / msm-4.9 / d9734e0d1ccf87e828ad172c58a96dff97cfc0ba / . / drivers / firmware / efi / Kconfig
blob: e1670d533f9742e94b505ba0684d9373956c8bb0 [file] [log] [blame]
Matt Fleming04851772013-02-08 15:48:51 +0000[diff] [blame]1menu "EFI (Extensible Firmware Interface) Support"
2 depends on EFI
3
4config EFI_VARS
5 tristate "EFI Variable Support via sysfs"
6 depends on EFI
7 default n
8 help
9 If you say Y here, you are able to get EFI (Extensible Firmware
10 Interface) variable information via sysfs. You may read,
11 write, create, and destroy EFI variables through this interface.
12
13 Note that using this driver in concert with efibootmgr requires
14 at least test release version 0.5.0-test3 or later, which is
Peter Jones0e4ca022014-12-09 16:14:11 -0500[diff] [blame]15 available from:
Matt Fleming04851772013-02-08 15:48:51 +0000[diff] [blame]16 <http://linux.dell.com/efibootmgr/testing/efibootmgr-0.5.0-test3.tar.gz>
17
18 Subsequent efibootmgr releases may be found at:
Peter Jones0e4ca022014-12-09 16:14:11 -0500[diff] [blame]19 <http://github.com/vathpela/efibootmgr>
Matt Fleming04851772013-02-08 15:48:51 +0000[diff] [blame]20
Peter Jones3846c152015-06-05 15:14:54 -0400[diff] [blame]21config EFI_ESRT
22 bool
23 depends on EFI && !IA64
24 default y
25
Matt Fleming04851772013-02-08 15:48:51 +0000[diff] [blame]26config EFI_VARS_PSTORE
27 tristate "Register efivars backend for pstore"
28 depends on EFI_VARS && PSTORE
29 default y
30 help
31 Say Y here to enable use efivars as a backend to pstore. This
32 will allow writing console messages, crash dumps, or anything
33 else supported by pstore to EFI variables.
34
35config EFI_VARS_PSTORE_DEFAULT_DISABLE
36 bool "Disable using efivars as a pstore backend by default"
37 depends on EFI_VARS_PSTORE
38 default n
39 help
40 Saying Y here will disable the use of efivars as a storage
41 backend for pstore by default. This setting can be overridden
42 using the efivars module's pstore_disable parameter.
43
Dave Young926172d2013-12-20 18:02:18 +0800[diff] [blame]44config EFI_RUNTIME_MAP
45 bool "Export efi runtime maps to sysfs"
Dave Young2965faa2015-09-09 15:38:55 -0700[diff] [blame]46 depends on X86 && EFI && KEXEC_CORE
Dave Young926172d2013-12-20 18:02:18 +0800[diff] [blame]47 default y
48 help
49 Export efi runtime memory maps to /sys/firmware/efi/runtime-map.
50 That memory map is used for example by kexec to set up efi virtual
51 mapping the 2nd kernel, but can also be used for debugging purposes.
52
53 See also Documentation/ABI/testing/sysfs-firmware-efi-runtime-map.
54
Taku Izumi0f96a992015-09-30 23:01:56 +0900[diff] [blame]55config EFI_FAKE_MEMMAP
56 bool "Enable EFI fake memory map"
57 depends on EFI && X86
58 default n
59 help
60 Saying Y here will enable "efi_fake_mem" boot option.
61 By specifying this parameter, you can add arbitrary attribute
62 to specific memory range by updating original (firmware provided)
63 EFI memmap.
64 This is useful for debugging of EFI memmap related feature.
65 e.g. Address Range Mirroring feature.
66
67config EFI_MAX_FAKE_MEM
68 int "maximum allowable number of ranges in efi_fake_mem boot option"
69 depends on EFI_FAKE_MEMMAP
70 range 1 128
71 default 8
72 help
73 Maximum allowable number of ranges in efi_fake_mem boot option.
74 Ranges can be set up to this value using comma-separated list.
75 The default value is 8.
76
Mark Salter0302f712013-12-30 12:12:12 -0500[diff] [blame]77config EFI_PARAMS_FROM_FDT
78 bool
79 help
80 Select this config option from the architecture Kconfig if
81 the EFI runtime support gets system table address, memory
82 map address, and other parameters from the device tree.
83
Ard Biesheuvel022ee6c2014-06-26 12:09:05 +0200[diff] [blame]84config EFI_RUNTIME_WRAPPERS
85 bool
86
Ard Biesheuvelf4f75ad52014-07-02 14:54:43 +0200[diff] [blame]87config EFI_ARMSTUB
88 bool
89
Matt Fleming04851772013-02-08 15:48:51 +0000[diff] [blame]90endmenu
Jan Beulichfce7d3b2013-12-16 14:39:40 +0000[diff] [blame]91
92config UEFI_CPER
93 bool