| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-regulator | 257 implementing suspend voltage configuration constraints.
268 implementing suspend voltage configuration constraints.
279 implementing suspend voltage configuration constraints.
289 memory, for regulators implementing suspend mode
300 for regulators implementing suspend mode configuration
311 standby, for regulators implementing suspend mode
321 when suspended to memory, for regulators implementing suspend
334 when suspended to disk, for regulators implementing
347 state when suspended to standby, for regulators implementing
|
| /openbmc/openpower-hw-diags/util/ |
| H A D | dbus.hpp | 29 * @param[out] o_path Path of dbus object implementing the interface
30 * @param[out] o_service Service implementing the dbus object path
41 * @param[out] o_service Service implementing the dbus object and interface
50 * @param[in] i_interface Interface implementing the property
52 * @param[in] i_service Service implementing the dbus object and interface
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Item/ |
| H A D | System.interface.yaml | 3 that represent a computer system. Implementing System does not provide any
4 additional API but instead adds type context to objects implementing other
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/ |
| H A D | Association.interface.yaml | 5 An object implementing Association describes a one way, one to many
8 object implementing Association.
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/ |
| H A D | FanPwm.interface.yaml | 3 dependent and objects implementing Control.FanPwm must be instantiated
6 Any service implementing Control.FanPwm on one or more objects must
|
| H A D | FanSpeed.interface.yaml | 3 dependent and objects implementing Control.FanSpeed must be instantiated
6 Any service implementing Control.FanSpeed on one or more objects must
|
| H A D | VoltageRegulatorControl.interface.yaml | 2 Implement to provide control of a voltage regulator. Objects implementing
7 Any service implementing Control.VoltageRegulatorControl on one or more
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/ |
| H A D | Manager.interface.yaml | 5 one implementation on the inventory namespace root. An implementing service
11 Signal the implementing service that an item is ready to have its
|
| /openbmc/u-boot/include/ |
| H A D | clk-uclass.h | 24 * The clock core calls this function as the first step in implementing
45 * implementing a client's clk_get_by_*() call, following a successful
46 * xxx_xlate() call, or as the only step in implementing a client's
|
| H A D | dma-uclass.h | 29 * The DMA core calls this function as the first step in implementing
50 * implementing a client's dma_get_by_*() call, following a successful
51 * xxx_xlate() call, or as the only step in implementing a client's
|
| H A D | power-domain-uclass.h | 25 * implementing a client's power_domain_get() call.
47 * implementing a client's power_domain_get() call, following a
|
| /openbmc/u-boot/test/dm/ |
| H A D | mmc.c | 13 * Basic test of the mmc uclass. We could expand this by implementing an MMC
14 * stack for sandbox, or at least implementing the basic operation.
|
| /openbmc/linux/Documentation/devicetree/bindings/iommu/ |
| H A D | arm,smmu.yaml | 26 - description: Qcom SoCs implementing "arm,smmu-v2"
35 - description: Qcom SoCs implementing "qcom,smmu-500" and "arm,mmu-500"
62 - description: Qcom SoCs implementing "arm,mmu-500" (legacy binding)
81 - description: Qcom Adreno GPUs implementing "qcom,smmu-500" and "arm,mmu-500"
95 - description: Qcom Adreno GPUs implementing "arm,mmu-500" (legacy binding)
105 - description: Qcom Adreno GPUs implementing "arm,smmu-v2"
119 - description: Marvell SoCs implementing "arm,mmu-500"
|
| /openbmc/linux/net/hsr/ |
| H A D | Kconfig | 13 DANH ("Doubly attached node implementing HSR") or DANP ("Doubly
14 attached node implementing PRP"). For this to work, your Linux box
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Sensor/Threshold/ |
| H A D | HardShutdown.interface.yaml | 4 implementing Sensor.Threshold.HardShutdown must be instantiated in the
20 Additionally, any object implementing Sensor.Threshold.HardShutdown must
|
| H A D | Warning.interface.yaml | 2 Implement to provide warning class sensor thresholds. Objects implementing
19 Additionally, any object implementing Sensor.Threshold.Warning must also
|
| H A D | SoftShutdown.interface.yaml | 3 implementing Sensor.Threshold.Shutdown must be instantiated in the correct
19 Additionally, any object implementing Sensor.Threshold.SoftShutdown must
|
| H A D | Critical.interface.yaml | 2 Implement to provide critical class sensor thresholds. Objects implementing
19 Additionally, any object implementing Sensor.Threshold.Critical must also
|
| H A D | PerformanceLoss.interface.yaml | 3 implementing Sensor.Threshold.PerformanceLoss must be instantiated in the
19 Additionally, any object implementing Sensor.Threshold.PerformanceLoss must
|
| /openbmc/phosphor-pid-control/ |
| H A D | interfaces.hpp | 31 * A ReadInterface is a plug-in for the PluggableSensor and anyone implementing
50 * A WriteInterface is a plug-in for the PluggableSensor and anyone implementing
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/cim-schema/files/ |
| H A D | LICENSE | 23 // any party implementing such standard, whether such implementation
27 // indemnified and held harmless by any party implementing the
|
| /openbmc/openbmc/meta-openembedded/meta-networking/licenses/ |
| H A D | DMTF | 23 // any party implementing such standard, whether such implementation
27 // indemnified and held harmless by any party implementing the
|
| /openbmc/linux/rust/macros/ |
| H A D | pinned_drop.rs | 10 // Ensure that we are implementing `PinnedDrop`. in pinned_drop()
36 .unwrap_or_else(|| panic!("Expected an `impl` block implementing `PinnedDrop`.")); in pinned_drop()
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-encoder-cmd.rst | 106 For a device implementing the :ref:`encoder`, once the drain sequence
118 For a device implementing the :ref:`encoder`, the command will initiate
160 A drain sequence of a device implementing the :ref:`encoder` is still in
|
| /openbmc/libmctp/ |
| H A D | README.md | 12 - where you are implementing MCTP in an embedded device; or
15 - need a single application implementing all of the MCTP stack; and
18 Notably, if you are implementing an MCTP application on Linux, you _almost
|