Searched full:relationship (Results 1 – 25 of 422) sorted by relevance
12345678910>>...17
| /kernel/linux/linux-6.6/tools/thermal/tmon/ |
| 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.
|
| D | tmon.8 | 12 \fBtmon \fP can be used to visualize thermal relationship and
31 3. Thermal relationship learning and device tuning
|
| /kernel/linux/linux-5.10/tools/thermal/tmon/ |
| 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.
|
| D | tmon.8 | 12 \fBtmon \fP can be used to visualize thermal relationship and
31 3. Thermal relationship learning and device tuning
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/LSM/ |
| 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
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/LSM/ |
| 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
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| 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.
|
| /kernel/linux/linux-6.6/Documentation/driver-api/ |
| 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.
|
| /kernel/linux/linux-6.6/security/yama/ |
| D | yama_lsm.c | 29 /* 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()
|
| /kernel/linux/linux-5.10/security/yama/ |
| D | yama_lsm.c | 29 /* 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()
|
| /kernel/linux/linux-6.6/drivers/perf/arm_cspmu/ |
| D | Kconfig | 11 architecture does not have relationship with the ARM CoreSight
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/pci/ |
| D | pci-iommu.txt | 2 relationship between PCI(e) devices and IOMMU(s).
21 The generic 'iommus' property is insufficient to describe this relationship,
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pci/ |
| D | pci-iommu.txt | 2 relationship between PCI(e) devices and IOMMU(s).
21 The generic 'iommus' property is insufficient to describe this relationship,
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-devices-software_node | 10 relationship it has to some of the other devices.
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-devices-software_node | 10 relationship it has to some of the other devices.
|
| /kernel/linux/linux-5.10/drivers/thermal/intel/int340x_thermal/ |
| D | acpi_thermal_rel.c | 2 /* acpi_thermal_rel.c driver for exporting ACPI thermal relationship
59 * acpi_parse_trt - Thermal Relationship Table _TRT for passive cooling
136 * acpi_parse_art - Parse Active Relationship Table _ART
|
| /kernel/linux/linux-6.6/drivers/iommu/ |
| D | fsl_pamu_domain.h | 20 /* domain-device relationship */
|
| /kernel/linux/linux-6.6/Documentation/power/regulator/ |
| D | overview.rst | 71 and this represents a "supplies" relationship:
87 and a "supplies" relationship:
|
| /kernel/linux/linux-5.10/Documentation/power/regulator/ |
| D | overview.rst | 71 and this represents a "supplies" relationship:
87 and a "supplies" relationship:
|
| /kernel/linux/linux-6.6/drivers/sh/intc/ |
| D | Kconfig | 39 This will create a debugfs entry for showing the relationship
|
| /kernel/linux/linux-5.10/drivers/sh/intc/ |
| D | Kconfig | 39 This will create a debugfs entry for showing the relationship
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/misc/ |
| D | fsl,qoriq-mc.txt | 20 The generic 'iommus' property is insufficient to describe the relationship
85 the relationship between the Ethernet MACs which belong to the MC
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/misc/ |
| D | fsl,qoriq-mc.txt | 20 The generic 'iommus' property is insufficient to describe the relationship
85 the relationship between the Ethernet MACs which belong to the MC
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/display/ |
| D | dp-aux-bus.yaml | 19 To model this relationship, DP sinks should be placed as children
|
| /kernel/linux/linux-6.6/arch/sh/mm/ |
| D | uncached.c | 12 * uncached segments by making use of the 1:1 mapping relationship in
|
12345678910>>...17