Home
last modified time | relevance | path

Searched full:trusted (Results 1 – 25 of 378) sorted by relevance

12345678910>>...16

/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/
H A DTrustedComponent.v1_4_0.json58 …software inventory resource that represents the active firmware image for this trusted component.",
59 …of type `SoftwareInventory` that represents the active firmware image for this trusted component.",
63 …ption": "An array of links to ComponentIntegrity resources for which the trusted component is resp…
67 … trusted component by other resources. The `TargetComponentURI` property in the referenced `Compo…
79 … an array of links to resources whose integrity is measured or reported by the trusted component.",
88 … "description": "A link to a resource to which this trusted component is integrated.",
89 …iption": "This property shall contain a link to a resource to which this trusted component is phys…
106 "description": "A link to the resource that owns this trusted component.",
107 …ion": "This property shall contain a link to the resource that owns this trusted component. In th…
112 "description": "The images that are associated with this trusted component.",
[all …]
/openbmc/openbmc/meta-arm/documentation/
H A Dtrusted-services.md1 # The Trusted Services: framework for developing root-of-trust services
3 meta-arm layer includes recipes for [Trusted Services][^1] Secure Partitions and Normal World appli…
4 in `meta-arm/recipes-security/trusted-services`
8 We define dedicated recipes for all supported Trusted Services (TS) Secure Partitions.
43 3. trusted-firmware-a might require platform specific TF-A build parameters (SPD and SPMC details o…
44 …See `meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend` for qemuarm64-securebo…
45 …and in `meta-arm-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a-corstone1000.inc` for theCo…
47 4. Trusted Services supports an SPMC agonistic binary format. To build SPs to this format the `TS_E…
54 [Trusted Services test and demo tools][^3] and [xtest][^4] configured to include the `ffa_spmc` tes…
56 ## OEQA Trusted Services tests
[all …]
H A Dquick-start.md44 If, as an example, we’re wanting to develop trusted-firmware-a; then fvp-base will work for us. 
55 …ware being used on the machine above (in the above example, this will be trusted-firmware-a for fv…
58 $ devtool modify trusted-firmware-a
61 …d print a path at the end where the source code was checked out.  In the trusted-firmware-a exampl…
63 > /builder/meta-arm/build/workspace/sources/trusted-firmware-a
70 $ devtool build trusted-firmware-a
88 $ mv 0001-example.patch ~/meta-arm/meta-arm/recipes-bsp/trusted-firmware-a/files/
90 $ devtool reset trusted-firmware-a
91 …:append = " file://0001-example.patch" >> meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware…
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Item/
H A DTrustedComponent.interface.yaml2 Interface to query trusted component info.
11 The type of trusted component, such as any physical distinction about
12 the trusted component.
19 object that the trusted component is reported by.
36 The type of trusted component, such as any physical distinction about
37 the trusted component.
41 A discrete trusted component. It is "discrete" when basic
46 An integrated trusted component.
/openbmc/bmcweb/redfish-core/schema/dmtf/csdl/
H A DTrustedComponent_v1.xml45 …"OData.Description" String="The `TrustedComponent` resource represents a trusted device, such as a…
46 …<Annotation Term="OData.LongDescription" String="This resource shall represent a trusted component…
96 <Annotation Term="OData.Description" String="The UUID for this trusted component."/>
97 …g="This property shall contain a universally unique identifier number for the trusted component."/>
105 …m="OData.Description" String="The type of trusted component, such as any physical distinction abou…
106 … Term="OData.LongDescription" String="This property shall contain the type of trusted component."/>
111 …tion" String="The link to a collection of device identity certificates of the trusted component."/>
112 …ype `CertificateCollection` that contains device identity certificates of the trusted component."/>
121 … <Annotation Term="OData.Description" String="The manufacturer of this trusted component."/>
122 …ization responsible for producing the trusted component. This organization may be the entity from…
[all …]
/openbmc/phosphor-fan-presence/monitor/
H A Dtrust_manager.hpp21 * reading can be trusted or not, based on the trust groups the sensor
64 * Checks if a sensor value can be trusted
66 * Checks if the sensor is trusted in each group
67 * it belongs to. Only considered trusted if it is
68 * trusted in all groups it belongs to.
78 * make one group change to trusted and another to untrusted.
82 * @return bool - if sensor is trusted in all groups or not
86 auto trusted = true; in checkTrust() local
97 trusted = false; in checkTrust()
114 return trusted; in checkTrust()
H A Dnonzero_speed_trust.hpp15 * A trust group where the sensors in the group are trusted as long
17 * have a speed of zero, then no sensor in the group is trusted.
41 * Determines if the group is trusted by checking
44 * are zero, then no sensors in the group are trusted.
46 * @return bool - if group is trusted or not
H A Dtrust_group.hpp29 * be trusted or not, where if it isn't trusted then it shouldn't
35 * then no sensor in the group is trusted. All sensors in the group
100 * Called when the group just changed to not trusted,
114 * Called when the group just changed to trusted.
130 * it will be considered trusted.
153 * Says if all sensors in the group are currently trusted,
156 * @return bool - if the group's sensors are trusted or not
184 * Checks if the group's sensors are trusted.
189 * @return bool - if group is trusted or not
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/trusted-firmware-a/
H A Dtrusted-firmware-a_%.bbappend6 MACHINE_TFA_REQUIRE:corstone1000 = "trusted-firmware-a-corstone1000.inc"
7 MACHINE_TFA_REQUIRE:fvp-base = "trusted-firmware-a-fvp-base.inc"
8 MACHINE_TFA_REQUIRE:juno = "trusted-firmware-a-juno.inc"
9 MACHINE_TFA_REQUIRE:sbsa-ref = "trusted-firmware-a-sbsa-ref.inc"
10 MACHINE_TFA_REQUIRE:sgi575 = "trusted-firmware-a-sgi575.inc"
/openbmc/qemu/tests/functional/
H A Dtest_aarch64_sbsaref.py27 - Trusted Firmware v2.12.0
79 # https://github.com/ARM-software/arm-trusted-firmware/blob/v2.8.0/\
80 # docs/design/trusted-board-boot.rst#trusted-board-boot-sequence
84 # AP Trusted ROM
85 wait_for_console_pattern(self, "Booting Trusted Firmware")
89 # Trusted Boot Firmware
96 # Non-trusted Firmware
/openbmc/openbmc/meta-arm/meta-arm/recipes-bsp/trusted-firmware-m/
H A Dtrusted-firmware-m_2.1.1.bb1 require recipes-bsp/trusted-firmware-m/trusted-firmware-m-${PV}-src.inc
2 require recipes-bsp/trusted-firmware-m/trusted-firmware-m.inc
H A Dtrusted-firmware-m_2.2.0.bb1 require recipes-bsp/trusted-firmware-m/trusted-firmware-m-${PV}-src.inc
2 require recipes-bsp/trusted-firmware-m/trusted-firmware-m.inc
H A Dtrusted-firmware-m-scripts-native_2.2.0.bb1 require recipes-bsp/trusted-firmware-m/trusted-firmware-m-${PV}-src.inc
2 require recipes-bsp/trusted-firmware-m/trusted-firmware-m-scripts-native.inc
H A Dtrusted-firmware-m-scripts-native_2.1.1.bb1 require recipes-bsp/trusted-firmware-m/trusted-firmware-m-${PV}-src.inc
2 require recipes-bsp/trusted-firmware-m/trusted-firmware-m-scripts-native.inc
H A Dtrusted-firmware-m_git.bb1 require recipes-bsp/trusted-firmware-m/trusted-firmware-m-git-src.inc
2 require recipes-bsp/trusted-firmware-m/trusted-firmware-m.inc
/openbmc/u-boot/include/
H A Dtee.h55 * struct tee_optee_ta_uuid - OP-TEE Trusted Application (TA) UUID format
86 * struct tee_param_memref - memory reference for a Trusted Application
100 * struct tee_param_value - value parameter for a Trusted Application
112 * struct tee_param - invoke parameter for a Trusted Application
132 * @uuid: [in] UUID of the Trusted Application
150 * @func: [in] Trusted Application function, specific to the TA
173 * @open_session: Opens a session to a Trusted Application in the TEE,
174 * @close_session: Closes a session to Trusted Application,
175 * @invoke_func: Invokes a function in a Trusted Application,
187 * open_session() - Open a session to a Trusted Application
[all …]
/openbmc/phosphor-fan-presence/docs/monitor/
H A Dclass.md7 determines if the group is trusted by checking each fan sensors listed within
8 the trust group against an algorithm that returns whether they can be trusted or
14 - Determines if the group is trusted by checking if any sensors in the group
16 group are trusted and therefore monitoring of all the sensors in the group
/openbmc/u-boot/drivers/tee/optee/
H A DKconfig1 # OP-TEE Trusted Execution Environment Configuration
6 This implements the OP-TEE Trusted Execution Environment (TEE)
7 driver. OP-TEE is a Trusted OS designed primarily to rely on the
21 Enables support for the AVB Trusted Application (TA) in OP-TEE.
H A Doptee_msg.h44 * to the Trusted Application.
171 * @func: Trusted Application function, specific to the Trusted Application,
181 * All normal calls to Trusted OS uses this struct. If cmd requires further
186 * Temp memref parameters can be fragmented if supported by the Trusted OS
191 * it will still be presented as a single logical memref to the Trusted
247 * Get UUID of Trusted OS.
249 * Used by non-secure world to figure out which Trusted OS is installed.
250 * Note that returned UUID is the UUID of the Trusted OS, not of the API.
262 * Get revision of Trusted OS.
264 * Used by non-secure world to figure out which version of the Trusted OS
[all …]
/openbmc/u-boot/doc/
H A DREADME.armada-secureboot1 The trusted boot framework on Marvell Armada 38x
6 1. Overview of the trusted boot
15 1. Overview of the trusted boot
18 The Armada's trusted boot framework enables the SoC to cryptographically verify
48 image, which employs this trusted boot framework, the following tasks need to
61 The documentation of the trusted boot mode is contained in part 1, chapter
88 trusted boot (also known as "security header")
92 Trusted debug mode - A special mode for the trusted boot that allows
93 debugging of devices employing the trusted boot
96 Trusted boot framework - The ARMADA SoC's implementation of a secure verified
[all …]
H A DREADME.tee7 A TEE (Trusted Execution Environment) is a trusted OS running in some
34 - tee_open_session() opens a session to a Trusted Application
36 - tee_invoke_func() invokes a function in a Trusted Application
38 - tee_close_session() closes a session to a Trusted Application
79 | Client | | Trusted |
90 | driver | | Trusted OS |
/openbmc/u-boot/drivers/tee/
H A DKconfig1 # Generic Trusted Execution Environment Configuration
3 bool "Trusted Execution Environment support"
7 This implements a generic interface towards a Trusted Execution
8 Environment (TEE). A TEE is a trusted OS running in some secure
/openbmc/openbmc/meta-arm/meta-arm/recipes-security/trusted-services/
H A Dtrusted-services-src.inc1 # Define sources of Trusted Service and all external dependencies
5 …://git.trustedfirmware.org/TS/trusted-services.git;protocol=https;branch=main;name=trusted-service…
16 # Trusted Services; aka. v1.1.0
20 S = "${WORKDIR}/git/trusted-services"
54 SRCREV_FORMAT = "trusted-services_dtc_mbedtls_nanopb_qcbor_tcose_cpputest"
H A Dts-service-test_git.bb1 DESCRIPTION = "Trusted Services ts-service-test deployment for arm-linux. \
3 on an Arm platform with real deployments of trusted services."
7 require trusted-services.inc
H A Dts-sp-common.inc1 # Common part of all Trusted Services SPs recipes
5 require trusted-services.inc
32 # Trusted Services SPs do not compile with clang
40 # Override yoctos default linux specific toolchain file. trusted-services.inc

12345678910>>...16