Home
last modified time | relevance | path

Searched refs:owner (Results 1 – 12 of 12) sorted by relevance

/arm-trusted-firmware-2.8.0/plat/arm/common/fconf/
A Darm_fconf_sp.c107 arm_sp.owner[index], ARM_SP_OWNER_NAME_LEN); in fconf_populate_arm_sp()
110 if ((strncmp(arm_sp.owner[index], "SiP", in fconf_populate_arm_sp()
112 (strncmp(arm_sp.owner[index], "", in fconf_populate_arm_sp()
115 } else if (strcmp(arm_sp.owner[index], "Plat") == 0) { in fconf_populate_arm_sp()
119 arm_sp.owner[index]); in fconf_populate_arm_sp()
/arm-trusted-firmware-2.8.0/plat/arm/board/tc/fdts/
A Dtc_tb_fw_config.dts54 owner = "SiP";
60 owner = "Plat";
71 owner = "Plat";
/arm-trusted-firmware-2.8.0/plat/arm/board/fvp/fdts/
A Dfvp_tb_fw_config.dts82 owner = "SiP";
88 owner = "Plat";
94 owner = "Plat";
100 owner = "Plat";
/arm-trusted-firmware-2.8.0/include/plat/arm/common/
A Dfconf_arm_sp_getter.h24 char owner[MAX_SP_IDS][ARM_SP_OWNER_NAME_LEN]; member
/arm-trusted-firmware-2.8.0/docs/resources/diagrams/plantuml/
A Dfip-secure-partitions.puml16 owner = "Sip"
28 owner = "Plat"
/arm-trusted-firmware-2.8.0/docs/process/
A Dcode-review-guidelines.rst62 - If one code owner has become unresponsive, ask the other code owners for
65 - If there is only one code owner and they have become unresponsive, ask one
127 If a code owner is happy with a patch, they should give their approval
145 - Be mindful when reviewing a patch. As a code owner, you are viewed as
A Dcontributing.rst54 - If you are submitting new files that you intend to be the code owner for
101 - At least one code owner for each module modified by the patch. See the list
106 - If some module has no code owner, try to identify a suitable (non-code
107 owner) reviewer. Running ``git blame`` on the module's source code can
116 the only code owner of a module modified by the patch. Getting a second pair
133 In the case where a code owner could not be found for a given module,
A Dfaq.rst60 will inform the patch owner if this is going to happen.
/arm-trusted-firmware-2.8.0/docs/components/
A Dsecure-partition-manager.rst385 This file also specifies the SP owner (as an optional field) identifying the
387 The SP owner can either be the silicon or the platform provider. The
388 corresponding "owner" field value can either take the value of "SiP" or "Plat".
389 In absence of "owner" field, it defaults to "SiP" owner.
400 "owner": "SiP",
407 "owner": "Plat"
419 "owner": "Plat"
A Drmm-el3-comms-spec.rst191 …- Platform data: This is defined by the platform owner and contains information specific to that p…
/arm-trusted-firmware-2.8.0/docs/design_documents/
A Dcontext_mgmt_rework.rst88 at runtime or the platform owner has decided not to enable the feature
/arm-trusted-firmware-2.8.0/docs/
A Dchange-log.md3881 - Added an owner field to Cactus secure partitions

Completed in 25 milliseconds