Home
last modified time | relevance | path

Searched refs:SMCCC (Results 1 – 19 of 19) sorted by relevance

/openbmc/linux/drivers/firmware/smccc/
H A DKconfig13 SMCCC v1.0 lacked discoverability and hence PSCI v1.0 was updated
14 to add SMCCC discovery mechanism though the PSCI firmware
16 success on firmware compliant to SMCCC v1.1 and above.
19 bool "SoC bus device for the ARM SMCCC SOC_ID"
24 Include support for the SoC bus on the ARM SMCCC firmware based
/openbmc/u-boot/arch/arm/cpu/armv8/
H A Dsmccc-call.S13 .macro SMCCC instr macro
36 SMCCC smc
46 SMCCC hvc
/openbmc/u-boot/arch/arm/cpu/armv7/
H A Dsmccc-call.S27 .macro SMCCC instr macro
48 SMCCC SMCCC_SMC
58 SMCCC SMCCC_HVC
/openbmc/linux/arch/arm/kernel/
H A Dsmccc-call.S25 .macro SMCCC instr macro
53 SMCCC SMCCC_SMC
63 SMCCC SMCCC_HVC
/openbmc/linux/arch/arm64/kernel/
H A Dsmccc-call.S11 .macro SMCCC instr macro
32 SMCCC smc
43 SMCCC hvc
/openbmc/u-boot/doc/
H A DREADME.tee51 Convention (SMCCC) [2], which is the foundation for OP-TEE's SMC interface
55 OP-TEE SMC interface provides the basic functions required by SMCCC and some
58 - OPTEE_SMC_FUNCID_CALLS_UID (part of SMCCC) returns the version information
93 | SMCCC (OPTEE_SMC_CALL_*) |
97 An RPC is identified by a special range of SMCCC return values from
/openbmc/linux/Documentation/virt/kvm/devices/
H A Dvm.rst343 representation of the SMCCC filter
346 Requests the installation of an SMCCC call filter described as follows::
362 range defines an action to be applied to SMCCC calls within the range.
366 The default configuration of KVM is such that all implemented SMCCC
367 calls are allowed. Thus, the SMCCC filter can be defined sparsely
374 The SMCCC filter applies to both SMC and HVC calls initiated by the
375 guest. The SMCCC filter gates the in-kernel emulation of SMCCC calls
377 SMCCC calls (e.g. hypercall bitmap registers).
381 - ``KVM_SMCCC_FILTER_HANDLE``: Allows the guest SMCCC call to be
383 explicitly describe the allowed SMCCC call ranges.
[all …]
/openbmc/linux/Documentation/virt/kvm/arm/
H A Dpvtime.rst15 Two new SMCCC compatible hypercalls are defined:
22 the PV_TIME_FEATURES hypercall should be probed using the SMCCC 1.1
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-devices-soc29 On many of ARM based silicon with SMCCC v1.2+ compliant firmware
67 On many of ARM based silicon with SMCCC v1.2+ compliant firmware
/openbmc/linux/Documentation/staging/
H A Dtee.rst127 Convention (SMCCC) [2], which is the foundation for OP-TEE's SMC interface
131 OP-TEE SMC interface provides the basic functions required by SMCCC and some
134 - OPTEE_SMC_FUNCID_CALLS_UID (part of SMCCC) returns the version information
169 | IOCTL (TEE_IOC_*) | | SMCCC (OPTEE_SMC_CALL_*) |
173 or tee-supplicant. An RPC is identified by a special range of SMCCC return
/openbmc/linux/Documentation/driver-api/firmware/
H A Dother_interfaces.rst32 and processed one by one. ARM’s SMCCC is used to pass the execution
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/u-boot/u-boot/corstone1000/
H A D0043-firmware-psci-Fix-bind_smccc_features-psci-check.patch10 whether the SMCCC is implemented by discovering SMCCC_VERSION.
H A D0001-FF-A-v15-arm64-smccc-add-support-for-SMCCCv1.2-x0-x1.patch9 In SMCCC v1.2 [1] arguments are passed in registers x1-x17.
49 SMCCC hvc
H A D0004-FF-A-v15-arm_ffa-introduce-Arm-FF-A-support.patch14 on top of the SMCCC layer. The driver provides the FF-A ABIs needed for
271 +FF-A support comes on top of the SMCCC layer and is implemented by the FF-A Uclass drivers/firmwar…
373 the PSCI driver is always probed and binds dirvers registered to the Arm SMCCC
374 services if any and reported as supported by the SMCCC firmware.
1572 + * The FF-A driver is registered as an SMCCC feature driver. So, features discovery
1573 + * callbacks are called by the PSCI driver (PSCI device is the SMCCC features
1600 +/* Registering the FF-A driver as an SMCCC feature driver */
1884 +/* Providing Arm SMCCC declarations to sandbox */
/openbmc/linux/drivers/char/hw_random/
H A DKconfig542 tristate "Arm SMCCC TRNG firmware interface support"
547 the Arm SMCCC TRNG firmware interface. This reads entropy from
548 higher exception levels (firmware, hypervisor). Uses SMCCC for
/openbmc/linux/Documentation/virt/hyperv/
H A Doverview.rst33 sequence. On arm64, hypercalls use the ARM standard SMCCC calling
/openbmc/u-boot/arch/arm/
H A DKconfig321 bool "Support for ARM SMC Calling Convention (SMCCC)"
327 firmware (for example, PSCI) according to SMCCC.
/openbmc/linux/Documentation/virt/kvm/
H A Dapi.rst6275 SMCCC exits can be enabled depending on the configuration of the SMCCC
6279 ``nr`` contains the function ID of the guest's SMCCC call. Userspace is
6285 conduit to initiate the SMCCC call. If this bit is 0 then the guest
6286 used the HVC conduit for the SMCCC call.
6289 instruction to initiate the SMCCC call. If this bit is 0 then the
/openbmc/linux/
H A DMAINTAINERS19337 SECURE MONITOR CALL(SMC) CALLING CONVENTION (SMCCC)