| /external/arm-trusted-firmware/docs/design/ |
| D | interrupt-framework-design.rst | 8 #. It should be possible to route interrupts meant to be handled by secure
9 software (Secure interrupts) to EL3, when execution is in non-secure state
11 the interrupt to either software in EL3 or Secure-EL1 depending upon the
13 that secure interrupts are under the control of the secure software with
15 intervention from non-secure software.
18 non-secure software (Non-secure interrupts) to the last executed exception
19 level in the normal world when the execution is in secure world at
21 knowledge of software executing in Secure-EL1/Secure-EL0. The choice of
22 approach should be governed by the secure software. This requirement
23 ensures that non-secure software is able to execute in tandem with the
[all …]
|
| /external/trusty/arm-trusted-firmware/docs/design/ |
| D | interrupt-framework-design.rst | 8 #. It should be possible to route interrupts meant to be handled by secure
9 software (Secure interrupts) to EL3, when execution is in non-secure state
11 the interrupt to either software in EL3 or Secure-EL1 depending upon the
13 that secure interrupts are under the control of the secure software with
15 intervention from non-secure software.
18 non-secure software (Non-secure interrupts) to the last executed exception
19 level in the normal world when the execution is in secure world at
21 knowledge of software executing in Secure-EL1/Secure-EL0. The choice of
22 approach should be governed by the secure software. This requirement
23 ensures that non-secure software is able to execute in tandem with the
[all …]
|
| /external/coreboot/src/mainboard/opencellular/elgon/ |
| D | devicetree.cb | 8 register "secure" = "0"
11 register "secure" = "0"
15 register "secure" = "0"
19 register "secure" = "1"
23 register "secure" = "1"
27 register "secure" = "1"
31 register "secure" = "0"
35 register "secure" = "0"
39 register "secure" = "0"
43 register "secure" = "1"
[all …]
|
| /external/coreboot/src/mainboard/cavium/cn8100_sff_evb/ |
| D | devicetree.cb | 8 register "secure" = "0"
11 register "secure" = "0"
15 register "secure" = "0"
19 register "secure" = "1"
23 register "secure" = "1"
27 register "secure" = "1"
31 register "secure" = "0"
35 register "secure" = "0"
39 register "secure" = "0"
43 register "secure" = "1"
[all …]
|
| /external/trusty/arm-trusted-firmware/services/spd/tspd/ |
| D | tspd_main.c | 9 * This is the Secure Payload Dispatcher (SPD). The dispatcher is meant to be a
10 * plug-in component to the Secure Monitor, registered as a runtime service. The
11 * SPD is expected to be a functional extension of the Secure Payload (SP) that
12 * executes in Secure EL1. The Secure Monitor will delegate all SMCs targeting
14 * handle the request locally or delegate it to the Secure Payload. It is also
36 * Address of the entrypoint vector table in the Secure Payload. It is
42 * Array to keep track of per-cpu Secure Payload state
55 * This helper function handles Secure EL1 preemption. The preemption could be
56 * due Non Secure interrupts or EL3 interrupts. In both the cases we context
64 assert(handle == cm_get_context(SECURE)); in tspd_handle_sp_preemption()
[all …]
|
| /external/robolectric/robolectric/src/test/java/org/robolectric/shadows/ |
| D | ShadowSettingsTest.java | 6 import static android.provider.Settings.Secure.LOCATION_MODE;
7 import static android.provider.Settings.Secure.LOCATION_MODE_BATTERY_SAVING;
8 import static android.provider.Settings.Secure.LOCATION_MODE_HIGH_ACCURACY;
9 import static android.provider.Settings.Secure.LOCATION_MODE_OFF;
10 import static android.provider.Settings.Secure.LOCATION_MODE_SENSORS_ONLY;
23 import android.provider.Settings.Secure;
56 assertThat(Settings.Secure.getInt(contentResolver, "property", 0)).isEqualTo(0); in testSecureGetInt()
57 assertThat(Settings.Secure.getInt(contentResolver, "property", 2)).isEqualTo(2); in testSecureGetInt()
59 Settings.Secure.putInt(contentResolver, "property", 1); in testSecureGetInt()
60 assertThat(Settings.Secure.getInt(contentResolver, "property", 0)).isEqualTo(1); in testSecureGetInt()
[all …]
|
| /external/arm-trusted-firmware/services/spd/tspd/ |
| D | tspd_main.c | 9 * This is the Secure Payload Dispatcher (SPD). The dispatcher is meant to be a
10 * plug-in component to the Secure Monitor, registered as a runtime service. The
11 * SPD is expected to be a functional extension of the Secure Payload (SP) that
12 * executes in Secure EL1. The Secure Monitor will delegate all SMCs targeting
14 * handle the request locally or delegate it to the Secure Payload. It is also
36 * Address of the entrypoint vector table in the Secure Payload. It is
42 * Array to keep track of per-cpu Secure Payload state
55 * This helper function handles Secure EL1 preemption. The preemption could be
56 * due Non Secure interrupts or EL3 interrupts. In both the cases we context
64 assert(handle == cm_get_context(SECURE)); in tspd_handle_sp_preemption()
[all …]
|
| /external/trusty/arm-trusted-firmware/docs/components/ |
| D | secure-partition-manager-mm.rst | 1 Secure Partition Manager (MM)
7 This document describes the implementation where the Secure Partition Manager
8 resides at EL3 and management services run from isolated Secure Partitions at
17 applications to provide security services like DRM, secure payment and
19 used by Non-secure world applications to access these services. A Trusted OS
31 centres and enterprise servers) the secure software stack typically does not
43 A **Secure Partition** is a software execution environment instantiated in
45 Since S-EL0 is an unprivileged Exception Level, a Secure Partition relies on
47 resources. Essentially, it is a software sandbox in the Secure world that runs
57 Note that currently TF-A only supports handling one Secure Partition.
[all …]
|
| D | firmware-update.rst | 31 A common system design will place the ``Update Agent`` in the Secure-world
119 This document describes the secure world FWU design. It is beyond its scope to
129 some parts of FWU to be implemented in other secure and normal world images.
136 - Copying images from non-secure to secure memory
138 - Context switching between the normal and secure world during the FWU
141 - Other secure world FWU images handle platform initialization required by
144 interfaces to non-secure memory.
176 is permitted to request execution of a secure world FWU image (after
177 authentication). Secure world certificates and non-AP images are examples
179 - Secure or non-secure image. This indicates whether the image is
[all …]
|
| /external/arm-trusted-firmware/docs/components/ |
| D | secure-partition-manager-mm.rst | 1 Secure Partition Manager (MM)
7 Two implementations of a Secure Partition Manager co-exist in the TF-A codebase:
9 - SPM based on the FF-A specification (:ref:`Secure Partition Manager`).
15 This document describes the latter implementation where the Secure Partition Manager
16 resides at EL3 and management services run from isolated Secure Partitions at S-EL0.
24 applications to provide security services like DRM, secure payment and
26 used by Non-secure world applications to access these services. A Trusted OS
38 centres and enterprise servers) the secure software stack typically does not
50 A **Secure Partition** is a software execution environment instantiated in
52 Since S-EL0 is an unprivileged Exception Level, a Secure Partition relies on
[all …]
|
| D | firmware-update.rst | 23 This document describes the secure world FWU design. It is beyond its scope to
33 some parts of FWU to be implemented in other secure and normal world images.
40 - Copying images from non-secure to secure memory
42 - Context switching between the normal and secure world during the FWU
45 - Other secure world FWU images handle platform initialization required by
48 interfaces to non-secure memory.
80 is permitted to request execution of a secure world FWU image (after
81 authentication). Secure world certificates and non-AP images are examples
83 - Secure or non-secure image. This indicates whether the image is
84 authenticated/executed in secure or non-secure memory.
[all …]
|
| /external/grpc-grpc/tools/run_tests/performance/ |
| D | scenario_config.py | 128 secure=True, argument
158 "security_params": _get_secargs(secure),
170 "security_params": _get_secargs(secure),
284 secure=False,
302 secure=False,
318 secure=False,
336 secure=False,
343 for secure in [True, False]:
344 secstr = "secure" if secure else "insecure"
345 smoketest_categories = [SMOKETEST] if secure else []
[all …]
|
| /external/rust/android-crates-io/crates/grpcio-sys/grpc/tools/run_tests/performance/ |
| D | scenario_config.py | 118 secure=True, argument
147 'security_params': _get_secargs(secure),
159 'security_params': _get_secargs(secure),
267 secure=False,
283 secure=False,
297 secure=False,
313 secure=False,
318 for secure in [True, False]:
319 secstr = 'secure' if secure else 'insecure'
320 smoketest_categories = ([SMOKETEST] if secure else [])
[all …]
|
| /external/openthread/third_party/mbedtls/repo/docs/architecture/ |
| D | psa-storage-resilience.md | 34 …)` for a key destruction). This also holds for an opaque key stored in a secure element that does …
38 * [Key management for stateful secure element keys](#designing-key-management-for-secure-element-ke…
44 ## Designing key management for secure element keys
46 …secure element key” to mean a key stored in a stateful secure element, i.e. a secure element that …
48 ### Assumptions on stateful secure elements
50 **Assumption: driver calls for key management in stateful secure elements are atomic and committing…
52 (For stateless secure elements, this assumption is vacuously true.)
56 For a secure element key, key management requires a commitment on both sites. For example, consider…
58 1. The core sends a request to the secure element to create a key.
59 2. The secure element modifies its key store to create the key.
[all …]
|
| /external/mbedtls/docs/architecture/ |
| D | psa-storage-resilience.md | 34 …)` for a key destruction). This also holds for an opaque key stored in a secure element that does …
38 * [Key management for stateful secure element keys](#designing-key-management-for-secure-element-ke…
44 ## Designing key management for secure element keys
46 …secure element key” to mean a key stored in a stateful secure element, i.e. a secure element that …
48 ### Assumptions on stateful secure elements
50 **Assumption: driver calls for key management in stateful secure elements are atomic and committing…
52 (For stateless secure elements, this assumption is vacuously true.)
56 For a secure element key, key management requires a commitment on both sites. For example, consider…
58 1. The core sends a request to the secure element to create a key.
59 2. The secure element modifies its key store to create the key.
[all …]
|
| /external/libwebsockets/lib/secure-streams/ |
| D | CMakeLists.txt | 29 secure-streams/secure-streams.c
30 secure-streams/policy-common.c
31 secure-streams/system/captive-portal-detect/captive-portal-detect.c
32 secure-streams/protocols/ss-raw.c
36 secure-streams/policy-json.c
37 secure-streams/system/fetch-policy/fetch-policy.c
42 secure-streams/protocols/ss-h1.c
47 secure-streams/protocols/ss-h2.c
52 secure-streams/protocols/ss-ws.c
57 secure-streams/protocols/ss-mqtt.c
[all …]
|
| /external/trusty/arm-trusted-firmware/services/spd/tlkd/ |
| D | tlkd_main.c | 9 * This is the Secure Payload Dispatcher (SPD). The dispatcher is meant to be a
10 * plug-in component to the Secure Monitor, registered as a runtime service. The
11 * SPD is expected to be a functional extension of the Secure Payload (SP) that
12 * executes in Secure EL1. The Secure Monitor will delegate all SMCs targeting
14 * handle the request locally or delegate it to the Secure Payload. It is also
37 * Per-cpu Secure Payload state
54 * Secure Payload Dispatcher's timer interrupt handler
69 * Disable the routing of NS interrupts from secure world to in tlkd_interrupt_handler()
72 disable_intr_rm_local(INTR_TYPE_S_EL1, SECURE); in tlkd_interrupt_handler()
78 /* Save non-secure state */ in tlkd_interrupt_handler()
[all …]
|
| /external/arm-trusted-firmware/services/spd/tlkd/ |
| D | tlkd_main.c | 9 * This is the Secure Payload Dispatcher (SPD). The dispatcher is meant to be a
10 * plug-in component to the Secure Monitor, registered as a runtime service. The
11 * SPD is expected to be a functional extension of the Secure Payload (SP) that
12 * executes in Secure EL1. The Secure Monitor will delegate all SMCs targeting
14 * handle the request locally or delegate it to the Secure Payload. It is also
37 * Per-cpu Secure Payload state
54 * Secure Payload Dispatcher's timer interrupt handler
69 * Disable the routing of NS interrupts from secure world to in tlkd_interrupt_handler()
72 disable_intr_rm_local(INTR_TYPE_S_EL1, SECURE); in tlkd_interrupt_handler()
78 /* Save non-secure state */ in tlkd_interrupt_handler()
[all …]
|
| /external/libwebsockets/minimal-examples/secure-streams/minimal-secure-streams-smd/ |
| D | CMakeLists.txt | 1 project(lws-minimal-secure-streams-smd C)
19 add_executable(${PROJECT_NAME} minimal-secure-streams-smd.c)
28 $<TARGET_FILE:lws-minimal-secure-streams-smd>)
31 add_test(NAME ss-smd COMMAND lws-minimal-secure-streams-smd)
35 … WORKING_DIRECTORY ${CMAKE_SOURCE_DIR}/minimal-examples/secure-streams/minimal-secure-streams-smd
42 $<TARGET_FILE:lws-minimal-secure-streams-smd>
47 $<TARGET_FILE:lws-minimal-secure-streams-smd>
52 $<TARGET_FILE:lws-minimal-secure-streams-smd>
56 add_test(NAME ss-smd-fi1 COMMAND lws-minimal-secure-streams-smd
59 add_test(NAME ss-smd-fi2 COMMAND lws-minimal-secure-streams-smd
[all …]
|
| /external/arm-trusted-firmware/plat/xilinx/versal/pm_service/ |
| D | pm_api_sys.c | 78 * @flag 0 - Call from secure source
79 * 1 - Call from non-secure source
96 * @flag 0 - Call from secure source
97 * 1 - Call from non-secure source
116 * @flag 0 - Call from secure source
117 * 1 - Call from non-secure source
155 * @flag 0 - Call from secure source
156 * 1 - Call from non-secure source
186 * @flag 0 - Call from secure source
187 * 1 - Call from non-secure source
[all …]
|
| /external/arm-trusted-firmware/plat/renesas/common/include/registers/ |
| D | cpg_registers.h | 36 /* Secure Module Stop Control Register 0 */
38 /* Secure Module Stop Control Register 1 */
40 /* Secure Module Stop Control Register 2 */
42 /* Secure Module Stop Control Register 3 */
44 /* Secure Module Stop Control Register 4 */
46 /* Secure Module Stop Control Register 5 */
48 /* Secure Module Stop Control Register 6 */
50 /* Secure Module Stop Control Register 7 */
52 /* Secure Module Stop Control Register 8 */
54 /* Secure Module Stop Control Register 9 */
[all …]
|
| /external/trusty/arm-trusted-firmware/plat/renesas/common/include/registers/ |
| D | cpg_registers.h | 36 /* Secure Module Stop Control Register 0 */
38 /* Secure Module Stop Control Register 1 */
40 /* Secure Module Stop Control Register 2 */
42 /* Secure Module Stop Control Register 3 */
44 /* Secure Module Stop Control Register 4 */
46 /* Secure Module Stop Control Register 5 */
48 /* Secure Module Stop Control Register 6 */
50 /* Secure Module Stop Control Register 7 */
52 /* Secure Module Stop Control Register 8 */
54 /* Secure Module Stop Control Register 9 */
[all …]
|
| /external/arm-trusted-firmware/docs/about/ |
| D | features.rst | 14 - Initialization of the secure world, for example exception vectors, control
28 - SMC (Secure Monitor Call) handling, conforming to the `SMC Calling
35 for example an AArch32 Secure OS.
37 - A minimal AArch32 Secure Payload (*SP_MIN*) to demonstrate |PSCI| library
40 - Secure Monitor library code such as world switching, EL1 context management
42 When a Secure-EL1 Payload (SP) is present, for example a Secure OS, the
43 AArch64 EL3 Runtime Software must be integrated with a Secure Payload
46 - A Test SP and SPD to demonstrate AArch64 Secure Monitor functionality and SP
49 - SPDs for the `OP-TEE Secure OS`_, `NVIDIA Trusted Little Kernel`_
50 and `Trusty Secure OS`_.
[all …]
|
| /external/arm-trusted-firmware/services/spd/opteed/ |
| D | opteed_main.c | 9 * This is the Secure Payload Dispatcher (SPD). The dispatcher is meant to be a
10 * plug-in component to the Secure Monitor, registered as a runtime service. The
11 * SPD is expected to be a functional extension of the Secure Payload (SP) that
12 * executes in Secure EL1. The Secure Monitor will delegate all SMCs targeting
14 * handle the request locally or delegate it to the Secure Payload. It is also
67 /* Save the non-secure context before entering the OPTEE */ in opteed_sel1_interrupt_handler()
73 assert(&optee_ctx->cpu_ctx == cm_get_context(SECURE)); in opteed_sel1_interrupt_handler()
75 cm_set_elr_el3(SECURE, (uint64_t)&optee_vector_table->fiq_entry); in opteed_sel1_interrupt_handler()
76 cm_el1_sysregs_context_restore(SECURE); in opteed_sel1_interrupt_handler()
77 cm_set_next_eret_context(SECURE); in opteed_sel1_interrupt_handler()
[all …]
|
| /external/arm-trusted-firmware/bl31/ |
| D | ehf.c | 37 * Convert index into secure priority using the platform-defined priority bits
47 /* Returns whether given priority is in secure priority range */
96 * This API is expected to be invoked before restoring context (Secure or
97 * Non-secure) in preparation for the respective dispatch.
163 * This API is expected to be invoked after saving context (Secure or
164 * Non-secure), having concluded the respective dispatch.
221 * After leaving Non-secure world, stash current Non-secure Priority Mask, and
222 * set Priority Mask to the highest Non-secure priority so that Non-secure
223 * interrupts cannot preempt Secure execution.
225 * If the current running priority is in the secure range, or if there are
[all …]
|