78 lines · plain
1# SPDX-License-Identifier: GPL-2.0-only2#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_SCM10 select QCOM_TZMEM11 tristate12 13config QCOM_TZMEM14 tristate15 select GENERIC_ALLOCATOR16 17choice18 prompt "TrustZone interface memory allocator mode"19 depends on QCOM_TZMEM20 default QCOM_TZMEM_MODE_GENERIC21 help22 Selects the mode of the memory allocator providing memory buffers of23 suitable format for sharing with the TrustZone. If in doubt, select24 'Generic'.25 26config QCOM_TZMEM_MODE_GENERIC27 bool "Generic"28 help29 Use the generic allocator mode. The memory is page-aligned, non-cachable30 and physically contiguous.31 32config QCOM_TZMEM_MODE_SHMBRIDGE33 bool "SHM Bridge"34 help35 Use Qualcomm Shared Memory Bridge. The memory has the same alignment as36 in the 'Generic' allocator but is also explicitly marked as an SHM Bridge37 buffer.38 39 With this selected, all buffers passed to the TrustZone must be allocated40 using the TZMem allocator or else the TrustZone will refuse to use them.41 42endchoice43 44config QCOM_QSEECOM45 bool "Qualcomm QSEECOM interface driver"46 depends on QCOM_SCM=y47 select AUXILIARY_BUS48 help49 Various Qualcomm SoCs have a Secure Execution Environment (SEE) running50 in the Trust Zone. This module provides an interface to that via the51 QSEECOM mechanism, using SCM calls.52 53 The QSEECOM interface allows, among other things, access to applications54 running in the SEE. An example of such an application is 'uefisecapp',55 which is required to access UEFI variables on certain systems. If56 selected, the interface will also attempt to detect and register client57 devices for supported applications.58 59 Select Y here to enable the QSEECOM interface driver.60 61config QCOM_QSEECOM_UEFISECAPP62 bool "Qualcomm SEE UEFI Secure App client driver"63 depends on QCOM_QSEECOM64 depends on EFI65 help66 Various Qualcomm SoCs do not allow direct access to EFI variables.67 Instead, these need to be accessed via the UEFI Secure Application68 (uefisecapp), residing in the Secure Execution Environment (SEE).69 70 This module provides a client driver for uefisecapp, installing efivar71 operations to allow the kernel accessing EFI variables, and via that also72 provide user-space with access to EFI variables via efivarfs.73 74 Select Y here to provide access to EFI variables on the aforementioned75 platforms.76 77endmenu78