Searched full:hierarchical (Results 1 – 25 of 269) sorted by relevance
1234567891011
| /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
93 [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-6.6/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 [dsd-guide] keys. Specifically, the hierarchical
18 the 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
|
| D | graph.rst | 14 for graphs: property [dsd-guide] and hierarchical data extensions. 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.
43 All port nodes are located under the device's "_DSD" node in the hierarchical
51 Further on, endpoints are located under the port nodes. The hierarchical
|
| /kernel/linux/linux-6.6/drivers/media/v4l2-core/ |
| D | v4l2-ctrls-defs.c | 926 case V4L2_CID_MPEG_VIDEO_H264_HIERARCHICAL_CODING: return "Enable H264 Hierarchical Coding"; in v4l2_ctrl_get_name()
927 case V4L2_CID_MPEG_VIDEO_H264_HIERARCHICAL_CODING_TYPE: return "H264 Hierarchical Coding Type"; in v4l2_ctrl_get_name()
940 case V4L2_CID_MPEG_VIDEO_H264_HIER_CODING_L0_BR: return "H264 Hierarchical Lay 0 Bitrate"; in v4l2_ctrl_get_name()
941 case V4L2_CID_MPEG_VIDEO_H264_HIER_CODING_L1_BR: return "H264 Hierarchical Lay 1 Bitrate"; in v4l2_ctrl_get_name()
942 case V4L2_CID_MPEG_VIDEO_H264_HIER_CODING_L2_BR: return "H264 Hierarchical Lay 2 Bitrate"; in v4l2_ctrl_get_name()
943 case V4L2_CID_MPEG_VIDEO_H264_HIER_CODING_L3_BR: return "H264 Hierarchical Lay 3 Bitrate"; in v4l2_ctrl_get_name()
944 case V4L2_CID_MPEG_VIDEO_H264_HIER_CODING_L4_BR: return "H264 Hierarchical Lay 4 Bitrate"; in v4l2_ctrl_get_name()
945 case V4L2_CID_MPEG_VIDEO_H264_HIER_CODING_L5_BR: return "H264 Hierarchical Lay 5 Bitrate"; in v4l2_ctrl_get_name()
946 case V4L2_CID_MPEG_VIDEO_H264_HIER_CODING_L6_BR: return "H264 Hierarchical Lay 6 Bitrate"; in v4l2_ctrl_get_name()
1015 case V4L2_CID_MPEG_VIDEO_HEVC_HIER_CODING_TYPE: return "HEVC Hierarchical Coding Type"; in v4l2_ctrl_get_name()
[all …]
|
| /kernel/linux/build/test/moduletest/runtest/bin/enhancedf2fs_t/testcases/bin/ |
| D | enhancedf2fs07.sh | 16 # Description: Hierarchical SSR control interface
36 tst_res TINFO "Start test hierarchical SSR control interface."
48 tst_res TPASS "Hierarchical SSR control interface setting pass."
50 tst_res TFAIL "Hierarchical SSR control interface setting failed!"
|
| D | enhancedf2fs09.sh | 16 # Description: Hierarchical SSR waterline configuration interface
36 tst_res TINFO "Start test hierarchical SSR waterline configuration interface."
63 tst_res TPASS "Hierarchical SSR waterline configuration interface pass."
65 tst_res TFAIL "Hierarchical SSR waterline configuration interface failed."
|
| D | enhancedf2fs08.sh | 16 # Description: Hierarchical SSR threshold configuration interface
36 tst_res TINFO "Start test hierarchical SSR threshold configuration interface."
63 tst_res TPASS "hierarchical SSR threshold configuration interface pass."
65 tst_res TFAIL "Hierarchical SSR threshold configuration interface failed!"
|
| D | enhancedf2fs10.sh | 16 # Description: hierarchical SSR recovery function is enabled
36 tst_res TINFO "Start test hierarchical SSR recovery function is enabled."
82 tst_res TPASS "The hierarchical SSR recovery function is enabled pass."
84 tst_res TFAIL "The hierarchical SSR recovery function is enabled failed!"
|
| D | enhancedf2fs11.sh | 16 # Description: Hierarchical SSR recycling is disabled
36 tst_res TINFO "Start test hierarchical SSR recycling is disabled."
81 tst_res TPASS "Hierarchical SSR recycling is disabled pass."
83 tst_res TFAIL "Hierarchical SSR recycling is disabled failed!"
|
| /kernel/linux/linux-6.6/tools/testing/selftests/net/forwarding/ |
| D | ip6gre_hier.sh | 5 # This test uses hierarchical topology for IP tunneling tests. See
38 test_traffic_ip4ip6 "GRE hierarchical IPv4-in-IPv6"
39 test_traffic_ip6ip6 "GRE hierarchical IPv6-in-IPv6"
|
| D | ip6gre_hier_keys.sh | 5 # This test uses hierarchical topology for IP tunneling tests. See
38 test_traffic_ip4ip6 "GRE hierarchical IPv4-in-IPv6 with ikey/okey"
39 test_traffic_ip6ip6 "GRE hierarchical IPv6-in-IPv6 with ikey/okey"
|
| D | ip6gre_hier_key.sh | 5 # This test uses hierarchical topology for IP tunneling tests. See
38 test_traffic_ip4ip6 "GRE hierarchical IPv4-in-IPv6 with key"
39 test_traffic_ip6ip6 "GRE hierarchical IPv6-in-IPv6 with key"
|
| 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.sh | 5 # This test uses hierarchical topology for IP tunneling tests. See
37 ping_test $h1 192.0.2.18 " gre hierarchical"
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-codec.rst | 1583 Enables H264 hierarchical coding. Applicable to the H264 encoder.
1585 .. _v4l2-mpeg-video-h264-hierarchical-coding-type:
1591 Specifies the hierarchical coding type. Applicable to the H264
1601 - Hierarchical B coding.
1603 - Hierarchical P coding.
1608 Specifies the number of hierarchical coding layers. Applicable to
1628 Indicates bit rate (bps) for hierarchical coding layer 0 for H264 encoder.
1631 Indicates bit rate (bps) for hierarchical coding layer 1 for H264 encoder.
1634 Indicates bit rate (bps) for hierarchical coding layer 2 for H264 encoder.
1637 Indicates bit rate (bps) for hierarchical coding layer 3 for H264 encoder.
[all …]
|
| /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
92 # Generic MSI hierarchical interrupt domain support
|
| /kernel/linux/linux-6.6/kernel/irq/ |
| D | Kconfig | 69 # Support for hierarchical irq domains
79 # Support for hierarchical fasteoi+edge and fasteoi+level handlers
94 # Generic MSI hierarchical interrupt domain support
|
| /kernel/linux/linux-6.6/drivers/cpuidle/ |
| D | Kconfig.arm | 28 - If the idle states are described with the non-hierarchical layout,
31 - If the idle states are described with the hierarchical layout,
43 which is needed to support the hierarchical DT based layout of the
|
| /kernel/linux/linux-6.6/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/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_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.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_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"
|
1234567891011