/linux/Documentation/firmware-guide/acpi/dsd/ |
H A D | data-node-references.rst | 5 Referencing hierarchical data nodes 12 Hierarchical data extension nodes may not be referred to directly, hence this 15 A reference to a _DSD hierarchical data node is a string consisting of a 18 the hierarchical data node, not a reference! 20 The hierarchical data extension node which is referred to shall be located 22 hierarchical data extension node [dsd-guide]. 24 The keys in the hierarchical data nodes shall consist of the name of the node, 30 In case a hierarchical data extensions node has no numerical value, then the 32 "@" character and the number shall be omitted from the hierarchical data 40 reference to a hierarchical data extension node ANOD under DEV0 under the parent
|
H A 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
|
H A D | leds.rst | 8 Individual LEDs are described by hierarchical data extension [5] nodes under the 11 connected. [leds] The hierarchical data nodes are named "led@X", where X is the 24 Under the LED driver device, The first hierarchical data extension package list
|
/linux/tools/testing/selftests/net/forwarding/ |
H A D | ip6gre_hier.sh | 5 # This test uses hierarchical topology for IP tunneling tests. See 39 test_traffic_ip4ip6 "GRE hierarchical IPv4-in-IPv6" 40 test_traffic_ip6ip6 "GRE hierarchical IPv6-in-IPv6" 52 test_traffic_ip4ip6 "GRE hierarchical IPv4-in-IPv6 (new remote)" 53 test_traffic_ip6ip6 "GRE hierarchical IPv6-in-IPv6 (new remote)" 57 test_traffic_ip4ip6 "GRE hierarchical IPv4-in-IPv6 (old remote)" 58 test_traffic_ip6ip6 "GRE hierarchical IPv6-in-IPv6 (old remote)"
|
H A D | ip6gre_hier_key.sh | 5 # This test uses hierarchical topology for IP tunneling tests. See 39 test_traffic_ip4ip6 "GRE hierarchical IPv4-in-IPv6 with key" 40 test_traffic_ip6ip6 "GRE hierarchical IPv6-in-IPv6 with key" 52 test_traffic_ip4ip6 "GRE hierarchical IPv4-in-IPv6 with key (new remote)" 53 test_traffic_ip6ip6 "GRE hierarchical IPv6-in-IPv6 with key (new remote)" 57 test_traffic_ip4ip6 "GRE hierarchical IPv4-in-IPv6 with key (old remote)" 58 test_traffic_ip6ip6 "GRE hierarchical IPv6-in-IPv6 with key (old remote)"
|
H A D | ip6gre_hier_keys.sh | 5 # This test uses hierarchical topology for IP tunneling tests. See 39 test_traffic_ip4ip6 "GRE hierarchical IPv4-in-IPv6 with ikey/okey" 40 test_traffic_ip6ip6 "GRE hierarchical IPv6-in-IPv6 with ikey/okey" 52 test_traffic_ip4ip6 "GRE hierarchical IPv4-in-IPv6 with ikey/okey (new remote)" 53 test_traffic_ip6ip6 "GRE hierarchical IPv6-in-IPv6 with ikey/okey (new remote)" 57 test_traffic_ip4ip6 "GRE hierarchical IPv4-in-IPv6 with ikey/okey (old remote)" 58 test_traffic_ip6ip6 "GRE hierarchical IPv6-in-IPv6 with ikey/okey (old remote)"
|
H A 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"
|
H A 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"
|
H A 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"
|
/linux/drivers/media/v4l2-core/ |
H A 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() 1016 case V4L2_CID_MPEG_VIDEO_HEVC_HIER_CODING_TYPE: return "HEVC Hierarchical Coding Type"; in v4l2_ctrl_get_name() [all …]
|
/linux/Documentation/userspace-api/media/v4l/ |
H A 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 …]
|
/linux/kernel/irq/ |
H A D | Kconfig | 65 # Support for hierarchical irq domains 75 # Support for hierarchical fasteoi+edge and fasteoi+level handlers 90 # Generic MSI hierarchical interrupt domain support
|
/linux/Documentation/admin-guide/device-mapper/ |
H A 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
|
/linux/drivers/cpuidle/ |
H A 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
|
H A D | cpuidle-psci.c | 80 /* Do runtime PM to manage a hierarchical CPU toplogy. */ in __psci_enter_domain_idle_state() 245 /* Currently limit the hierarchical topology to be used in OSI mode. */ in psci_dt_cpu_init_topology() 258 * deeper states. On PREEMPT_RT the hierarchical topology is limited to in psci_dt_cpu_init_topology() 302 /* Initialize optional data, used for the hierarchical topology. */ in psci_dt_cpu_init_idle()
|
H A D | Kconfig.riscv | 14 driver for RISC-V systems. This drivers also supports hierarchical
|
/linux/block/ |
H A D | Kconfig.iosched | 31 bool "BFQ hierarchical scheduling support" 37 Enable hierarchical scheduling in BFQ, using the blkio
|
/linux/drivers/media/dvb-frontends/ |
H A D | stv0367_priv.h | 100 FE_TER_HIER_ALPHA_1, /* Hierarchical modulation a = 1*/ 101 FE_TER_HIER_ALPHA_2, /* Hierarchical modulation a = 2*/ 102 FE_TER_HIER_ALPHA_4 /* Hierarchical modulation a = 4*/
|
/linux/Documentation/devicetree/bindings/arm/ |
H A D | psci.yaml | 108 ARM systems can have multiple cores, sometimes in an hierarchical 119 (OSI) CPU suspend mode is introduced. Using a hierarchical representation 188 // Case 4: CPUs and CPU idle states described using the hierarchical model.
|
/linux/arch/arm/mm/ |
H A D | cache-tauros2.c | 29 * When Tauros2 is used on a CPU that supports the v7 hierarchical 236 * Check whether this CPU has support for the v7 hierarchical in tauros2_internal_init() 238 * register indicates support for the v7 hierarchical cache in tauros2_internal_init()
|
/linux/Documentation/driver-api/driver-model/ |
H A D | overview.rst | 79 By virtue of having a complete hierarchical view of all the devices in the 80 system, exporting a complete hierarchical view to userspace becomes relatively
|
/linux/Documentation/firmware-guide/acpi/ |
H A D | DSD-properties-rules.rst | 42 "Hierarchical Data Extension UUID" in _DSD (Device Specific Data) 45 Property sets may be hierarchical. That is, a property set may contain
|
/linux/Documentation/maintainer/ |
H A D | feature-and-driver-maintainers.rst | 134 To an outsider the Linux kernel may resemble a hierarchical organization 135 with Linus as the CEO. While the code flows in a hierarchical fashion,
|
/linux/Documentation/filesystems/ |
H A D | btrfs.rst | 25 * Hierarchical quota groups (subvolume and snapshot support)
|
/linux/net/sched/ |
H A D | Kconfig | 49 tristate "Hierarchical Token Bucket (HTB)" 51 Say Y here if you want to use the Hierarchical Token Buckets (HTB) 63 tristate "Hierarchical Fair Service Curve (HFSC)" 65 Say Y here if you want to use the Hierarchical Fair Service Curve
|