/linux-6.12.1/Documentation/devicetree/bindings/arm/ |
D | secure.txt | 15 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 …]
|
/linux-6.12.1/Documentation/arch/powerpc/ |
D | ultravisor.rst | 56 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 …]
|
/linux-6.12.1/drivers/gpu/drm/amd/amdgpu/ |
D | amdgpu_ib.c | 138 bool secure, init_shadow; in amdgpu_ib_schedule() local 247 secure = false; in amdgpu_ib_schedule() 249 secure = ib->flags & AMDGPU_IB_FLAGS_SECURE; in amdgpu_ib_schedule() 250 amdgpu_ring_emit_frame_cntl(ring, true, secure); in amdgpu_ib_schedule() 257 if (secure != !!(ib->flags & AMDGPU_IB_FLAGS_SECURE)) { in amdgpu_ib_schedule() 258 amdgpu_ring_emit_frame_cntl(ring, false, secure); in amdgpu_ib_schedule() 259 secure = !secure; in amdgpu_ib_schedule() 260 amdgpu_ring_emit_frame_cntl(ring, true, secure); in amdgpu_ib_schedule() 269 amdgpu_ring_emit_frame_cntl(ring, false, secure); in amdgpu_ib_schedule()
|
/linux-6.12.1/arch/arm/mach-omap2/ |
D | Makefile | 16 secure-common = omap-smc.o omap-secure.o 19 obj-$(CONFIG_ARCH_OMAP3) += $(omap-2-3-common) $(hwmod-common) $(secure-common) 20 obj-$(CONFIG_ARCH_OMAP4) += $(secure-common) 21 obj-$(CONFIG_SOC_AM33XX) += $(secure-common) 22 obj-$(CONFIG_SOC_OMAP5) += $(secure-common) 23 obj-$(CONFIG_SOC_AM43XX) += $(secure-common) 24 obj-$(CONFIG_SOC_DRA7XX) += $(secure-common)
|
/linux-6.12.1/Documentation/tee/ |
D | op-tee.rst | 23 separate secure co-processor. 56 RPC (Remote Procedure Call) are requests from secure world to kernel driver 74 There are two kinds of notifications that secure world can use to make 79 2. Asynchronous notifications delivered with a combination of a non-secure 80 edge-triggered interrupt and a fast call from the non-secure interrupt 84 this is only usable when secure world is entered with a yielding call via 85 ``OPTEE_SMC_CALL_WITH_ARG``. This excludes such notifications from secure 88 An asynchronous notification is delivered via a non-secure edge-triggered 98 building block for OP-TEE OS in secure world to implement the top half and
|
D | tee.rst | 12 A TEE is a trusted OS running in some secure environment, for example, 13 TrustZone on ARM CPUs, or a separate secure co-processor etc. A TEE driver
|
/linux-6.12.1/arch/s390/crypto/ |
D | Kconfig | 22 SHA-384 and SHA-512 secure hash algorithms (FIPS 180) 33 SHA-1 secure hash algorithm (FIPS 180) 44 SHA-224 and SHA-256 secure hash algorithms (FIPS 180) 55 SHA3-224 and SHA3-256 secure hash algorithms (FIPS 202) 66 SHA3-384 and SHA3-512 secure hash algorithms (FIPS 202)
|
/linux-6.12.1/arch/arm64/boot/dts/arm/ |
D | corstone1000.dtsi | 145 secure-status = "okay"; /* secure-world-only */ 157 secure-status = "okay"; /* secure-world-only */
|
/linux-6.12.1/Documentation/driver-api/firmware/ |
D | other_interfaces.rst | 25 higher than the kernel is granted. Such secure features include 31 drivers to request access to the secure features. The requests are queued 33 of the requests on to a secure monitor (EL3).
|
/linux-6.12.1/arch/mips/crypto/ |
D | Kconfig | 39 SHA-1 secure hash algorithm (FIPS 180) 49 SHA-224 and SHA-256 secure hash algorithms (FIPS 180) 59 SHA-384 and SHA-512 secure hash algorithms (FIPS 180)
|
/linux-6.12.1/arch/arm64/boot/dts/tesla/ |
D | fsd.dtsi | 378 interrupts = <GIC_SPI 438 IRQ_TYPE_LEVEL_HIGH>, /* Global secure fault */ 379 <GIC_SPI 439 IRQ_TYPE_LEVEL_HIGH>, /* Global non-secure fault */ 380 <GIC_SPI 451 IRQ_TYPE_LEVEL_HIGH>, /* Combined secure interrupt */ 381 <GIC_SPI 450 IRQ_TYPE_LEVEL_HIGH>, /* Combined non-secure interrupt */ 386 /* Per context non-secure context interrupts, 0-3 interrupts */ 398 interrupts = <GIC_SPI 321 IRQ_TYPE_LEVEL_HIGH>, /* Global secure fault */ 399 <GIC_SPI 322 IRQ_TYPE_LEVEL_HIGH>, /* Global non-secure fault */ 400 <GIC_SPI 346 IRQ_TYPE_LEVEL_HIGH>, /* Combined secure interrupt */ 401 <GIC_SPI 345 IRQ_TYPE_LEVEL_HIGH>, /* Combined non-secure interrupt */ 410 /* Per context non-secure context interrupts, 0-7 interrupts */ [all …]
|
/linux-6.12.1/arch/arm64/boot/dts/amlogic/ |
D | amlogic-a4-common.dtsi | 71 sec_ao: ao-secure@10220 { 72 compatible = "amlogic,a4-ao-secure", 73 "amlogic,meson-gx-ao-secure",
|
D | amlogic-t7.dtsi | 121 sm: secure-monitor { 198 sec_ao: ao-secure@10220 { 199 compatible = "amlogic,t7-ao-secure", 200 "amlogic,meson-gx-ao-secure",
|
/linux-6.12.1/arch/arm64/crypto/ |
D | Kconfig | 45 SHA-1 secure hash algorithm (FIPS 180) 54 SHA-224 and SHA-256 secure hash algorithms (FIPS 180) 64 SHA-224 and SHA-256 secure hash algorithms (FIPS 180) 73 SHA-384 and SHA-512 secure hash algorithms (FIPS 180) 83 SHA-384 and SHA-512 secure hash algorithms (FIPS 180) 94 SHA-3 secure hash algorithms (FIPS 202) 105 SM3 (ShangMi 3) secure hash function (OSCCA GM/T 0004-2012) 116 SM3 (ShangMi 3) secure hash function (OSCCA GM/T 0004-2012)
|
/linux-6.12.1/drivers/of/ |
D | kobj.c | 68 bool secure = strncmp(pp->name, "security-", 9) == 0; in __of_add_property_sysfs() local 78 pp->attr.attr.mode = secure ? 0400 : 0444; in __of_add_property_sysfs() 79 pp->attr.size = secure ? 0 : pp->length; in __of_add_property_sysfs()
|
/linux-6.12.1/Documentation/devicetree/bindings/firmware/ |
D | intel,stratix10-svc.txt | 10 communication with SDM, only the secure world of software (EL3, Exception 18 driver also manages secure monitor call (SMC) to communicate with secure monitor
|
/linux-6.12.1/Documentation/security/ |
D | siphash.rst | 7 SipHash is a cryptographically secure PRF -- a keyed hash function -- that 15 indistinguishable from random. You may then use that integer as part of secure 16 sequence numbers, secure cookies, or mask it off for use in a hash table. 21 Keys should always be generated from a cryptographically secure source of 137 same as the siphash ones, or that they are secure; the hsiphash functions still 138 use a less secure reduced-round algorithm and truncate their outputs to 32 144 Keys should always be generated from a cryptographically secure source of
|
/linux-6.12.1/arch/sparc/crypto/ |
D | Kconfig | 45 SHA-1 secure hash algorithm (FIPS 180) 55 SHA-224 and SHA-256 secure hash algorithms (FIPS 180) 65 SHA-384 and SHA-512 secure hash algorithms (FIPS 180)
|
/linux-6.12.1/arch/riscv/crypto/ |
D | Kconfig | 47 SHA-224 and SHA-256 secure hash algorithm (FIPS 180) 58 SHA-384 and SHA-512 secure hash algorithm (FIPS 180) 70 SM3 (ShangMi 3) secure hash function (OSCCA GM/T 0004-2012)
|
/linux-6.12.1/drivers/vfio/ |
D | Kconfig | 11 VFIO provides a framework for secure userspace device drivers. 25 to set up secure DMA context for device access. This interface does 69 considered secure. VFIO No-IOMMU mode enables IOMMU groups for 71 infrastructure in a non-secure mode. Use of this mode will result
|
/linux-6.12.1/drivers/gpu/drm/nouveau/nvkm/falcon/ |
D | v1.c | 30 u32 size, u16 tag, u8 port, bool secure) in nvkm_falcon_v1_load_imem() argument 38 reg = start | BIT(24) | (secure ? BIT(28) : 0); in nvkm_falcon_v1_load_imem()
|
/linux-6.12.1/Documentation/ABI/testing/ |
D | sysfs-secvar | 5 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 32 Description: Each secure variable is represented as a directory named as 60 defined by the secure variable implementation. All data is in
|
/linux-6.12.1/drivers/firmware/ |
D | Kconfig | 150 and manages secure monitor call to communicate with secure monitor 151 software at secure monitor exception level. 231 bool "Trusted Foundations secure monitor support" 235 the market) are booted with the Trusted Foundations secure monitor 236 active, requiring some core operations to be performed by the secure 239 This option allows the kernel to invoke the secure monitor whenever 247 tristate "Turris Mox rWTM secure firmware driver" 254 This driver communicates with the firmware on the Cortex-M3 secure
|
/linux-6.12.1/drivers/gpio/ |
D | gpio-tegra186.c | 107 void __iomem *secure; member 157 return gpio->secure + offset + pin * TEGRA186_GPIO_SCR_PIN_SIZE; in tegra186_gpio_get_secure_base() 162 void __iomem *secure; in tegra186_gpio_is_accessible() local 165 secure = tegra186_gpio_get_secure_base(gpio, pin); in tegra186_gpio_is_accessible() 168 value = readl(secure + TEGRA186_GPIO_VM); in tegra186_gpio_is_accessible() 173 value = __raw_readl(secure + TEGRA186_GPIO_SCR); in tegra186_gpio_is_accessible() 760 base = gpio->secure + port->bank * 0x1000 + 0x800; in tegra186_gpio_init_route_mapping() 845 gpio->secure = devm_platform_ioremap_resource_byname(pdev, "security"); in tegra186_gpio_probe() 846 if (IS_ERR(gpio->secure)) { in tegra186_gpio_probe() 847 gpio->secure = devm_platform_ioremap_resource(pdev, 0); in tegra186_gpio_probe() [all …]
|
/linux-6.12.1/arch/arm/crypto/ |
D | Kconfig | 91 SHA-1 secure hash algorithm (FIPS 180) 102 SHA-1 secure hash algorithm (FIPS 180) 113 SHA-1 secure hash algorithm (FIPS 180) 123 SHA-224 and SHA-256 secure hash algorithms (FIPS 180) 133 SHA-224 and SHA-256 secure hash algorithms (FIPS 180) 143 SHA-384 and SHA-512 secure hash algorithms (FIPS 180)
|