| /rk3399_ARM-atf/docs/components/ |
| H A D | granule-protection-tables-design.rst | 9 different PAS (physical address spaces) at runtime.
12 and non-secure. In addition to new security states, corresponding physical
65 function: the PPS (protected physical space) which is the total amount of
66 protected physical address space in the system, PGS (physical granule size)
68 determines how much physical memory is governed by each level 0 entry. A granule
99 A ``pas_region_t`` structure is a way to represent a physical address space and
104 #. The base physical address
117 compatibility issues. These macros take the base physical address, region size,
|
| H A D | realm-management-extension.rst | 46 Realm-world firmware (`RMM`_) is loaded by BL2 in the Realm physical address
60 Isolation between the four physical address spaces is enforced by a process
63 Root world that describes the physical address space assignment of every
65 transition granules between different physical address spaces has been added.
|
| H A D | debugfs-design.rst | 98 needs to allocate a physical page frame and transmit its address.
105 - Notice, a physical device driver if exposed by the firmware may conflict with
107 physical device.
|
| H A D | ffa-manifest-binding.rst | 138 physical interrupt.
149 physical interrupt.
415 - Base physical address in which the SPMC binary is placed. Should be page aligned.
418 - Defines the physical address for the cold boot primary core entrypoint used by the SPMD
|
| H A D | secure-partition-manager.rst | 227 - X0 holds the ``TOS_FW_CONFIG`` physical address (or SPMC manifest blob).
228 - X1 holds the ``HW_CONFIG`` physical address.
|
| H A D | xlat-tables-lib-v2-design.rst | 23 #. Support for non-identity virtual to physical mappings to compress the virtual
59 - its physical base address;
151 * The size of the physical address space.
153 Size in bytes of the physical address space to map using this context.
163 - size of the physical address space: ``PLAT_PHY_ADDR_SPACE_SIZE``.
|
| H A D | arm-sip-service.rst | 62 of the entry point (physical address) at which execution should start, after
|
| H A D | el3-spmc.rst | 236 The SPMC calling FFA_FEATURES at secure physical FF-A instance always get
338 the FFA_SPM_ID_GET interface at the secure physical FF-A instance.
457 SP manifest field should match the number of physical PE.
|
| H A D | sdei.rst | 196 The SDEI specification requires that the *physical* SDEI client executes in the
|
| H A D | exception-handling.rst | 415 panics. Also, to prevent interruption by physical interrupts of lower
|
| H A D | rmm-el3-comms-spec.rst | 1056 …y EL3. These include system registers with the ``_EL2`` prefix. The EL2 physical and virtual timer…
|
| /rk3399_ARM-atf/docs/components/fconf/ |
| H A D | fconf_properties.rst | 37 - A platform uses this physical address to copy the configuration to
|
| /rk3399_ARM-atf/docs/threat_model/firmware_threat_model/ |
| H A D | threat_model_fw_update_and_recovery.rst | 59 outside of TF-A security boundary or for a physical attacker to modify it
75 access from secure software, protecting it from physical, unauthenticated
|
| H A D | threat_model.rst | 162 In this threat model an advanced physical attacker that has the capability
167 Certain non-invasive physical attacks that do not need modifications to the
263 that require physical access are unlikely in server environments while
839 | Threat | | **An attacker with physical access can execute |
852 | | achieved with physical access to the device by |
953 Event Log backed by a discrete TPM, physical vulnerabilities come to mind.
958 Measured Boot. This vulnerability requires physical access to the host machine.
960 TF-A does not provide any mitigations against these physical vulnerabilities,
|
| H A D | threat_model_el3_spm.rst | 26 - Not covering advanced or invasive physical attacks such as decapsulation,
113 - Hardware attacks (non-invasive) requiring a physical access to the device,
|
| /rk3399_ARM-atf/docs/plat/ |
| H A D | allwinner.rst | 105 0 64K 16M 1GB 1G+160M physical address
134 address space. So the virtual addresses used in BL31 match the physical
|
| /rk3399_ARM-atf/docs/security_advisories/ |
| H A D | security-advisory-tfv-11.rst | 30 SDEI_INTERRUPT_BIND is used to bind any physical interrupt into a normal
|
| /rk3399_ARM-atf/docs/plat/marvell/armada/ |
| H A D | porting.rst | 26 This file describes the SoC physical memory mapping to be used for the CCU,
32 In cases where a special physical address map is needed (e.g. Special size for
|
| /rk3399_ARM-atf/docs/ |
| H A D | porting-guide.rst | 68 only for re-mapping peripheral physical addresses and allows platforms with high
451 Defines the ID of the secure physical generic timer interrupt used by the
476 table library code. A region consists of physical base address, virtual base
493 Defines the total size of the physical address space in bytes. For example,
494 for a 32 bit physical address space, this value should be ``(1ULL << 32)``.
614 Defines the physical address range that the NPU's firmware will be loaded
2377 Return value is the physical address of a memory region of at least ``size`` bytes, which needs
2501 arg2 - The IDE stream info associated with a physical device, this parameter packs the
2541 arg2 - The IDE stream info associated with a physical device, this parameter packs the
2579 arg2 - The IDE stream info associated with a physical devic
[all...] |
| /rk3399_ARM-atf/docs/design_documents/ |
| H A D | measured_boot.rst | 104 It is one of the physical backends to extend the measurements. Please refer
|
| H A D | measured_boot_dtpm_poc.rst | 48 - **TF-A TPM Drivers**: To interface with a physical (Discrete) TPM chip in
|
| H A D | psci_osi_mode.rst | 18 arises from the physical dependencies between power domains.
|
| /rk3399_ARM-atf/docs/design/ |
| H A D | console-framework.rst | 5 so that user's output can be displayed on physical consoles throughout the different
|
| H A D | interrupt-framework-design.rst | 940 #. Checks whether the interrupt is the secure physical timer interrupt. It
942 interrupt number. If it is not the secure physical timer interrupt, then
949 ``tsp_generic_timer_handler()`` to reprogram the secure physical generic
|
| H A D | firmware-design.rst | 2199 There might be loss of coherency when physical memory with mismatched
2627 By default, the global physical counter is used for the timestamp
|