| /openbmc/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
|
| /openbmc/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
|
| /openbmc/phosphor-dbus-interfaces/ |
| H A D | requirements.md | 62 Directed associations are more common and are used to show a relationship
92 The primary relationship should be a verb with a Present Participle tense
93 (ending in '-ing'). The secondary relationship should be a verb with a Past
|
| /openbmc/qemu/include/qapi/ |
| H A D | visitor.h | 277 * @name expresses the relationship of this object to its parent
335 * @name expresses the relationship of this list to its parent
411 * @name expresses the relationship of this alternate to its parent
501 * @name expresses the relationship of this enum to its parent
540 * @name expresses the relationship of this integer to its parent
621 * @name expresses the relationship of this boolean to its parent
637 * @name expresses the relationship of this string to its parent
660 * @name expresses the relationship of this number to its parent
678 * @name expresses the relationship of this value to its parent
699 * @name expresses the relationship of the null value to its parent
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | Volume.v1_10_1.json | 95 …"description": "This action is used to establish a replication relationship by assigning an existi…
96 …"longDescription": "This action shall be used to establish a replication relationship by assigning…
100 "description": "The type of replica relationship to be created.",
101 …"longDescription": "This parameter shall contain the type of replica relationship to be created (e…
236 …volume resource to provide expanded data protection through a replica relationship with the specif…
237 …volume resource to provide expanded data protection through a replica relationship with the specif…
241 "description": "The type of replica relationship to be created.",
242 …"longDescription": "This parameter shall contain the type of replica relationship to be created (e…
980 …ronization between a source and target volume, remove the replication relationship, and optionally…
981 …ronization between a source and target volume, remove the replication relationship, and optionally…
[all …]
|
| /openbmc/docs/designs/ |
| H A D | physical-topology.md | 65 add an association definition for each of the relationship types listed above
132 a relationship to a specific item, it makes a query to the object mapper which
133 returns a list of all associated items and the relationship types between them.
|
| /openbmc/phosphor-host-ipmid/docs/ |
| H A D | contributing.md | 27 origin/master), these commits will show up with that same relationship in
28 gerrit. This means that each patch must be merged in order of that relationship.
30 that point on would need to be pushed to maintain the relationship. This will
|
| /openbmc/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.
|
| /openbmc/linux/security/yama/ |
| H A 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()
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/toastergui/templates/ |
| H A D | package_built_dependencies.html | 67 …<span class="glyphicon glyphicon-question-sign get-help" title="Five relationship types exist: rec…
68 Relationship type
|
| H A D | package_included_dependencies.html | 62 …<span class="glyphicon glyphicon-question-sign get-help" title="Five relationship types exist: rec…
63 Relationship type
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | Python-2.0.1 | 41 relationship of agency, partnership, or joint venture between PSF and
88 create any relationship of agency, partnership, or joint venture
159 License Agreement shall be deemed to create any relationship of
|
| H A D | Python-2.0 | 42 relationship of agency, partnership, or joint venture between PSF and
88 create any relationship of agency, partnership, or joint venture
158 License Agreement shall be deemed to create any relationship of
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Common/ |
| H A D | FilePath.interface.yaml | 4 Typically, this is added onto an existing object path to show a relationship
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Decorator/ |
| H A D | ManagedHost.interface.yaml | 10 host. This index is used for finding those relationship when an
|
| /openbmc/linux/drivers/perf/arm_cspmu/ |
| H A D | Kconfig | 11 architecture does not have relationship with the ARM CoreSight
|
| /openbmc/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,
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices-software_node | 10 relationship it has to some of the other devices.
|
| /openbmc/openpower-host-ipmi-flash/ |
| H A D | hiomap.cpp | 72 replied to by method calls, so it needs a Wants=/After= relationship on
77 Point 3. suggests mboxd should have a Wants=/Before= relationship with ipmid to
82 Wants=/Before= relationship with ipmid this message will never propagate to the
85 The above leads to mboxd having a Wants=/After= relationship with ipmid. This
97 On the basis that mboxd has a Wants=/After= relationship with ipmid,
103 sending it, and that the Wants=/After= relationship requires that mboxd has
|
| /openbmc/linux/drivers/iommu/ |
| H A D | fsl_pamu_domain.h | 20 /* domain-device relationship */
|
| /openbmc/linux/Documentation/power/regulator/ |
| H A D | overview.rst | 71 and this represents a "supplies" relationship:
87 and a "supplies" relationship:
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/Decorator/ |
| H A D | PowerSystemInputs.interface.yaml | 3 power supply unit(s). It is expected that the relationship to the chassis is
|
| /openbmc/linux/drivers/sh/intc/ |
| H A D | Kconfig | 39 This will create a debugfs entry for showing the relationship
|
| /openbmc/linux/Documentation/devicetree/bindings/misc/ |
| H A 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
|