Searched refs:element (Results 1 – 9 of 9) sorted by relevance
| /rk3399_ARM-atf/drivers/arm/css/scp/ |
| H A D | css_pm_scpi.c | 76 int rc, element; in css_scp_get_power_state() local 103 element = (mpidr >> MPIDR_AFF1_SHIFT) & MPIDR_AFFLVL_MASK; in css_scp_get_power_state() 105 element = mpidr & MPIDR_AFFLVL_MASK; in css_scp_get_power_state() 107 return CSS_CPU_PWR_STATE(cpu_state, element) == in css_scp_get_power_state()
|
| /rk3399_ARM-atf/docs/threat_model/firmware_threat_model/ |
| H A D | threat_model_arm_cca.rst | 85 with TF-A. A description of each diagram element is given on Table 1. On the 148 | 08 | Yes | Additional diagram element: DF8. | 164 | 13 | Yes | Additional diagram element: DF8. | 168 | 15 | Yes | Additional diagram element: DF8. | 182 | 01 | Yes | Additional diagram element: DF8. | 186 | 02 | Yes | Additional diagram element: DF8. | 204 | 07 | Yes | Additional diagram element: DF8. | 208 | 09 | Yes | Additional diagram element: DF8. | 212 | 10 | Yes | Additional diagram element: DF8. | 216 | 12 | Yes | Additional diagram element: DF8. |
|
| H A D | threat_model_el3_spm.rst | 35 A description of each diagram element is given in Table 1. In the diagram, the 138 element of the data flow diagram.
|
| H A D | threat_model.rst | 53 their interactions with TF-A. A description of each diagram element 103 firmware. The threats are identified for each diagram element on the 272 each diagram element of the data flow diagram.
|
| /rk3399_ARM-atf/tools/marvell/doimage/ |
| H A D | doimage.c | 616 const char *element, char *copy_to) in verify_and_copy_file_name_entry() 618 size_t element_length = strlen(element); in verify_and_copy_file_name_entry() 622 element, element_name, (unsigned long)element_length); in verify_and_copy_file_name_entry() 631 memcpy(copy_to, element, element_length); in verify_and_copy_file_name_entry() 650 int array_sz, element, rval = -1; in parse_sec_config_file() local 710 for (element = 0; element < array_sz; element++) { in parse_sec_config_file() 711 cfg_string = config_setting_get_string_elem(csk_array, element); in parse_sec_config_file() 714 sec_opt->csk_key_file[element])) { in parse_sec_config_file() 716 element); in parse_sec_config_file() 784 for (element = 0; element < CP_CTRL_EL_ARRAY_SZ; element++) { in parse_sec_config_file() [all …]
|
| /rk3399_ARM-atf/docs/components/ |
| H A D | context-management-library.rst | 212 This CPU data structure has a member element with an array of pointers to hold
|
| /rk3399_ARM-atf/docs/ |
| H A D | porting-guide.rst | 2892 is part of that domain and a *power domain level*. A processing element (for 2929 differently at CPU level versus higher levels. As an example, if the element at 2947 differently at CPU level versus higher levels. As an example, if the element at
|
| H A D | change-log.md | 4625 …- enable base element RAM RAS support on RD-N2 platform ([0288632](https://review.trustedfirmware.…
|
| /rk3399_ARM-atf/docs/design/ |
| H A D | firmware-design.rst | 1381 element of the array specifies the interrupt number and its attributes 1382 (priority, group, configuration). Each element of the array shall be populated
|