| /linux-6.1.9/lib/ |
| D | test_objagg.c | 29 struct world { struct
46 static struct objagg_obj *world_obj_get(struct world *world, in world_obj_get() argument
60 if (!world->key_refs[key_id_index(key_id)]) { in world_obj_get()
61 world->objagg_objs[key_id_index(key_id)] = objagg_obj; in world_obj_get()
62 } else if (world->objagg_objs[key_id_index(key_id)] != objagg_obj) { in world_obj_get()
68 world->key_refs[key_id_index(key_id)]++; in world_obj_get()
76 static void world_obj_put(struct world *world, struct objagg *objagg, in world_obj_put() argument
81 if (!world->key_refs[key_id_index(key_id)]) in world_obj_put()
83 objagg_obj = world->objagg_objs[key_id_index(key_id)]; in world_obj_put()
85 world->key_refs[key_id_index(key_id)]--; in world_obj_put()
[all …]
|
| /linux-6.1.9/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 …]
|
| /linux-6.1.9/scripts/kconfig/tests/preprocess/builtin_func/ |
| D | expected_stderr | 1 Kconfig:8: hello world 1
2 Kconfig:18: hello world 3
3 Kconfig:22: hello world 4
|
| D | Kconfig | 4 $(info,hello world 0)
8 $(warning-if,y,hello world 1)
18 $(warning,$(shell,echo hello world 3))
|
| D | expected_stdout | 1 hello world 0
|
| /linux-6.1.9/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.
|
| /linux-6.1.9/drivers/firmware/arm_ffa/ |
| D | Kconfig | 11 the Secure world and Normal world. It also leverages the
|
| /linux-6.1.9/Documentation/staging/ |
| D | tee.rst | 152 User space Kernel Secure world
172 RPC (Remote Procedure Call) are requests from secure world to kernel driver
190 There are two kinds of notifications that secure world can use to make
191 normal world aware of some event.
200 this is only usable when secure world is entered with a yielding call via
202 world interrupt handlers.
211 special meaning. When this value is received it means that normal world is
214 building block for OP-TEE OS in secure world to implement the top half and
|
| /linux-6.1.9/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)
|
| /linux-6.1.9/scripts/kconfig/tests/preprocess/escape/ |
| D | expected_stderr | 1 Kconfig:9: hello, world
|
| D | Kconfig | 9 $(warning,hello$(comma) world)
|
| /linux-6.1.9/drivers/of/unittest-data/ |
| D | testcases_common.dtsi | 7 prop-remove = "world";
|
| /linux-6.1.9/Documentation/core-api/wrappers/ |
| D | atomic_bitops.rst | 2 This is a simple wrapper to bring atomic_bitops.txt into the RST world
|
| D | atomic_t.rst | 2 This is a simple wrapper to bring atomic_t.txt into the RST world
|
| D | memory-barriers.rst | 2 This is a simple wrapper to bring memory-barriers.txt into the RST world
|
| /linux-6.1.9/arch/arm64/boot/dts/arm/ |
| D | corstone1000.dtsi | 148 secure-status = "okay"; /* secure-world-only */
160 secure-status = "okay"; /* secure-world-only */
|
| /linux-6.1.9/drivers/parport/ |
| D | TODO-parport | 14 with (maybe just log) whatever the printer wants to tell the world.
|
| /linux-6.1.9/fs/ext2/ |
| D | Kconfig | 28 groups beyond the owner/group/world scheme.
|
| /linux-6.1.9/Documentation/devicetree/bindings/nvmem/ |
| D | st,stm32-romem.yaml | 39 related area can only be reached by the secure world.
|
| /linux-6.1.9/Documentation/devicetree/bindings/arm/firmware/ |
| D | linaro,optee-tz.yaml | 30 This interrupt which is used to signal an event by the secure world
|
| /linux-6.1.9/fs/9p/ |
| D | Kconfig | 28 groups beyond the owner/group/world scheme.
|
| /linux-6.1.9/fs/ceph/ |
| D | Kconfig | 37 groups beyond the owner/group/world scheme.
|
| /linux-6.1.9/Documentation/admin-guide/sysctl/ |
| D | fs.rst | 211 in world writable sticky directories, unless they are owned by the
223 time-of-check-time-of-use race, most commonly seen in world-writable
249 don't own in world writable sticky directories, unless they are
259 time-of-check-time-of-use race, most commonly seen in world-writable
269 a sticky world-writable directory, or when the uid of the symlink and
|
| /linux-6.1.9/fs/jfs/ |
| D | Kconfig | 18 groups beyond the owner/group/world scheme.
|
| /linux-6.1.9/Documentation/driver-api/memory-devices/ |
| D | ti-emif.rst | 48 Interface to the external world
|