| /f-stack/freebsd/contrib/device-tree/Bindings/arm/ |
| H A 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
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 …]
|
| H A D | juno,scpi.txt | 8 - compatible : should be "arm,juno-sram-ns" for Non-secure SRAM
14 - compatible : should be "arm,juno-scp-shmem" for Non-secure SRAM based
|
| H A D | pmu.yaml | 80 secure-reg-access:
85 any setup required that is only possible in ARMv7 secure
91 in Non-secure state.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/crypto/ |
| H A D | inside-secure-safexcel.txt | 4 - 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";
|
| /f-stack/freebsd/contrib/device-tree/Bindings/iommu/ |
| H A D | qcom,iommu.txt | 6 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>;
|
| H A D | msm,iommu-v0.txt | 12 support secure mode two interrupts must be specified, for non-secure and
13 secure mode, in that order. For instances that don't support secure mode a
|
| H A D | arm,smmu.yaml | 76 maximum: 260 # 2 secure, 2 non-secure, and up to 256 perf counters
110 calxeda,smmu-secure-config-access:
113 Enable proper handling of buggy implementations that always use secure
114 access to SMMU configuration registers. In this case non-secure aliases of
115 secure registers have to be used during SMMU configuration.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/arm/amlogic/ |
| H A D | amlogic,meson-gx-ao-secure.yaml | 5 $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";
|
| /f-stack/freebsd/contrib/device-tree/Bindings/arm/samsung/ |
| H A D | samsung-secure-firmware.yaml | 4 $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";
|
| /f-stack/freebsd/contrib/device-tree/Bindings/nvmem/ |
| H A D | st,stm32-romem.yaml | 32 st,non-secure-otp:
34 This property explicits a factory programmed area that both secure
35 and non-secure worlds can access. It is needed when, by default, the
36 related area can only be reached by the secure world.
59 st,non-secure-otp;
|
| H A D | amlogic-efuse.txt | 7 - secure-monitor: phandle to the secure-monitor node
20 secure-monitor = <&sm>;
35 sm: secure-monitor {
|
| /f-stack/freebsd/contrib/device-tree/Bindings/thermal/ |
| H A D | amlogic,thermal.yaml | 31 amlogic,ao-secure:
32 description: phandle to the ao-secure syscon
43 - amlogic,ao-secure
56 amlogic,ao-secure = <&sec_AO>;
|
| /f-stack/freebsd/contrib/device-tree/Bindings/rng/ |
| H A D | omap_rng.txt | 9 - "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";
|
| H A D | omap3_rom_rng.txt | 3 Secure SoCs may provide RNG via secure ROM calls like Nokia N900 does. The
4 implementation can depend on the SoC secure ROM used.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/firmware/meson/ |
| H A D | meson_sm.txt | 6 Required properties for the secure monitor node:
12 sm: secure-monitor {
|
| /f-stack/freebsd/contrib/device-tree/Bindings/misc/ |
| H A D | brcm,kona-smc.txt | 4 used for non-secure to secure communications.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/mailbox/ |
| H A D | ti,secure-proxy.txt | 4 The Texas Instruments' secure proxy is a mailbox controller that has
15 - compatible: Shall be "ti,am654-secure-proxy"
32 compatible = "ti,am654-secure-proxy";
|
| /f-stack/freebsd/contrib/device-tree/Bindings/soc/rockchip/ |
| H A D | grf.txt | 7 - GRF, used for general non-secure system,
8 - SGRF, used for general secure system,
14 - GRF, used for general non-secure system,
15 - SGRF, used for general secure system,
|
| /f-stack/freebsd/contrib/device-tree/Bindings/timer/ |
| H A D | ti,timer.txt | 32 - ti,timer-secure: Indicates the timer is reserved on a secure OMAP device
43 ti,timer-secure;
|
| /f-stack/freebsd/contrib/device-tree/Bindings/firmware/ |
| H A 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
|
| /f-stack/freebsd/contrib/device-tree/Bindings/power/ |
| H A D | amlogic,meson-sec-pwrc.yaml | 16 of secure-monitor.
32 secure-monitor {
|
| /f-stack/freebsd/contrib/openzfs/tests/zfs-tests/tests/functional/history/ |
| H A D | history_002_pos.ksh | 85 aclinherit secure aclinherit passthrough
113 aclinherit secure aclinherit passthrough
141 aclinherit secure aclinherit passthrough
|
| /f-stack/freebsd/contrib/device-tree/Bindings/sram/ |
| H A D | sram.yaml | 170 // declaration. These nodes are of two types depending upon secure or
171 // non-secure execution environment.
249 // Allwinner's A80 SoC uses part of the secure sram for hotplugging of the
254 // Also there are no "secure-only" properties. The implementation should
257 // 256 KiB secure SRAM at 0x20000
|
| /f-stack/freebsd/contrib/openzfs/include/sys/ |
| H A D | vdev_trim.h | 38 boolean_t secure);
|
| /f-stack/freebsd/contrib/device-tree/Bindings/arm/firmware/ |
| H A D | tlm,trusted-foundations.txt | 4 Boards that use the Trusted Foundations secure monitor can signal its
|