Searched full:hierarchical (Results 1 – 25 of 224) sorted by relevance
123456789
| /kernel/linux/linux-4.19/Documentation/acpi/dsd/ |
| D | data-node-references.txt | 5 Referencing hierarchical data nodes
9 Hierarchical data extension nodes may not be referred to directly, hence this
13 hierarchical data extension [1] keys. Specifically, the hierarchical data
15 parent object i.e. either the device object or another hierarchical data
18 The keys in the hierarchical data nodes shall consist of the name of the node,
24 In case a hierarchical data extensions node has no numerical value, then the
26 "@" character and the number shall be omitted from the hierarchical data
35 hierarchical data extension key "node@1" referring to the NOD1 object
36 and lastly, a hierarchical data extension key "anothernode" referring to
83 [1] Hierarchical Data Extension UUID For _DSD.
[all …]
|
| D | graph.txt | 11 for graphs: property [4] and hierarchical data extensions [5]. The
13 hierarchical data extension supports nodes with references to other
23 the firmware type. In ACPI, fwnodes are _DSD hierarchical data
29 hierarchical data extension array on each depth.
39 All port nodes are located under the device's "_DSD" node in the hierarchical
47 Further on, endpoints are located under the port nodes. The hierarchical
165 [5] Hierarchical Data Extension UUID For _DSD.
166 …<URL:http://www.uefi.org/sites/default/files/resources/_DSD-hierarchical-data-extension-UUID-v1.1.…
|
| /kernel/linux/linux-5.10/Documentation/firmware-guide/acpi/dsd/ |
| D | data-node-references.rst | 5 Referencing hierarchical data nodes
12 Hierarchical data extension nodes may not be referred to directly, hence this
16 hierarchical data extension [1] keys. Specifically, the hierarchical data
18 parent object i.e. either the device object or another hierarchical data
21 The keys in the hierarchical data nodes shall consist of the name of the node,
27 In case a hierarchical data extensions node has no numerical value, then the
29 "@" character and the number shall be omitted from the hierarchical data
38 hierarchical data extension key "node@1" referring to the NOD1 object
39 and lastly, a hierarchical data extension key "anothernode" referring to
87 [1] Hierarchical Data Extension UUID For _DSD.
[all …]
|
| D | graph.rst | 14 for graphs: property [4] and hierarchical data extensions [5]. The
16 hierarchical data extension supports nodes with references to other
26 the firmware type. In ACPI, fwnodes are _DSD hierarchical data
32 hierarchical data extension array on each depth.
42 All port nodes are located under the device's "_DSD" node in the hierarchical
50 Further on, endpoints are located under the port nodes. The hierarchical
168 [5] Hierarchical Data Extension UUID For _DSD.
169 … https://www.uefi.org/sites/default/files/resources/_DSD-hierarchical-data-extension-UUID-v1.1.pdf,
|
| D | leds.rst | 8 Individual LEDs are described by hierarchical data extension [6] nodes under the
11 connected. [3] The hierarchical data nodes are named "led@X", where X is the
28 Under the LED driver device, The first hierarchical data extension package list
107 [6] Hierarchical Data Extension UUID For _DSD.
108 …<URL:https://www.uefi.org/sites/default/files/resources/_DSD-hierarchical-data-extension-UUID-v1.1…
|
| /kernel/linux/linux-4.19/kernel/irq/ |
| D | Kconfig | 71 # Support for hierarchical irq domains
76 # Support for hierarchical fasteoi+edge and fasteoi+level handlers
88 # Generic MSI hierarchical interrupt domain support
|
| /kernel/linux/linux-5.10/kernel/irq/ |
| D | Kconfig | 73 # Support for hierarchical irq domains
78 # Support for hierarchical fasteoi+edge and fasteoi+level handlers
91 # Generic MSI hierarchical interrupt domain support
|
| /kernel/linux/linux-4.19/Documentation/device-mapper/ |
| D | persistent-data.txt | 19 upcoming hierarchical storage target.
73 Currently there is only one data structure, a hierarchical btree.
77 The btree is 'hierarchical' in that you can define it to be composed
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/device-mapper/ |
| D | persistent-data.rst | 23 upcoming hierarchical storage target.
77 Currently there is only one data structure, a hierarchical btree.
81 The btree is 'hierarchical' in that you can define it to be composed
|
| /kernel/linux/linux-5.10/tools/testing/selftests/net/forwarding/ |
| D | ipip_hier_gre.sh | 5 # This test uses hierarchical topology for IP tunneling tests. See
37 ping_test $h1 192.0.2.18 " gre hierarchical"
|
| D | ipip_hier_gre_key.sh | 5 # This test uses hierarchical topology for IP tunneling tests. See
37 ping_test $h1 192.0.2.18 " gre hierarchical with key"
|
| D | ipip_hier_gre_keys.sh | 5 # This test uses hierarchical topology for IP tunneling tests. See
37 ping_test $h1 192.0.2.18 " gre hierarchical with ikey/okey"
|
| /kernel/linux/linux-5.10/block/ |
| D | Kconfig.iosched | 32 bool "BFQ hierarchical scheduling support"
37 Enable hierarchical scheduling in BFQ, using the blkio
|
| /kernel/linux/linux-4.19/kernel/rcu/ |
| D | Kconfig | 121 int "Tree-based hierarchical RCU fanout value"
128 This option controls the fanout of hierarchical implementations
141 int "Tree-based hierarchical RCU leaf-level fanout value"
147 This option controls the leaf-level fanout of hierarchical
|
| /kernel/linux/linux-5.10/drivers/media/dvb-frontends/ |
| D | stv0367_priv.h | 97 FE_TER_HIER_ALPHA_1, /* Hierarchical modulation a = 1*/
98 FE_TER_HIER_ALPHA_2, /* Hierarchical modulation a = 2*/
99 FE_TER_HIER_ALPHA_4 /* Hierarchical modulation a = 4*/
|
| /kernel/linux/linux-5.10/kernel/rcu/ |
| D | Kconfig | 117 int "Tree-based hierarchical RCU fanout value"
124 This option controls the fanout of hierarchical implementations
137 int "Tree-based hierarchical RCU leaf-level fanout value"
145 This option controls the leaf-level fanout of hierarchical
|
| /kernel/linux/linux-4.19/drivers/media/dvb-frontends/ |
| D | stv0367_priv.h | 107 FE_TER_HIER_ALPHA_1, /* Hierarchical modulation a = 1*/
108 FE_TER_HIER_ALPHA_2, /* Hierarchical modulation a = 2*/
109 FE_TER_HIER_ALPHA_4 /* Hierarchical modulation a = 4*/
|
| /kernel/linux/linux-4.19/Documentation/acpi/ |
| D | DSD-properties-rules.txt | 36 Hierarchical Properties Extension UUID definition document [2].
38 Property sets may be hierarchical. That is, a property set may contain
97 [2] http://www.uefi.org/sites/default/files/resources/_DSD-hierarchical-data-extension-UUID-v1.1.pdf
|
| /kernel/linux/linux-5.10/Documentation/firmware-guide/acpi/ |
| D | DSD-properties-rules.rst | 39 Hierarchical Properties Extension UUID definition document [2]_.
41 Property sets may be hierarchical. That is, a property set may contain
100 .. [2] https://www.uefi.org/sites/default/files/resources/_DSD-hierarchical-data-extension-UUID-v1.…
|
| /kernel/linux/linux-4.19/block/ |
| D | Kconfig.iosched | 95 bool "BFQ hierarchical scheduling support"
100 Enable hierarchical scheduling in BFQ, using the blkio
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-codec.rst | 1460 Enables H264 hierarchical coding. Applicable to the H264 encoder.
1462 .. _v4l2-mpeg-video-h264-hierarchical-coding-type:
1468 Specifies the hierarchical coding type. Applicable to the H264
1478 - Hierarchical B coding.
1480 - Hierarchical P coding.
1485 Specifies the number of hierarchical coding layers. Applicable to
3477 Selects the hierarchical coding type for encoding. Possible values are:
3490 - Use the B frame for hierarchical coding.
3492 - Use the P frame for hierarchical coding.
3500 Selects the hierarchical coding layer. In normal encoding
[all …]
|
| /kernel/linux/linux-4.19/Documentation/media/uapi/v4l/ |
| D | extended-controls.rst | 1454 Enables H264 hierarchical coding. Applicable to the H264 encoder.
1456 .. _v4l2-mpeg-video-h264-hierarchical-coding-type:
1462 Specifies the hierarchical coding type. Applicable to the H264
1472 - Hierarchical B coding.
1474 - Hierarchical P coding.
1479 Specifies the number of hierarchical coding layers. Applicable to
2052 Selects the hierarchical coding type for encoding. Possible values are:
2065 - Use the B frame for hierarchical coding.
2067 - Use the P frame for hierarchical coding.
2075 Selects the hierarchical coding layer. In normal encoding
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/ |
| D | psci.yaml | 112 ARM systems can have multiple cores, sometimes in an hierarchical
123 (OSI) CPU suspend mode is introduced. Using a hierarchical representation
192 // Case 4: CPUs and CPU idle states described using the hierarchical model.
|
| /kernel/linux/linux-4.19/arch/arm/mm/ |
| D | cache-tauros2.c | 32 * When Tauros2 is used on a CPU that supports the v7 hierarchical
239 * Check whether this CPU has support for the v7 hierarchical in tauros2_internal_init()
241 * register indicates support for the v7 hierarchical cache in tauros2_internal_init()
|
| /kernel/linux/linux-5.10/arch/arm/mm/ |
| D | cache-tauros2.c | 32 * When Tauros2 is used on a CPU that supports the v7 hierarchical
239 * Check whether this CPU has support for the v7 hierarchical in tauros2_internal_init()
241 * register indicates support for the v7 hierarchical cache in tauros2_internal_init()
|
123456789