| /openbmc/u-boot/api/ |
| H A D | README | 12 - the consumer app is responsible for producing appropriate context (call 18 - consumer application will recognize the API is available by searching 23 leaving as much processing as possible on the consumer application side, 47 - entry point at the consumer side, allows to make syscall, mandatory 50 - helper conveniency wrappers so that consumer app does not have to use 54 - consumer application
|
| /openbmc/gpioplus/test/ |
| H A D | chip.cpp | 108 ASSERT_LE(expected_info.consumer.size(), sizeof(info.consumer)); in TEST_F() 109 strcpy(info.consumer, expected_info.consumer.c_str()); in TEST_F() 122 EXPECT_EQ(expected_info.consumer, retrieved_info.consumer); in TEST_F()
|
| /openbmc/phosphor-power/phosphor-power-sequencer/src/ |
| H A D | gpio.hpp | 138 line.request({consumer, gpiod::line_request::DIRECTION_INPUT, 0}); in requestRead() 144 line.request({consumer, gpiod::line_request::DIRECTION_OUTPUT, 0}, in requestWrite() 170 inline static const std::string consumer{"phosphor-power-control"}; member in phosphor::power::sequencer::BMCGPIO
|
| /openbmc/docs/designs/ |
| H A D | bmc-health-monitor.md | 17 of this document), and a metric consumer (a program that makes use of health 27 consumer programs. Because of this staging step, the consumer does not need 29 4. Data transfer, where the consumer program obtains the metrics from the BMC by 31 5. The consumer program may take certain actions based on the metrics collected. 34 accomplished by both the producer and consumer. 5) is up to the consumer. 81 The metric consumer may be written in various different ways. No matter how the 82 consumer is obtained, it should be able to obtain the health metrics from the 85 The metric consumer is not in the scope of this document.
|
| H A D | redfish-pcie.md | 33 The proposed implementation will follow the standard D-Bus producer-consumer 35 from hardware. The consumer will retrieve and parse the D-Bus data to provide 57 bmcweb will be the consumer. It will be responsible for retrieving the Redfish
|
| /openbmc/u-boot/doc/device-tree-bindings/reset/ |
| H A D | ti,sci-reset.txt | 20 - #reset-cells: Must be 2. Please see the reset consumer node below for 36 Each of the reset consumer nodes should have the following properties,
|
| H A D | reset.txt | 10 reset consumer (the module being reset, or a module managing when a sub- 12 consumer, and provide a way to couple the two together.
|
| /openbmc/gpioplus/src/gpioplus/ |
| H A D | chip.hpp | 51 std::string consumer; member
|
| H A D | chip.cpp | 53 return LineInfo{info.flags, info.name, info.consumer}; in getLineInfo()
|
| /openbmc/openpower-proc-control/procedures/common/ |
| H A D | cfam_reset.cpp | 56 conf.consumer = "cfamReset"; in cfamReset()
|
| /openbmc/qemu/tests/qtest/libqos/ |
| H A D | qgraph.h | 299 void qos_node_consumes(const char *consumer, const char *interface,
|
| H A D | qgraph.c | 670 void qos_node_consumes(const char *consumer, const char *interface, in qos_node_consumes() argument 674 add_edge(interface, consumer, QEDGE_CONSUMED_BY, opts); in qos_node_consumes()
|
| /openbmc/u-boot/doc/device-tree-bindings/memory-controllers/ |
| H A D | k3-am654-ddrss.txt | 26 be defined as per the appropriate clock bindings consumer
|
| /openbmc/openbmc/meta-yadro/meta-nicole/recipes-kernel/linux/linux-aspeed/ |
| H A D | 0001-Add-NCSI-channel-selector.patch | 34 +#include <linux/gpio/consumer.h>
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | MS-PL | 18 … express warranties, guarantees, or conditions. You may have additional consumer rights under your…
|
| H A D | MS-LPL | 22 … express warranties, guarantees, or conditions. You may have additional consumer rights under your…
|
| H A D | MS-RL | 22 … express warranties, guarantees, or conditions. You may have additional consumer rights under your…
|
| /openbmc/u-boot/doc/ |
| H A D | README.menu | 14 the menu, and an opaque pointer to data controlled by the consumer.
|
| /openbmc/entity-manager/src/gpio-presence/ |
| H A D | gpio_presence_manager.cpp | 96 lineConfig.consumer = "gpio-presence"; in addConfig()
|
| /openbmc/u-boot/doc/device-tree-bindings/gpio/ |
| H A D | nvidia,tegra186-gpio.txt | 100 Indicates how many cells are used in a consumer's GPIO specifier. 114 Indicates how many cells are used in a consumer's interrupt specifier.
|
| /openbmc/openbmc/poky/meta/recipes-kernel/lttng/lttng-tools/ |
| H A D | 0001-tests-add-check_skip_kernel_test-to-check-root-user-.patch | 472 diag "With UST consumer daemons" 475 - skip $isroot "Root access is needed. Skipping kernel consumer health check test." "1" || 476 + check_skip_kernel_test "1" "Skipping kernel consumer health check test." || 478 diag "With kernel consumer daemon" 510 - skip $isroot "Root access is needed. Skipping kernel consumer health check test." "5" || 511 + check_skip_kernel_test "5" "Skipping kernel consumer health check test." || 513 diag "With kernel consumer daemon"
|
| /openbmc/u-boot/doc/driver-model/ |
| H A D | fs_firmware_loader.txt | 14 such as memory, then consumer driver such as FPGA driver can program FPGA image
|
| /openbmc/u-boot/doc/device-tree-bindings/firmware/ |
| H A D | nvidia,tegra186-bpmp.txt | 23 This node is a mailbox consumer. See the following files for details of
|
| /openbmc/u-boot/doc/device-tree-bindings/clock/ |
| H A D | st,stm32h7-rcc.txt | 114 The peripheral clock consumer should specify the desired clock by
|
| /openbmc/u-boot/board/hisilicon/hikey/ |
| H A D | README | 13 https://github.com/96boards/documentation/blob/master/consumer/hikey/hikey620/hardware-docs/HiKey_s… 16 https://github.com/96boards/documentation/blob/master/consumer/hikey/hikey620/hardware-docs/Hi6220V…
|