Searched refs:hierarchical (Results 1 – 25 of 40) sorted by relevance
12
| /Linux-v6.1/Documentation/firmware-guide/acpi/dsd/ |
| D | data-node-references.rst | 5 Referencing hierarchical data nodes
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
|
| 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
29 Under the LED driver device, The first hierarchical data extension package list
|
| D | phy.rst | 62 hierarchical data extension (UUID dbb8e3e6-5886-4ba6-8795-1319f52a966b
|
| /Linux-v6.1/kernel/irq/ |
| D | Kconfig | 69 # Support for hierarchical irq domains
79 # Support for hierarchical fasteoi+edge and fasteoi+level handlers
93 # Generic MSI hierarchical interrupt domain support
|
| /Linux-v6.1/block/ |
| D | Kconfig.iosched | 31 bool "BFQ hierarchical scheduling support"
36 Enable hierarchical scheduling in BFQ, using the blkio
|
| /Linux-v6.1/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
|
| /Linux-v6.1/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
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.
1640 Indicates bit rate (bps) for hierarchical coding layer 4 for H264 encoder.
1643 Indicates bit rate (bps) for hierarchical coding layer 5 for H264 encoder.
[all …]
|
| /Linux-v6.1/drivers/cpuidle/ |
| D | Kconfig.riscv | 14 driver for RISC-V systems. This drivers also supports hierarchical
|
| D | Kconfig.arm | 35 which is needed to support the hierarchical DT based layout of the
|
| /Linux-v6.1/fs/notify/fanotify/ |
| D | Kconfig | 25 hierarchical storage management systems.
|
| /Linux-v6.1/Documentation/devicetree/bindings/gpio/ |
| D | intel,ixp4xx-gpio.txt | 6 The interrupt portions of the GPIO controller is hierarchical:
|
| /Linux-v6.1/kernel/rcu/ |
| D | Kconfig | 145 int "Tree-based hierarchical RCU fanout value"
152 This option controls the fanout of hierarchical implementations
165 int "Tree-based hierarchical RCU leaf-level fanout value"
173 This option controls the leaf-level fanout of hierarchical
|
| /Linux-v6.1/Documentation/devicetree/bindings/mtd/ |
| D | partition.txt | 20 hierarchical (multi-level) layouts and should be used if there is some
|
| /Linux-v6.1/Documentation/driver-api/driver-model/ |
| 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-v6.1/Documentation/admin-guide/cgroup-v1/ |
| D | memory.rst | 49 - hierarchical accounting
81 memory.use_hierarchy set/show hierarchical account enabled
560 total_<counter> # hierarchical version of <counter>, which in
562 sum of all hierarchical children's values of
636 hierarchical children's values in addition to the memcg's own value.
651 The memory controller supports a deep hierarchy and hierarchical accounting.
664 In the diagram above, with hierarchical accounting enabled, all memory
672 Hierarchical accounting is enabled by default. Disabling the hierarchical
907 hierarchical, pass-through, notification for all ancestor memcgs. Notification
|
| D | pids.rst | 31 all new cgroups (N.B. that PID limits are hierarchical, so the most stringent
|
| D | freezer-subsystem.rst | 56 The cgroup freezer is hierarchical. Freezing a cgroup freezes all
|
| /Linux-v6.1/tools/perf/Documentation/ |
| D | tips.txt | 31 For hierarchical output, try: perf report --hierarchy
|
| /Linux-v6.1/Documentation/devicetree/bindings/arm/msm/ |
| D | qcom,idle-state.txt | 49 modes. In a hierarchical power domain SoC, this means L2 and other caches can
|
| /Linux-v6.1/Documentation/firmware-guide/acpi/ |
| D | DSD-properties-rules.rst | 45 Property sets may be hierarchical. That is, a property set may contain
|
| /Linux-v6.1/Documentation/power/powercap/ |
| D | powercap.rst | 23 the system represented by different power zones are hierarchical (that is, one
|
| /Linux-v6.1/arch/arm/boot/compressed/ |
| D | head.S | 1264 tst r10, #0xf << 16 @ hierarchical cache (ARMv7)
1266 beq hierarchical
1269 hierarchical: label
|
| /Linux-v6.1/fs/cifs/ |
| D | Kconfig | 41 support for DFS (hierarchical name space), secure per-user
|
| /Linux-v6.1/Documentation/block/ |
| D | bfq-iosched.rst | 42 system, in case full hierarchical support is enabled (i.e.,
49 If CONFIG_BFQ_CGROUP_DEBUG is set (and of course full hierarchical
241 also ready for hierarchical scheduling, details in Section 4.
|
12
