Searched full:world (Results 1 – 25 of 125) sorted by relevance
12345
| /Documentation/devicetree/bindings/arm/ |
| D | secure.txt | 1 * ARM Secure world bindings
6 world or the Secure world. However some devicetree consumers are
13 The general principle of the naming scheme for Secure world bindings
14 is that any property that needs a different value in the Secure world
19 world value is the same as specified for the Normal world by the
30 world consumers (like kernels that run entirely in Secure) to simply
31 describe the view of Secure world using the standard bindings. These
33 world views need to be described in a single device tree.
35 Valid Secure world properties
39 in the secure world. The combination of this with "status" allows
[all …]
|
| /Documentation/devicetree/bindings/iio/ |
| D | mount-matrix.txt | 13 that produce three-dimensional data in relation to the world where it is
41 external world, the environment where the device is deployed. Usually the data
43 to this world. When using the mounting matrix, the sensor and device orientation
45 world.
47 Device-to-world examples for some three-dimensional sensor types:
49 - Accelerometers have their world frame of reference toward the center of
53 this point. Up and down in the world relative to the device frame of
93 - Magnetometers (compasses) have their world frame of reference relative to the
94 geomagnetic field. The system orientation vis-a-vis the world is defined with
160 space, relative to the device or world point of reference.
|
| /Documentation/tee/ |
| D | op-tee.rst | 36 User space Kernel Secure world
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
75 normal world aware of some event.
84 this is only usable when secure world is entered with a yielding call via
86 world interrupt handlers.
95 special meaning. When this value is received it means that normal world is
98 building block for OP-TEE OS in secure world to implement the top half and
|
| /Documentation/kbuild/ |
| D | kconfig-macro-language.rst | 181 For example, $(shell echo hello, world) runs the command "echo hello, world".
182 Likewise, $(info hello, world) prints "hello, world" to stdout. You could say
188 $(shell, echo hello, world)
194 $(shell, echo hello$(comma) world)
|
| /Documentation/doc-guide/ |
| D | hello.dot | 2 Hello -- World
|
| /Documentation/core-api/wrappers/ |
| D | atomic_t.rst | 2 This is a simple wrapper to bring atomic_t.txt into the RST world
|
| D | atomic_bitops.rst | 2 This is a simple wrapper to bring atomic_bitops.txt into the RST world
|
| D | memory-barriers.rst | 2 This is a simple wrapper to bring memory-barriers.txt into the RST world
|
| /Documentation/translations/ko_KR/core-api/wrappers/ |
| D | memory-barriers.rst | 2 This is a simple wrapper to bring memory-barriers.txt into the RST world
|
| /Documentation/translations/sp_SP/wrappers/ |
| D | memory-barriers.rst | 3 translation) into the RST world until such a time as that file can be
|
| /Documentation/arch/arm64/ |
| D | cpu-hotplug.rst | 8 CPU hotplug in the arm64 world is commonly used to describe the kernel taking
24 In the arm64 world CPUs are not a single device but a slice of the system.
|
| /Documentation/admin-guide/sysctl/ |
| D | fs.rst | 180 in world writable sticky directories, unless they are owned by the
192 time-of-check-time-of-use race, most commonly seen in world-writable
218 don't own in world writable sticky directories, unless they are
228 time-of-check-time-of-use race, most commonly seen in world-writable
238 a sticky world-writable directory, or when the uid of the symlink and
|
| /Documentation/devicetree/bindings/clock/ |
| D | mediatek,mtmips-sysc.yaml | 16 for the rest of the world.
|
| /Documentation/devicetree/bindings/arm/firmware/ |
| D | linaro,optee-tz.yaml | 30 This interrupt which is used to signal an event by the secure world
|
| /Documentation/admin-guide/acpi/ |
| D | initrd_table_override.rst | 63 Store("HELLO WORLD", debug)
95 [ 1.272091] [ACPI Debug] String [0x0B] "HELLO WORLD"
|
| /Documentation/networking/ |
| D | ipsec.rst | 9 deploy various IPsec configuration in real world production environment.
|
| /Documentation/dev-tools/kunit/api/ |
| D | functionredirection.rst | 80 KUNIT_EXPECT_STREQ(test, str, "Hello World!");
109 send_data_to_hardware("Hello World!"); /* Succeeds */
|
| /Documentation/devicetree/bindings/nvmem/ |
| D | st,stm32-romem.yaml | 44 related area can only be reached by the secure world.
|
| /Documentation/devicetree/bindings/firmware/ |
| D | intel,stratix10-svc.txt | 10 communication with SDM, only the secure world of software (EL3, Exception
|
| /Documentation/devicetree/bindings/dma/ |
| D | qcom,adm.yaml | 58 description: indicates the security domain identifier used in the secure world.
|
| D | qcom,bam-dma.yaml | 66 secure world.
|
| /Documentation/driver-api/memory-devices/ |
| D | ti-emif.rst | 48 Interface to the external world
|
| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-intro.rst | 42 world.
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | mediatek,gce-props.yaml | 41 in the secure world completes a task. However, in MT8195, event ID 855
|
| /Documentation/arch/arm/ |
| D | firmware.rst | 8 world, which changes the way some things have to be initialized. This makes
|
12345