Home
last modified time | relevance | path

Searched refs:vendor (Results 1 – 14 of 14) sorted by relevance

/trusted-firmware-a-3.7.0/plat/socionext/synquacer/
Dplatform.mk33 -Idrivers/arm/css/scmi/vendor
105 drivers/arm/css/scmi/vendor/scmi_sq.c \
/trusted-firmware-a-3.7.0/include/drivers/
Draw_nand.h157 uint8_t vendor[88]; member
/trusted-firmware-a-3.7.0/plat/st/stm32mp1/
Dstm32mp1_scmi.c181 static const char vendor[] = "ST"; variable
186 return vendor; in plat_scmi_vendor_name()
/trusted-firmware-a-3.7.0/include/drivers/brcm/emmc/
Demmc_chal_sd.h139 uint32_t vendor; /* vendor number */ member
/trusted-firmware-a-3.7.0/docs/security_advisories/
Dsecurity-advisory-tfv-9.rst118 For more information about non-Arm CPUs, please contact the CPU vendor.
Dsecurity-advisory-tfv-7.rst38 vendor-supplied interfaces. Therefore, the TF-A project takes a conservative
Dsecurity-advisory-tfv-6.rst125 For more information about non-Arm CPUs, please contact the CPU vendor.
/trusted-firmware-a-3.7.0/docs/process/
Dcoding-guidelines.rst250 Trusted Boot vendor may provide the BL2 image, a TEE vendor may provide the BL32
251 image and the OEM/SoC vendor may provide the other images).
Dcontributing.rst287 - Only platform port code (i.e. in the ``plat/<vendor>`` directory) may rely on
/trusted-firmware-a-3.7.0/docs/getting_started/
Dimage-terminology.rst101 abbreviated name should identify the vendor as well as the image
/trusted-firmware-a-3.7.0/docs/design_documents/
Dpsci_osi_mode.rst87 Current vendor implementations and workarounds
/trusted-firmware-a-3.7.0/docs/components/
Dsecure-partition-manager.rst335 SPs may be signed by different parties (SiP, OEM/ODM, TOS vendor, etc.).
/trusted-firmware-a-3.7.0/docs/
Dporting-guide.rst2936 and vendor reset can return other PSCI error codes as defined
Dchange-log.md2298 …- extend SiP vendor subscription events ([99d30b7](https://review.trustedfirmware.org/plugins/giti…