| /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.
|
| /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/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/linux/drivers/perf/arm_cspmu/ |
| H A D | Kconfig | 11 architecture does not have relationship with the ARM CoreSight
|
| /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/Documentation/ABI/testing/ |
| H A D | sysfs-devices-software_node | 10 relationship it has to some of the other devices.
|
| /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/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/openbmc/meta-phosphor/recipes-phosphor/chassis/ |
| H A D | phosphor-skeleton-control-power_git.bb | 38 # Build up requires relationship for START_TGTFMT and STOP_TGTFMT
|
| /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/drivers/sh/intc/ |
| H A D | Kconfig | 39 This will create a debugfs entry for showing the relationship
|
| /openbmc/linux/Documentation/devicetree/bindings/display/ |
| H A D | dp-aux-bus.yaml | 19 To model this relationship, DP sinks should be placed as children
|
| /openbmc/openbmc/poky/meta/lib/oe/ |
| H A D | spdx.py | 322 def add_relationship(self, _from, relationship, _to, *, comment=None, annotation=None): argument
336 relationshipType=relationship,
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Item/ |
| H A D | README.md | 10 edges can be constructed that represents the relationship between different
|
| /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/openbmc/poky/meta/recipes-core/ncurses/files/ |
| H A D | 0001-tic-hang.patch | 40 # KDE's "vt100" keyboard has no relationship to any terminal that DEC made, but
|
| /openbmc/linux/Documentation/devicetree/bindings/soc/qcom/ |
| H A D | qcom,pmic-glink.yaml | 18 particularly the USB Type-C controllers relationship with USB and DisplayPort
|
| /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/devicetree/bindings/clock/ |
| H A D | sprd,sc9860-clk.txt | 29 relationship (i.e. how many parents and which are the parents)
|
| /openbmc/u-boot/doc/device-tree-bindings/mailbox/ |
| H A D | nvidia,tegra186-hsp.txt | 7 two processors not in an SMP relationship.
|
| /openbmc/linux/Documentation/sound/soc/ |
| H A D | clocking.rst | 38 This relationship depends on the codec or SoC CPU in particular. In general
|
| /openbmc/u-boot/doc/ |
| H A D | README.sched | 50 - There is no parent-child relationship between threads. Only one
|
| /openbmc/linux/Documentation/peci/ |
| H A D | peci.rst | 37 have a fixed relationship with the processor socket ID - if one of the
|
| /openbmc/linux/Documentation/devicetree/bindings/mfd/ |
| H A D | mfd.txt | 28 - ranges: Describes the address mapping relationship to the parent. Should set
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | k8temp.rst | 56 The relationship is following:
|