1# SPDX-License-Identifier: GPL-2.0-only 2# 3# For a description of the syntax of this configuration file, 4# see Documentation/kbuild/kconfig-language.rst. 5# 6 7menu "Qualcomm firmware drivers" 8 9config QCOM_SCM 10 select QCOM_TZMEM 11 tristate 12 13config QCOM_TZMEM 14 tristate 15 select GENERIC_ALLOCATOR 16 17choice 18 prompt "TrustZone interface memory allocator mode" 19 default QCOM_TZMEM_MODE_GENERIC 20 help 21 Selects the mode of the memory allocator providing memory buffers of 22 suitable format for sharing with the TrustZone. If in doubt, select 23 'Generic'. 24 25config QCOM_TZMEM_MODE_GENERIC 26 bool "Generic" 27 help 28 Use the generic allocator mode. The memory is page-aligned, non-cachable 29 and physically contiguous. 30 31endchoice 32 33config QCOM_SCM_DOWNLOAD_MODE_DEFAULT 34 bool "Qualcomm download mode enabled by default" 35 depends on QCOM_SCM 36 help 37 A device with "download mode" enabled will upon an unexpected 38 warm-restart enter a special debug mode that allows the user to 39 "download" memory content over USB for offline postmortem analysis. 40 The feature can be enabled/disabled on the kernel command line. 41 42 Say Y here to enable "download mode" by default. 43 44config QCOM_QSEECOM 45 bool "Qualcomm QSEECOM interface driver" 46 depends on QCOM_SCM=y 47 select AUXILIARY_BUS 48 help 49 Various Qualcomm SoCs have a Secure Execution Environment (SEE) running 50 in the Trust Zone. This module provides an interface to that via the 51 QSEECOM mechanism, using SCM calls. 52 53 The QSEECOM interface allows, among other things, access to applications 54 running in the SEE. An example of such an application is 'uefisecapp', 55 which is required to access UEFI variables on certain systems. If 56 selected, the interface will also attempt to detect and register client 57 devices for supported applications. 58 59 Select Y here to enable the QSEECOM interface driver. 60 61config QCOM_QSEECOM_UEFISECAPP 62 bool "Qualcomm SEE UEFI Secure App client driver" 63 depends on QCOM_QSEECOM 64 depends on EFI 65 help 66 Various Qualcomm SoCs do not allow direct access to EFI variables. 67 Instead, these need to be accessed via the UEFI Secure Application 68 (uefisecapp), residing in the Secure Execution Environment (SEE). 69 70 This module provides a client driver for uefisecapp, installing efivar 71 operations to allow the kernel accessing EFI variables, and via that also 72 provide user-space with access to EFI variables via efivarfs. 73 74 Select Y here to provide access to EFI variables on the aforementioned 75 platforms. 76 77endmenu 78