Home
last modified time | relevance | path

Searched refs:secure (Results 1 – 25 of 609) sorted by relevance

12345678910>>...25

/openbmc/qemu/hw/intc/
H A Darmv7m_nvic.c442 if (secure) { in set_prio()
461 if (secure) { in get_prio()
511 if (secure) { in armv7m_nvic_clear_pending()
1058 if (attrs.secure) { in nvic_readl()
1089 if (attrs.secure) { in nvic_readl()
1126 if (attrs.secure) { in nvic_readl()
1507 if (attrs.secure) { in nvic_readl()
1691 if (attrs.secure) { in nvic_writel()
1715 if (attrs.secure) { in nvic_writel()
1761 if (!attrs.secure && cpu->env.v7m.secure && in nvic_writel()
[all …]
H A Darm_gicv3_dist.c68 if (!attrs.secure && !(s->gicd_ctlr & GICD_CTLR_DS)) { in mask_group_and_nsacr()
210 if (!attrs.secure && !(s->gicd_ctlr & GICD_CTLR_DS)) { in gicd_read_ipriorityr()
232 if (!attrs.secure && !(s->gicd_ctlr & GICD_CTLR_DS)) { in gicd_write_ipriorityr()
252 if (!attrs.secure && !(s->gicd_ctlr & GICD_CTLR_DS)) { in gicd_read_irouter()
274 if (!attrs.secure && !(s->gicd_ctlr & GICD_CTLR_DS)) { in gicd_write_irouter()
383 if (!attrs.secure && !(s->gicd_ctlr & GICD_CTLR_DS)) { in gicd_readl()
529 if ((s->gicd_ctlr & GICD_CTLR_DS) || !attrs.secure) { in gicd_readl()
555 if ((s->gicd_ctlr & GICD_CTLR_DS) || !attrs.secure) { in gicd_readl()
624 if (attrs.secure) { in gicd_writel()
743 if ((s->gicd_ctlr & GICD_CTLR_DS) || !attrs.secure) { in gicd_writel()
[all …]
/openbmc/linux/Documentation/devicetree/bindings/arm/
H A Dsecure.txt15 can be supported by prefixing the property name with "secure-". So for
16 instance "secure-foo" would override "foo". For property names with
18 "vendor,secure-foo". If there is no "secure-" property then the Secure
21 validly have "secure-" versions; this list will be enlarged on a
39 in the secure world. The combination of this with "status" allows
41 specified. If "secure-status" is not specified it defaults to the
50 secure-status = "disabled"; /* NS-only */
51 status = "okay"; secure-status = "disabled"; /* NS-only */
52 status = "disabled"; secure-status = "okay"; /* S-only */
56 The secure-chosen node
[all …]
/openbmc/qemu/target/arm/tcg/
H A Dm_helper.c66 if (!secure) { in arm_v7m_mrs_control()
254 exc_secure = secure; in v7m_stack_write()
583 assert(env->v7m.secure); in HELPER()
607 assert(env->v7m.secure); in HELPER()
1053 assert(env->v7m.secure); in HELPER()
1127 assert(env->v7m.secure); in HELPER()
1212 if (env->v7m.secure && in v7m_push_stack()
1867 if (env->v7m.secure) { in do_v7m_exception_exit()
2099 assert(!env->v7m.secure); in v7m_handle_execute_nsc()
2841 if (env->v7m.secure) { in HELPER()
[all …]
/openbmc/u-boot/doc/
H A DREADME.ti-secure1 README on how boot images are created for secure TI devices
12 devices are part of a secure development package (SECDEV) that can be
44 package for creating a bootable SPL image for secure TI devices.
65 <OUTPUT_FILE> is the full path and filename of the final secure
97 <OUTPUT_FILE> is the full path and filename of the final secure
132 non-secure devices)
177 build procedure for secure TI devices will secure these images before
193 ${TI_SECURE_DEV_PKG}/scripts/secure-binary-image.sh
206 the device's secure ROM (fixed read-only-memory that is secure and
209 Invoking the secure-binary-image script for Secure Devices
[all …]
/openbmc/qemu/include/hw/intc/
H A Darmv7m_nvic.h99 void armv7m_nvic_set_pending(NVICState *s, int irq, bool secure);
112 void armv7m_nvic_set_pending_derived(NVICState *s, int irq, bool secure);
124 void armv7m_nvic_set_pending_lazyfp(NVICState *s, int irq, bool secure);
160 int armv7m_nvic_complete_irq(NVICState *s, int irq, bool secure);
174 bool armv7m_nvic_get_ready_status(NVICState *s, int irq, bool secure);
193 bool armv7m_nvic_neg_prio_requested(NVICState *s, bool secure);
195 static inline bool armv7m_nvic_neg_prio_requested(NVICState *s, bool secure) in armv7m_nvic_neg_prio_requested() argument
/openbmc/linux/Documentation/devicetree/bindings/crypto/
H A Dinside-secure-safexcel.txt4 - compatible: Should be "inside-secure,safexcel-eip197b",
5 "inside-secure,safexcel-eip197d" or
6 "inside-secure,safexcel-eip97ies".
21 - "inside-secure,safexcel-eip197" is equivalent to
22 "inside-secure,safexcel-eip197b".
23 - "inside-secure,safexcel-eip97" is equivalent to
24 "inside-secure,safexcel-eip97ies".
29 compatible = "inside-secure,safexcel-eip197b";
/openbmc/openbmc/meta-arm/ci/
H A Dmeta-secure-core.yml5 meta-secure-core:
6 url: https://github.com/Wind-River/meta-secure-core.git
8 meta-secure-core-common:
10 meta-efi-secure-boot:
/openbmc/linux/Documentation/devicetree/bindings/arm/amlogic/
H A Damlogic,meson-gx-ao-secure.yaml5 $id: http://devicetree.org/schemas/arm/amlogic/amlogic,meson-gx-ao-secure.yaml#
15 secure firmware.
22 const: amlogic,meson-gx-ao-secure
29 - const: amlogic,meson-gx-ao-secure
50 ao-secure@140 {
51 compatible = "amlogic,meson-gx-ao-secure", "syscon";
/openbmc/linux/Documentation/devicetree/bindings/mailbox/
H A Dti,secure-proxy.yaml4 $id: http://devicetree.org/schemas/mailbox/ti,secure-proxy.yaml#
13 The Texas Instruments' secure proxy is a mailbox controller that has
25 const: ti,am654-secure-proxy
30 Contains the secure proxy thread ID used for the specific transfer path.
48 secure proxy thread in the form 'rx_<PID>'.
54 Contains the interrupt information for the Rx interrupt path for secure
71 compatible = "ti,am654-secure-proxy";
/openbmc/u-boot/arch/arm/cpu/armv7/
H A DKconfig13 bool "Enable support for booting in non-secure mode" if EXPERT
17 Say Y here to enable support for booting in non-secure / SVC mode.
20 bool "Boot in secure mode by default" if EXPERT
24 Say Y here to boot in secure mode by default even if non-secure mode
26 suppport booting in non-secure mode. Only set this if you need it.
35 Say Y here to boot in hypervisor (HYP) mode when booting non-secure.
/openbmc/openbmc/meta-arm/meta-arm-bsp/documentation/corstone1000/
H A Dsoftware-architecture.rst36 framework to build secure IoT devices.
51 secure flash. Software running on the Secure Enclave is isolated via
62 the TrustZone technology that allows secure and non-secure security
69 (`OPTEE-OS`_) in the secure world, and U-Boot(`U-Boot repo`_) and
71 non-secure and the secure world is performed via FF-A messages.
119 in the `TBBR`_ to authenticate the secure and non-secure software.
125 Corstone-1000 is unique in providing a secure environment to run a secure
127 it also has hardware isolated secure enclave environment to run such secure
131 these services which are running on a secure enclave instead of the
149 secure world or secure encalve are available. It's a trade-off between
[all …]
/openbmc/linux/Documentation/devicetree/bindings/arm/samsung/
H A Dsamsung-secure-firmware.yaml4 $id: http://devicetree.org/schemas/arm/samsung/samsung-secure-firmware.yaml#
15 - const: samsung,secure-firmware
19 Address of non-secure SYSRAM used for communication with firmware.
31 compatible = "samsung,secure-firmware";
/openbmc/u-boot/arch/arm/mach-omap2/
H A Dutils.c56 const char *secure; in omap_set_fastboot_secure() local
61 secure = "EMU"; in omap_set_fastboot_secure()
64 secure = "HS"; in omap_set_fastboot_secure()
67 secure = "GP"; in omap_set_fastboot_secure()
70 secure = NULL; in omap_set_fastboot_secure()
74 env_set("fastboot.secure", secure); in omap_set_fastboot_secure()
/openbmc/u-boot/arch/arm/cpu/
H A Du-boot.lds22 * If CONFIG_ARMV7_SECURE_BASE is true, secure code will not
26 * address for secure code.
28 * If CONFIG_ARMV7_SECURE_BASE is undefined, the secure zone will
30 * were used in secure code. The absolute addresses of the secure
70 /* Align the secure section only if we're going to use it in situ */
122 "Error: secure section exceeds secure memory size");
127 /* Reset VMA but don't allocate space if we have secure SRAM */
/openbmc/linux/Documentation/powerpc/
H A Dultravisor.rst63 the VM it is returning to is secure.
102 that are running in secure mode can access secure memory.
161 passes control in secure mode.
243 When the secure pages are transferred back to secure memory, they may
473 of a secure virtual machine or if called from a
665 * U_INVALID if VM is not secure.
703 * U_INVALID if the VM is not secure.
752 * U_INVALID if VM is not secure.
766 yet, mark the PTE as secure and back it with a secure page when that
795 * U_INVAL if VM is not secure.
[all …]
/openbmc/linux/Documentation/devicetree/bindings/nvmem/
H A Dst,stm32-romem.yaml36 st,non-secure-otp:
38 This property explicits a factory programmed area that both secure
39 and non-secure worlds can access. It is needed when, by default, the
40 related area can only be reached by the secure world.
65 st,non-secure-otp;
H A Damlogic,meson-gxbb-efuse.yaml26 secure-monitor:
27 description: phandle to the secure-monitor node
33 - secure-monitor
44 secure-monitor = <&sm>;
/openbmc/openbmc/meta-arm/kas/
H A Dcorstone1000-base.yml32 meta-secure-core:
33 url: https://github.com/wind-river/meta-secure-core.git
36 meta-secure-core-common:
38 meta-efi-secure-boot:
/openbmc/linux/Documentation/devicetree/bindings/thermal/
H A Damlogic,thermal.yaml31 amlogic,ao-secure:
32 description: phandle to the ao-secure syscon
43 - amlogic,ao-secure
56 amlogic,ao-secure = <&sec_AO>;
/openbmc/linux/drivers/gpu/drm/amd/amdgpu/
H A Damdgpu_ib.c139 bool secure, init_shadow; in amdgpu_ib_schedule() local
246 secure = false; in amdgpu_ib_schedule()
248 secure = ib->flags & AMDGPU_IB_FLAGS_SECURE; in amdgpu_ib_schedule()
249 amdgpu_ring_emit_frame_cntl(ring, true, secure); in amdgpu_ib_schedule()
256 if (secure != !!(ib->flags & AMDGPU_IB_FLAGS_SECURE)) { in amdgpu_ib_schedule()
257 amdgpu_ring_emit_frame_cntl(ring, false, secure); in amdgpu_ib_schedule()
258 secure = !secure; in amdgpu_ib_schedule()
259 amdgpu_ring_emit_frame_cntl(ring, true, secure); in amdgpu_ib_schedule()
268 amdgpu_ring_emit_frame_cntl(ring, false, secure); in amdgpu_ib_schedule()
/openbmc/u-boot/board/xilinx/zynqmp/
H A DKconfig11 Enable ZynqMP specific commands like "zynqmp secure"
12 which is used for zynqmp secure image verification.
13 The secure image is a xilinx specific BOOT.BIN with
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/android-tools/android-tools/core/
H A D0008-adb-Allow-adbd-to-be-ran-as-root.patch17 int secure = 0;
21 /* run adbd in secure mode if ro.secure is set and
/openbmc/linux/Documentation/devicetree/bindings/iommu/
H A Dqcom,iommu.yaml16 to non-secure vs secure interrupt line.
49 qcom,iommu-secure-id:
52 The SCM secure ID of the IOMMU instance.
113 qcom,iommu-secure-id = <17>;
/openbmc/qemu/roms/
H A Dedk2-build.config49 [build.ovmf.i386.secure]
50 desc = ovmf build (32-bit, secure boot)
57 cpy1 = FV/OVMF_CODE.fd edk2-i386-secure-code.fd
71 [build.ovmf.x86_64.secure]
72 desc = ovmf build (64-bit, secure boot)
79 cpy1 = FV/OVMF_CODE.fd edk2-x86_64-secure-code.fd

12345678910>>...25