Home
last modified time | relevance | path

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

12345678910>>...45

/OK3568_Linux_fs/kernel/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
26 still be processed unmodified by existing Non-secure software (and in
32 secure- bindings only need to be used where both the Secure and Normal
38 - secure-status : specifies whether the device is present and usable
39 in the secure world. The combination of this with "status" allows
41 specified. If "secure-status" is not specified it defaults to the
47 secure-status = "okay"; /* visible in both */
[all …]
/OK3568_Linux_fs/u-boot/doc/
H A DREADME.ti-secure1 README on how boot images are created for secure TI devices
7 a secure device from TI, the initial public software image must be signed
11 from Texas Instruments. The tools used to generate boot images for secure
12 devices are part of a secure development package (SECDEV) that can be
17 The secure development package is access controlled due to NDA and export
31 warning is issued during the build to indicate that a final secure
38 This is called as part of the SPL/u-boot build process. As the secure
39 boot image formats and requirements differ between secure SOC from TI,
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
[all …]
/OK3568_Linux_fs/u-boot/spl/drivers/misc/
H A D.rk3568-secure-otp.o.cmd
/OK3568_Linux_fs/kernel/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";
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/iommu/
H A Dqcom,iommu.txt6 to non-secure vs secure interrupt line.
31 - qcom,iommu-secure-id : secure-id.
37 - "qcom,msm-iommu-v1-ns" : non-secure context bank
38 - "qcom,msm-iommu-v1-sec" : secure context bank
46 for routing of context bank irq's to secure vs non-
47 secure lines. (Ie. if the iommu contains secure
63 qcom,iommu-secure-id = <17>;
89 qcom,iommu-secure-id = <18>;
/OK3568_Linux_fs/u-boot/drivers/misc/
H A DMakefile59 obj-$(CONFIG_$(SPL_TPL_)ROCKCHIP_SECURE_OTP) += rk3308-secure-otp.o
63 obj-$(CONFIG_$(SPL_TPL_)ROCKCHIP_SECURE_OTP) += px30-secure-otp.o
67 obj-$(CONFIG_$(SPL_TPL_)ROCKCHIP_SECURE_OTP) += rk3328-secure-otp.o
71 obj-$(CONFIG_$(SPL_TPL_)ROCKCHIP_SECURE_OTP) += rk3568-secure-otp.o
75 obj-$(CONFIG_$(SPL_TPL_)ROCKCHIP_SECURE_OTP) += rv1106-secure-otp.o
79 obj-$(CONFIG_$(SPL_TPL_)ROCKCHIP_SECURE_OTP) += rv1126-secure-otp.o
83 obj-$(CONFIG_$(SPL_TPL_)ROCKCHIP_SECURE_OTP) += rk3588-secure-otp.o
87 obj-$(CONFIG_$(SPL_TPL_)ROCKCHIP_SECURE_OTP) += rk3528-secure-otp.o
91 obj-$(CONFIG_$(SPL_TPL_)ROCKCHIP_SECURE_OTP) += rk3562-secure-otp.o
/OK3568_Linux_fs/kernel/Documentation/powerpc/
H A Dultravisor.rst56 process is running in secure mode, MSR(S) bit 41. MSR(S)=1, process
57 is in secure mode, MSR(s)=0 process is in normal mode.
63 the VM it is returning to is secure.
101 * Memory is partitioned into secure and normal memory. Only processes
102 that are running in secure mode can access secure memory.
104 * The hardware does not allow anything that is not running secure to
105 access secure memory. This means that the Hypervisor cannot access
110 * I/O systems are not allowed to directly address secure memory. This
117 * When a process is running in secure mode all hypercalls
120 * When a process is in secure mode all interrupts go to the
[all …]
/OK3568_Linux_fs/buildroot/package/optee-client/
H A DConfig.in6 Enable the OP-TEE client package that brings non-secure
11 applications hosted in the OP-TEE OS secure world. The
12 supplicant provides services hosted by the non-secure world
13 and invoked by the secure world.
20 string "Path for normal world OS secure storage"
23 Path to storage area for secure storage based on the
/OK3568_Linux_fs/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.
/OK3568_Linux_fs/kernel/drivers/gpu/drm/amd/amdgpu/
H A Damdgpu_ib.c137 bool secure; in amdgpu_ib_schedule() local
232 secure = false; in amdgpu_ib_schedule()
234 secure = ib->flags & AMDGPU_IB_FLAGS_SECURE; in amdgpu_ib_schedule()
235 amdgpu_ring_emit_frame_cntl(ring, true, secure); in amdgpu_ib_schedule()
242 if (secure != !!(ib->flags & AMDGPU_IB_FLAGS_SECURE)) { in amdgpu_ib_schedule()
243 amdgpu_ring_emit_frame_cntl(ring, false, secure); in amdgpu_ib_schedule()
244 secure = !secure; in amdgpu_ib_schedule()
245 amdgpu_ring_emit_frame_cntl(ring, true, secure); in amdgpu_ib_schedule()
254 amdgpu_ring_emit_frame_cntl(ring, false, secure); in amdgpu_ib_schedule()
/OK3568_Linux_fs/u-boot/arch/arm/cpu/
H A Du-boot.lds23 * If CONFIG_ARMV7_SECURE_BASE is true, secure code will not
27 * address for secure code.
29 * If CONFIG_ARMV7_SECURE_BASE is undefined, the secure zone will
31 * were used in secure code. The absolute addresses of the secure
52 /* Align the secure section only if we're going to use it in situ */
104 "Error: secure section exceeds secure memory size");
109 /* Reset VMA but don't allocate space if we have secure SRAM */
/OK3568_Linux_fs/u-boot/arch/arm/mach-omap2/
H A Dutils.c48 const char *secure; in omap_set_fastboot_secure() local
53 secure = "EMU"; in omap_set_fastboot_secure()
56 secure = "HS"; in omap_set_fastboot_secure()
59 secure = "GP"; in omap_set_fastboot_secure()
62 secure = NULL; in omap_set_fastboot_secure()
66 env_set("fastboot.secure", secure); in omap_set_fastboot_secure()
/OK3568_Linux_fs/u-boot/include/
H A Damp.h18 #define MAP_SECURE(secure) ((secure) ? 0 : 1) argument
25 #define PE_STATE(aarch64, hyp, thumb, secure) \ argument
29 ((MAP_SECURE(secure) & 0x1) << MODE_SECURE_SHIFT))
/OK3568_Linux_fs/u-boot/arch/arm/cpu/armv8/
H A DKconfig44 menu "ARMv8 secure monitor firmware"
46 bool "Enable ARMv8 secure monitor firmware framework support"
50 This framework is aimed at making secure monitor firmware load
54 - Address of secure firmware.
55 - Address to hold the return address from secure firmware.
58 - The target exception level that secure monitor firmware will
62 bool "Enable ARMv8 secure monitor firmware framework support for SPL"
69 bool "PSCI implementation in secure monitor firmware"
72 This config enables the ARMv8 PSCI implementation in secure monitor
77 bool "ARMv8 secure monitor firmware ERET address byteorder swap"
[all …]
/OK3568_Linux_fs/external/security/bin/
H A DRelease_List_EN.md11 …hen using security partitions for secure storage, data is synchronized every time it is written，it…
35 1. Support read secure boot enable flag.
36 2. Support read secure boot public key hash.
/OK3568_Linux_fs/buildroot/board/qemu/arm-vexpress-tz/
H A Dreadme.txt2 OP-TEE running in the TrustZone secure world and a Linux based
3 OS running in the non-secure world. The board configuration enables
15 -machine virt -machine secure=on -cpu cortex-a15 \
35 this image loads the OP-TEE secure world (ARMv7-A BL32 stage) and the U-boot as
36 non-secure bootloader (BL33 stage).
47 Secure boot stages and/or secure runtime services may use a serial link for
60 -machine virt -machine secure=on -cpu cortex-a15 \
73 and again for the secure console
80 One can debug the OP-TEE secure world using GDB through the QEMU host.
90 -machine virt -machine secure=on -cpu cortex-a15 \
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/nvmem/
H A Damlogic-efuse.txt7 - secure-monitor: phandle to the secure-monitor node
20 secure-monitor = <&sm>;
35 sm: secure-monitor {
/OK3568_Linux_fs/buildroot/package/optee-examples/
H A DConfig.in11 implementation of OP-TEE non-secure client applications and
12 secure trusted applications. OP-TEE examples is a
18 non-secure filesystem/directory into the secure world for
/OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-dbs/postgresql/files/
H A D0001-Properly-NULL-terminate-GSS-receive-buffer-on-error-.patch31 src/interfaces/libpq/fe-secure-gssapi.c | 3 ++-
34 diff --git a/src/interfaces/libpq/fe-secure-gssapi.c b/src/interfaces/libpq/fe-secure-gssapi.c
36 --- a/src/interfaces/libpq/fe-secure-gssapi.c
37 +++ b/src/interfaces/libpq/fe-secure-gssapi.c
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/rng/
H A Domap_rng.txt9 - "inside-secure,safexcel-eip76" for SoCs with EIP76 IP block
14 Used for "ti,omap4-rng" and "inside-secure,safexcel-eip76"
16 "inside-secure,safexcel-eip76" compatible, the second clock is
34 compatible = "inside-secure,safexcel-eip76";
/OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-devtools/android-tools/android-tools/core/
H A D0008-adb-Allow-adbd-to-be-ran-as-root.patch15 int secure = 0;
19 /* run adbd in secure mode if ro.secure is set and
/OK3568_Linux_fs/kernel/arch/arm/mach-omap2/
H A DMakefile17 secure-common = omap-smc.o omap-secure.o
20 obj-$(CONFIG_ARCH_OMAP3) += $(omap-2-3-common) $(hwmod-common) $(secure-common)
21 obj-$(CONFIG_ARCH_OMAP4) += $(hwmod-common) $(secure-common)
22 obj-$(CONFIG_SOC_AM33XX) += $(hwmod-common) $(secure-common)
23 obj-$(CONFIG_SOC_OMAP5) += $(hwmod-common) $(secure-common)
24 obj-$(CONFIG_SOC_AM43XX) += $(hwmod-common) $(secure-common)
25 obj-$(CONFIG_SOC_DRA7XX) += $(hwmod-common) $(secure-common)
/OK3568_Linux_fs/kernel/fs/
H A Danon_inodes.c82 bool secure) in __anon_inode_getfile() argument
90 if (secure) { in __anon_inode_getfile()
155 bool secure) in __anon_inode_getfd() argument
166 secure); in __anon_inode_getfd()
/OK3568_Linux_fs/kernel/arch/arm/crypto/
H A DKconfig17 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
27 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
37 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
46 SHA-256 secure hash standard (DFIPS 180-2) implemented
54 SHA-256 secure hash standard (DFIPS 180-2) implemented
62 SHA-512 secure hash standard (DFIPS 180-2) implemented
109 Use a faster and more secure NEON based implementation of AES in CBC,
/OK3568_Linux_fs/kernel/Documentation/ABI/testing/
H A Dsysfs-secvar5 secureboot, thereby secure variables. It exposes interface
6 for reading/writing the secure variables
11 Description: This directory lists all the secure variables that are supported
24 Description: Each secure variable is represented as a directory named as

12345678910>>...45