Home
last modified time | relevance | path

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

123

/rk3399_rockchip-uboot/drivers/misc/
H A DMakefile60 obj-$(CONFIG_ROCKCHIP_RK3308) += rk3308-secure-otp.o
61 obj-$(CONFIG_ROCKCHIP_PX30) += px30-secure-otp.o
62 obj-$(CONFIG_ROCKCHIP_RK3328) += rk3328-secure-otp.o
63 obj-$(CONFIG_ROCKCHIP_RK3568) += rk3568-secure-otp.o
64 obj-$(CONFIG_ROCKCHIP_RV1103B) += rv1103b-secure-otp.o
65 obj-$(CONFIG_ROCKCHIP_RV1106) += rv1106-secure-otp.o
66 obj-$(CONFIG_ROCKCHIP_RV1126) += rv1126-secure-otp.o
67 obj-$(CONFIG_ROCKCHIP_RK3506) += rk3506-secure-otp.o
68 obj-$(CONFIG_ROCKCHIP_RK3588) += rk3588-secure-otp.o
69 obj-$(CONFIG_ROCKCHIP_RK3528) += rk3528-secure-otp.o
[all …]
/rk3399_rockchip-uboot/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 …]
/rk3399_rockchip-uboot/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))
/rk3399_rockchip-uboot/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.
H A Dnonsec_virt.S52 @ Obtain a secure stack
78 @ FIQ preserved for secure mode
103 movs pc, lr @ ERET to non-secure
200 mcr p15, 0, r1, c12, c0, 1 @ set MVBAR to secure vectors
/rk3399_rockchip-uboot/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()
H A DKconfig110 and an optional customer programmable secure boot.
126 programmable secure boot.
140 If a high secure (HS) device type is being used, this config
143 authenticated) and the code. See the doc/README.ti-secure
160 region on secure devices.
168 reserved EMIF region set aside for secure OS needs that will be protected
H A Dconfig_secure.mk32 ifneq ($(wildcard $(TI_SECURE_DEV_PKG)/scripts/secure-binary-image.sh),)
33 cmd_omapsecureimg = $(TI_SECURE_DEV_PKG)/scripts/secure-binary-image.sh \
/rk3399_rockchip-uboot/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 */
/rk3399_rockchip-uboot/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 …]
/rk3399_rockchip-uboot/board/freescale/ls1043ardb/
H A DKconfig17 bool "Enable secure address for PSCI image"
21 PSCI image can be re-located to secure RAM.
/rk3399_rockchip-uboot/arch/arm/dts/
H A Drv1126b-u-boot.dtsi20 secure-otp@20b10000 {
21 compatible = "rockchip,rv1126b-secure-otp";
34 secure;
H A Drv1103b-u-boot.dtsi18 secure-otp@20790000 {
19 compatible = "rockchip,rv1103b-secure-otp";
H A Drk3506-u-boot.dtsi17 secure-otp@ff520000 {
18 compatible = "rockchip,rk3506-secure-otp";
H A Dpx30-u-boot.dtsi18 secure-otp@ff110000 {
19 compatible = "rockchip,px30-secure-otp";
H A Drk3308-u-boot.dtsi18 secure-otp@ff2a8000 {
19 compatible = "rockchip,rk3308-secure-otp";
H A Drk3562-u-boot.dtsi18 secure-otp@ff920000 {
19 compatible = "rockchip,rk3562-secure-otp";
H A Drv1106-u-boot.dtsi18 secure-otp@ff3fd8000 {
19 compatible = "rockchip,rv1106-secure-otp";
H A Drk3528-u-boot.dtsi18 secure-otp@ffcd0000 {
19 compatible = "rockchip,rk3528-secure-otp";
/rk3399_rockchip-uboot/arch/arm/mach-at91/include/mach/
H A Dsama5_sfr.h21 u32 secure; /* 0x28: Security Configuration Register */ member
/rk3399_rockchip-uboot/arch/arm/cpu/armv8/fsl-layerscape/doc/
H A DREADME.soc40 - Enhanced secure digital host controller (eSDXC/eMMC)
81 - Enhanced secure digital host controller (eSDXC/eMMC)
89 - Service processor (SP) provides pre-boot initialization and secure-boot
119 - Two enhanced secure digital host controllers
167 - Enhanced secure digital host controller (eSDXC/eMMC)
208 - Enhanced secure digital host controller (eSDXC/eMMC)
216 - Service processor (SP) provides pre-boot initialization and secure-boot
/rk3399_rockchip-uboot/arch/arm/mach-imx/
H A DKconfig34 This option enables the support for secure boot (HAB).
55 Freescale secure boot mechanism. This command encapsulates and
/rk3399_rockchip-uboot/board/freescale/common/
H A DKconfig17 This option enables two commands used for secure booting:
/rk3399_rockchip-uboot/doc/SPL/
H A DREADME.spl-secure-boot14 the main u-boot image. For secure boot process on these platforms ROM verifies
/rk3399_rockchip-uboot/arch/arm/cpu/armv8/fsl-layerscape/
H A Dspl.c91 #error Need secure RAM for PPA in board_init_f()

123