Home
last modified time | relevance | path

Searched refs:same (Results 1 – 25 of 81) sorted by relevance

1234

/rk3399_ARM-atf/docs/resources/diagrams/plantuml/
H A Del3_spm_dfd.puml27 {rank="same" smmu, spmd}
38 rank="same"
49 {rank="same" spmc, bl31}
50 {rank="same" spmd, lsp}
H A Dtfa_dfd.puml40 rank="same"
H A Dspm_dfd.puml34 rank="same"
H A Dtfa_rse_dfd.puml41 rank="same"
H A Dtfa_arm_cca_dfd.puml41 rank="same"
/rk3399_ARM-atf/docs/threat_model/firmware_threat_model/
H A Dthreat_model_rse_interface.rst25 is the same as in the general TF-A threat-model document.
54 received. The caller of the API must do the same if data is not needed
H A Dthreat_model_firmware_handoff.rst25 consumer are typically TF-A stages that remain within the same broader TF-A
30 Even so, it is safer to handle those threats in the same way. Doing so keeps
138 | | between stages. If the same TL is reused across |
/rk3399_ARM-atf/plat/arm/board/fvp/
H A Djmptbl.i7 # The index in the output file will be generated cumulatively in the same
/rk3399_ARM-atf/plat/arm/board/juno/
H A Djmptbl.i7 # The index in the output file will be generated cumulatively in the same
/rk3399_ARM-atf/drivers/ti/clk/
H A Dti_pll.c211 bool same; in ti_pll_consider() local
313 same = false; in ti_pll_consider()
320 same = true; in ti_pll_consider()
357 same = true; in ti_pll_consider()
375 if (!((bin == data->max_bin) && !same && !better)) { in ti_pll_consider()
378 if (!((bin == data->max_bin) && same && (fitness <= data->max_fitness))) { in ti_pll_consider()
/rk3399_ARM-atf/docs/perf/
H A Dpsci-performance-instr.rst57 state. Generally, this parameter takes the same form as the power_state
66 :param target_cpu: follows the same format as ``PSCI_STAT_RESIDENCY``.
67 :param power_state: follows the same format as ``PSCI_STAT_RESIDENCY``.
/rk3399_ARM-atf/docs/plat/
H A Drpi5.rst33 BL31 and BL33 in the same ``armstub`` image (e.g. TF-A + EDK2).
73 The boot process is essentially the same, the only notable difference being that
H A Dintel-agilex.rst29 Make all the repositories in the same ${BUILD\_PATH}.
H A Dintel-stratix10.rst29 Make all the repositories in the same ${BUILD\_PATH}.
/rk3399_ARM-atf/docs/plat/marvell/armada/
H A Duart-booting.rst48 target, which is the exactly same file as used for flashing. So when using CZ.NIC mox-imager there
85 A7K/A8K/CN913x uses same image ``flash-image.bin`` for both flashing and booting over UART.
H A Dporting.rst117 The parameters for the same type of comphy may vary even for the same
119 different HW characteristic than lanes from comphy-y to the same
/rk3399_ARM-atf/
H A Ddco.txt25 by me, under the same open source license (unless I am
/rk3399_ARM-atf/docs/process/
H A Dcoding-style.rst226 Local variables and function parameters use the same format as function names:
274 ``switch`` so that they are in the same column.
421 For header files that are in the same directory as the source file that is
424 For header files that are **not** in the same directory as the source file that
481 function shall use the same names and type qualifiers".
H A Dplatform-ports-policy.rst47 versions are the same.
/rk3399_ARM-atf/docs/security_advisories/
H A Dsecurity-advisory-tfv-5.rst47 The same issue exists for the equivalent AArch32 register, ``PMCR``, except that
H A Dsecurity-advisory-tfv-2.rst39 may or may not have the same problem, depending on the platform.
/rk3399_ARM-atf/docs/design/
H A Dreset-design.rst36 Therefore, all CPUs start at the same address (typically address 0) whenever
131 In this configuration, BL31 uses the same reset framework and code as the one
134 same way.
H A Dpsci-pd-tree.rst18 a platform will use exactly the same MPIDRs as generated by the generic PSCI
141 for a core domain will be the same as the index returned by
145 core in the array is the same as the return value from these APIs.
/rk3399_ARM-atf/docs/components/
H A Dnuma-per-cpu.rst84 CPUs access different addresses that lie on the same cache line. Although the
88 write to different addresses within the same cache line, the line bounces
145 In assembly routines, the ``per_cpu_cur`` helper macro performs the same
/rk3399_ARM-atf/docs/about/
H A Dlts.rst40 the risk of regression. At the same time the companies don't want to exclude
190 the LTS branch will be created at the same time as the TF-A November release,
203 diagram, at the same time LTS release candidate branch is made which is based
217 - Nov 2023: TF-A 2.10 is released. Not shown in the diagram, at the same time
313 will be cherry-picked from master branch to the LTS branch the same way it is done for TF-A.
341 #. The review criteria for LTS patches must be the same as TF-A patches

1234