| /linux/tools/thermal/tmon/ |
| H A D | README | 6 thermal relationship between processor and fan has become past for modern
11 complexity of the thermal relationship can grow exponentially among cooling
14 To expose such relationship to the userspace, Linux generic thermal layer
30 that can be used for thermal relationship training.
|
| H A D | tmon.8 | 12 \fBtmon \fP can be used to visualize thermal relationship and
31 3. Thermal relationship learning and device tuning
|
| /linux/Documentation/networking/devlink/ |
| H A D | index.rst | 37 nested relationship:
40 devlink relationship (could be user for multiple nested instances.
42 nested devlink relationship.
44 nested devlink relationship.
|
| /linux/Documentation/admin-guide/LSM/ |
| H A D | Yama.rst | 59 a process must have a predefined relationship
61 this relationship is that of only its descendants when the above
62 classic criteria is also met. To change the relationship, an
|
| /linux/Documentation/driver-api/ |
| H A D | device_link.rst | 8 that are borne out of a parent/child relationship within the device
10 are ordered based on this relationship, i.e. children are always suspended
14 mere parent/child relationship, e.g. between siblings, and have the
169 relationship between the devices and is thus more apt.
186 VGA device (supplier) aptly represents this relationship.
|
| /linux/security/yama/ |
| H A D | yama_lsm.c | 30 /* describe a ptrace relationship for potential exception */
139 * Returns 0 if relationship was added, -ve on error.
316 * If there's already an active tracing relationship, then make an in ptracer_exception_found()
325 /* Look for a PR_SET_PTRACER relationship. */ in ptracer_exception_found()
|
| /linux/Documentation/devicetree/bindings/pci/ |
| H A D | pci-iommu.txt | 2 relationship between PCI(e) devices and IOMMU(s).
21 The generic 'iommus' property is insufficient to describe this relationship,
|
| /linux/Documentation/power/regulator/ |
| H A D | overview.rst | 71 and this represents a "supplies" relationship:
87 and a "supplies" relationship:
|
| /linux/Documentation/devicetree/bindings/misc/ |
| H A D | fsl,qoriq-mc.yaml | 30 The generic 'iommus' property is insufficient to describe the relationship
132 the relationship between the Ethernet MACs which belong to the MC
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices-software_node | 10 relationship it has to some of the other devices.
|
| /linux/drivers/iommu/ |
| H A D | fsl_pamu_domain.h | 20 /* domain-device relationship */
|
| /linux/drivers/perf/arm_cspmu/ |
| H A D | Kconfig | 11 architecture does not have relationship with the ARM CoreSight
|
| /linux/drivers/sh/intc/ |
| H A D | Kconfig | 39 This will create a debugfs entry for showing the relationship
|
| /linux/tools/perf/tests/shell/lib/ |
| H A D | perf_metric_validation.py | 12 self.metric: list = metric # multiple metrics in relationship type tests
21 return "\nMetric Relationship Error: \tThe collected value of metric {0}\n\
252 Validate if the metrics follow the required relationship in the rule.
402 # Create metric set for relationship rules
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | numaperf.rst | 38 this relationship. The highest performing initiator to a given target
46 relationship for the access class "0" memory initiators and targets::
|
| /linux/Documentation/devicetree/bindings/display/ |
| H A D | dp-aux-bus.yaml | 19 To model this relationship, DP sinks should be placed as children
|
| /linux/arch/sh/mm/ |
| H A D | uncached.c | 12 * uncached segments by making use of the 1:1 mapping relationship in
|
| H A D | asids-debugfs.c | 13 * relationship needs to be known. This is primarily for debugging.
|
| /linux/arch/arm/mach-mmp/ |
| H A D | addr-map.h | 12 * slave port to AHB/APB bridge, due to its close relationship to those
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | colorspaces.rst | 30 enters the eye. The science of colorimetry is about the relationship
38 In the 1920s experiments were devised to determine the relationship
|
| /linux/Documentation/networking/ |
| H A D | alias.rst | 46 Relationship with main device
|
| /linux/Documentation/devicetree/bindings/mfd/ |
| H A D | mfd.txt | 29 - ranges: Describes the address mapping relationship to the parent. Should set
|
| /linux/include/uapi/drm/ |
| H A D | drm_fourcc.h | 56 * vendor-namespaced, and as such the relationship between a fourcc code and a
119 /* 1 bpp Darkness (inverse relationship between channel value and brightness) */
122 /* 2 bpp Darkness (inverse relationship between channel value and brightness) */
125 /* 4 bpp Darkness (inverse relationship between channel value and brightness) */
128 /* 8 bpp Darkness (inverse relationship between channel value and brightness) */
131 /* 1 bpp Red (direct relationship between channel value and brightness) */
134 /* 2 bpp Red (direct relationship between channel value and brightness) */
137 /* 4 bpp Red (direct relationship between channel value and brightness) */
140 /* 8 bpp Red (direct relationship between channel value and brightness) */
143 /* 10 bpp Red (direct relationship between channel value and brightness) */
[all …]
|
| /linux/include/uapi/sound/sof/ |
| H A D | header.h | 24 * IPC4 ABI version numbers have no relationship.
|
| /linux/Documentation/peci/ |
| H A D | peci.rst | 37 have a fixed relationship with the processor socket ID - if one of the
|