Home
last modified time | relevance | path

Searched refs:per (Results 1 – 25 of 47) sorted by relevance

12

/trusted-firmware-a/plat/nvidia/tegra/soc/t194/
A Dplat_sip_calls.c44 uint64_t per[3] = {0ULL}; in plat_sip_handler() local
63 per[0] = smmu_per[0] | ((uint64_t)smmu_per[1] << 32U); in plat_sip_handler()
64 per[1] = smmu_per[2] | ((uint64_t)smmu_per[3] << 32U); in plat_sip_handler()
65 per[2] = smmu_per[4] | ((uint64_t)smmu_per[5] << 32U); in plat_sip_handler()
68 write_ctx_reg(get_gpregs_ctx(handle), CTX_GPREG_X1, per[0]); in plat_sip_handler()
69 write_ctx_reg(get_gpregs_ctx(handle), CTX_GPREG_X2, per[1]); in plat_sip_handler()
70 write_ctx_reg(get_gpregs_ctx(handle), CTX_GPREG_X3, per[2]); in plat_sip_handler()
/trusted-firmware-a/fdts/
A Dfvp-base-gicv3-psci-1t.dts7 /* Configuration: max 4 clusters with up to 4 CPUs with 1 thread per each */
A Dfvp-base-gicv3-psci-aarch32-1t.dts7 /* Configuration: max 4 clusters with up to 4 CPUs with 1 thread per each */
A Dfvp-base-gicv3-psci-dynamiq-2t.dts7 /* DynamIQ configuration: 1 cluster with up to 8 CPUs with 2 threads per each */
A Dfvp-base-gicv3-psci-common.dtsi82 * Define a list of Group 1 Secure and Group 0 interrupts as per GICv3
A Dfvp-defs.dtsi337 /* Max 4 CPUs per cluster */
/trusted-firmware-a/docs/build/TF-A_2.5/_sources/components/fconf/
A Dmpmm-bindings.rst.txt5 DTB bindings allow the platform to communicate per-core support for |MPMM| via
/trusted-firmware-a/docs/components/fconf/
A Dmpmm-bindings.rst5 DTB bindings allow the platform to communicate per-core support for |MPMM| via
/trusted-firmware-a/plat/nvidia/tegra/scat/
A Dbl31.scat193 /* padded memory section to store per cpu bakery locks */
225 /* padded memory section to store per cpu timestamps */
/trusted-firmware-a/docs/build/TF-A_2.5/_sources/components/
A Dmpmm.rst.txt11 |MPMM| is enabled on a per-core basis by the EL3 runtime firmware. The presence
/trusted-firmware-a/docs/components/
A Dmpmm.rst11 |MPMM| is enabled on a per-core basis by the EL3 runtime firmware. The presence
/trusted-firmware-a/
A D.editorconfig66 # "Use 4 spaces per indentation level."
/trusted-firmware-a/docs/build/latex/
A Dsphinxlatexnumfig.sty45 % LaTeX core per default does not reset chapter or section
/trusted-firmware-a/docs/design/
A Dfirmware-design.rst549 BL31 initializes the per-CPU data framework, which provides a cache of
973 Function ID is passed in W0 from the lower exception level (as per the
2125 Depending upon the data cache line size, the per-CPU fields of the
2175 | `bakery_info_t`| <-- Lock_0 per-CPU field
2178 | `bakery_info_t`| <-- Lock_1 per-CPU field
2183 | `bakery_info_t`| <-- Lock_N per-CPU field
2191 | `bakery_info_t`| <-- Lock_0 per-CPU field
2194 | `bakery_info_t`| <-- Lock_1 per-CPU field
2199 | `bakery_info_t`| <-- Lock_N per-CPU field
2496 PMF timestamps are stored in a per-service timestamp region. On a
[all …]
A Dinterrupt-framework-design.rst328 interrupt was generated and routed as per the routing model specified
510 will be routed to EL3 (as per the routing model where **CSS=1 and
534 If ``PSTATE.F=1`` then Secure-EL1 interrupts will be handled as per the
635 upon exception entry. The registers are saved in the per-cpu ``cpu_context``
639 per-cpu ``cpu_context`` data structure referenced by the ``SP_EL3`` register.
642 from the per-cpu ``cpu_context`` data structure in ``SP_EL0`` and
675 The handler function returns a reference to the per-cpu ``cpu_context_t``
728 per the synchronous interrupt handling model it implements. A Secure-EL1
735 #. Setting the return value of the handler to the per-cpu ``cpu_context`` if
787 #. It returns the per-cpu ``cpu_context`` to indicate that the interrupt can
/trusted-firmware-a/docs/build/TF-A_2.5/_sources/design/
A Dfirmware-design.rst.txt549 BL31 initializes the per-CPU data framework, which provides a cache of
973 Function ID is passed in W0 from the lower exception level (as per the
2125 Depending upon the data cache line size, the per-CPU fields of the
2175 | `bakery_info_t`| <-- Lock_0 per-CPU field
2178 | `bakery_info_t`| <-- Lock_1 per-CPU field
2183 | `bakery_info_t`| <-- Lock_N per-CPU field
2191 | `bakery_info_t`| <-- Lock_0 per-CPU field
2194 | `bakery_info_t`| <-- Lock_1 per-CPU field
2199 | `bakery_info_t`| <-- Lock_N per-CPU field
2496 PMF timestamps are stored in a per-service timestamp region. On a
[all …]
A Dinterrupt-framework-design.rst.txt328 interrupt was generated and routed as per the routing model specified
510 will be routed to EL3 (as per the routing model where **CSS=1 and
534 If ``PSTATE.F=1`` then Secure-EL1 interrupts will be handled as per the
635 upon exception entry. The registers are saved in the per-cpu ``cpu_context``
639 per-cpu ``cpu_context`` data structure referenced by the ``SP_EL3`` register.
642 from the per-cpu ``cpu_context`` data structure in ``SP_EL0`` and
675 The handler function returns a reference to the per-cpu ``cpu_context_t``
728 per the synchronous interrupt handling model it implements. A Secure-EL1
735 #. Setting the return value of the handler to the per-cpu ``cpu_context`` if
787 #. It returns the per-cpu ``cpu_context`` to indicate that the interrupt can
/trusted-firmware-a/docs/build/TF-A_2.5/_sources/plat/
A Dpoplar.rst.txt12 video at 60 frames per second.
A Dnvidia-tegra.rst.txt35 micro-ops can be executed per clock), and includes a 128KB 4-way L1
/trusted-firmware-a/docs/security_advisories/
A Dsecurity-advisory-tfv-8.rst31 As per the `SMC Calling Convention`_, up to 4 values may be returned to the
/trusted-firmware-a/docs/plat/
A Dpoplar.rst12 video at 60 frames per second.
A Dnvidia-tegra.rst35 micro-ops can be executed per clock), and includes a 128KB 4-way L1
/trusted-firmware-a/docs/build/TF-A_2.5/_sources/security_advisories/
A Dsecurity-advisory-tfv-8.rst.txt31 As per the `SMC Calling Convention`_, up to 4 values may be returned to the
/trusted-firmware-a/docs/build/TF-A_2.5/_sources/plat/marvell/armada/
A Dporting.rst.txt113 The PHY porting layer simplifies updating static values per board type,
/trusted-firmware-a/docs/plat/marvell/armada/
A Dporting.rst113 The PHY porting layer simplifies updating static values per board type,

Completed in 29 milliseconds

12