Home
last modified time | relevance | path

Searched refs:interface (Results 1 – 25 of 57) sorted by relevance

123

/rk3399_ARM-atf/docs/resources/diagrams/plantuml/
H A Dio_arm_class_diagram.puml72 .. io_dev_funcs_t interface ..
78 .. io_dev_funcs_t interface ..
82 interface io_driver {
86 .. io_dev_connector_t interface ..
89 .. io_dev_funcs_t interface ..
/rk3399_ARM-atf/docs/process/
H A Dplatform-ports-policy.rst16 platform compatibility, which means the previous interface needs to be deprecated
17 and a new interface introduced to replace it. In case the migration to the new
18 interface is trivial, the contributor of the change is expected to make good
19 effort to migrate the upstream platforms to the new interface.
27 the release after which each one will be removed. When an interface is
29 interface will be removed. This must be at least 1 full release cycle in future.
30 For non-trivial interface changes, an email should be sent out to the `TF-A
33 the deprecated interface.
38 If a platform, driver or library interface is no longer maintained, it is best
/rk3399_ARM-atf/docs/threat_model/firmware_threat_model/
H A Dthreat_model_rse_interface.rst1 Threat Model for RSE - AP interface
14 The scope of this threat model only includes the interface between the RSE and
23 it includes the RSE and highlights the interface between the AP and the RSE
24 cores. The interface description only focuses on the AP-RSE interface the rest
47 - ID 11: The access to the communication interface between AP and RSE is
49 interface to NSCode can allow malicious code to interact with RSE and
H A Dthreat_model.rst73 | | informative messages over a UART interface. |
75 | | | Also, characters can be read from a UART interface. |
81 | | with TF-A through SMC call interface and/or shared |
85 | | with TF-A through SMC call interface and/or shared |
371 | | debug and trace interface** |
492 | | interface** |
582 | | a UART interface may allow an attacker to tamper |
624 | | UART interface(s). |
940 its on-chip memory. |HES| interface is available for BL1 and BL2.
1155 | | debug interface signals, i.e. Secure world event |
H A Dthreat_model_arm_cca.rst113 | | TF-A through SMC call interface and/or shared |
155 | | | code or access otherwise restricted HW interface. |
/rk3399_ARM-atf/drivers/tpm/
H A Dtpm2_cmds.c19 static struct interface_ops *interface; variable
25 ret = interface->send(chip_data, send); in tpm_xfer()
30 ret = interface->receive(chip_data, receive); in tpm_xfer()
42 interface = tpm_interface_getops(chip_data, locality); in tpm_interface_init()
44 err = interface->request_access(chip_data, locality); in tpm_interface_init()
49 return interface->get_info(chip_data, locality); in tpm_interface_init()
54 return interface->release_locality(chip_data, locality); in tpm_interface_close()
/rk3399_ARM-atf/docs/design_documents/
H A Ddtpm_drivers.rst13 When a Discrete TPM interface is implemented correctly, the risk of software
23 Platforms opt to use a specific messaging interface, such as |CRB| or |FIFO|,
24 and a specific hardware bus interface, such as |I2C| or |SPI|.
34 TPM interface, perform a TPM startup, set up a locality for operations like
37 via a specific TPM interface like FIFO or CRB. It also includes functions
39 tailored to the specific interface.
41 device. The link layer maps the command passed from the interface layer to
43 that use the platform bus interface to transfer commands.
49 The command, interface, and link layers are implemented in common code in
75 on the selected TPM interface, the appropriate drivers will be built and
[all …]
H A Dmeasured_boot_dtpm_poc.rst16 that showcases the use of Measured Boot with a Discrete TPM interface.
20 show how Measured Boot on TF-A can interact with a Discrete TPM interface.
22 Raspberry Pi communicates with the TPM via a GPIO pin bit-banged SPI interface.
23 For other platforms, different may be required to interface with the hardware
31 driver development and the availability of GPIO pins to interface with a TPM
48 - **TF-A TPM Drivers**: To interface with a physical (Discrete) TPM chip in
49 TF-A, the PoC uses TF-A drivers that provide the command, interface, link,
141 - ``TPM_INTERFACE=FIFO_SPI`` specifies the use of the FIFO SPI interface.
H A Drse.rst42 to each other. An MHU interface consists of two pairs of MHUs, one sender and
44 interface. One pair provides message sending from AP to RSE and the other pair
439 it on behalf of RMM. The access to MHU interface and thereby to RSE is
687 clients with an interface to send DICE commands, encoded as CBOR objects,
748 AP/RSE interface for retrieving and incrementing non-volatile counters API is
772 AP/RSE interface for reading the ROTPK is as follows.
793 AP/RSE interface for reading the entropy is as follows.
/rk3399_ARM-atf/docs/components/
H A Ddebugfs-design.rst18 interface (`Notes on the Plan 9 Kernel Source`_ and
30 9p interface
67 This interface is embedded into the BL31 run-time payload when selected by build
68 options. The interface multiplexes drivers or emulated "files":
77 SMC interface
84 for a description of the SMC interface.
97 - In order to setup the shared buffer, the component consuming the interface
112 The SMC interface is accessible from an NS environment, that is:
H A Dven-el3-debugfs.rst1 DebugFS interface
4 The optional DebugFS interface is accessed through a Vendor specific EL3 service. Refer
315 Returns the debugfs interface version if implemented in TF-A.
331 w0 == SMC_UNK if interface is not implemented
333 uint32_t w1: On success, debugfs interface version, 32 bits
H A Dven-el3-service.rst80 DebugFS interface
83 The optional DebugFS interface is accessed through Vendor specific EL3 service. Refer
84 to :ref:`DebugFS interface` documentation for further details and usage.
H A Drmm-el3-comms-spec.rst1 RMM-EL3 Communication interface
4 This document defines the communication interface between RMM and EL3.
5 There are two parts in this interface: the boot interface and the runtime
6 interface.
9 R-EL2 for the first time after boot. The cold boot interface defines the ABI
10 for the cold boot path and the warm boot interface defines the same for the
13 The RMM-EL3 runtime interface defines the ABI for EL3 services which can be
26 RMM-EL3 runtime interface.
178 warm boot by any PE should not enter RMM using the warm boot interface.
217 This section defines the RMM-EL3 runtime interface which specifies the ABI for
[all …]
H A Dsecure-partition-manager-mm.rst10 (MM) interface.
33 other interfaces (e.g. ACPI TCG TPM interface, UEFI runtime variable service).
84 - Implement a standard interface that is used for initialising a Secure
89 - Implement a standard interface that is used by a Secure Partition to fulfil
92 - Implement a standard interface that is used by the Non-secure world for
149 TF-A exports a porting interface that enables a platform to specify the system
151 However, this interface is under development and it may change as new features
182 interface defined in the `Management Mode Interface Specification`_ (*Arm DEN
304 corresponding interface.
309 The Secure Partition provides an Event Management interface that is used by the
[all …]
H A Del3-spmc.rst320 This is a mandatory interface for secure partitions participating in direct request
337 FFA_ID_GET interface, and records it. The SPMC can also query the SPMD ID using
338 the FFA_SPM_ID_GET interface at the secure physical FF-A instance.
340 Secure partitions call this interface at the virtual FF-A instance, to which
396 The FFA_SECONDARY_EP_REGISTER interface is to be used by a secure partition
428 - the FFA_MSG_SEND_DIRECT_REQ interface.
429 - the FFA_RUN interface.
467 - Interrupt is forwarded to SP using FFA_INTERRUPT interface.
470 SPMC using FFA_MSG_WAIT interface.
H A Dfirmware-update.rst11 IHI 0093), which defines a standard firmware interface for installing firmware
148 #. Export a BL1 SMC interface to interoperate with other FWU images executing
150 #. Export a platform interface to provide FWU common code with the information
152 :ref:`Porting Guide` for details of this interface.
/rk3399_ARM-atf/docs/security_advisories/
H A Dsecurity-advisory-tfv-2.rst5 | Title | Enabled secure self-hosted invasive debug interface can |
44 interface. Therefore this issue only exists for AArch32 Secure EL1 code when
45 secure privileged invasive debug is enabled by the authentication interface, at
H A Dsecurity-advisory-tfv-1.rst26 Generic Trusted Firmware (TF) BL1 code contains an SMC interface that is briefly
31 example, BL31 on AArch64 systems), the FWU SMC interface is replaced by the EL3
32 Runtime SMC interface. Platforms may choose how much of this FWU functionality
/rk3399_ARM-atf/plat/arm/board/tc/
H A Dplatform_test.mk90 PLAT_INCLUDES += -I$(TF_M_EXTRAS_PATH)/partitions/measured_boot/interface/include \
91 -I$(TF_M_EXTRAS_PATH)/partitions/delegated_attestation/interface/include \
/rk3399_ARM-atf/drivers/arm/tzc/
H A Dtzc_dmc500.c54 #define DMC_INST_SI_BASE(instance, interface) \ argument
55 (DMC_INST_BASE_ADDR(instance) + IFACE_OFFSET(interface))
/rk3399_ARM-atf/plat/st/common/include/
H A Dstm32mp_common.h134 void stm32_get_boot_interface(uint32_t *interface, uint32_t *instance);
/rk3399_ARM-atf/plat/st/common/
H A Dstm32mp_common.c397 void stm32_get_boot_interface(uint32_t *interface, uint32_t *instance) in stm32_get_boot_interface() argument
410 *interface = (itf & BOOT_ITF_MASK) >> BOOT_ITF_SHIFT; in stm32_get_boot_interface()
/rk3399_ARM-atf/
H A Dreadme.rst10 TF-A implements Arm interface standards, including:
/rk3399_ARM-atf/docs/about/
H A Dfeatures.rst37 - A generic |SCMI| driver to interface with conforming power controllers, for
100 - Support for Errata management firmware interface.
/rk3399_ARM-atf/docs/plat/
H A Drcar-gen3.rst52 SD card host interface,
74 BL2 initializes DDR (and on some platforms i2c to interface to the

123