Home
last modified time | relevance | path

Searched full:consumer (Results 1 – 25 of 119) sorted by relevance

12345

/openbmc/u-boot/api/
H A DREADME12 - 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 Dchip.cpp103 const LineInfo expected_info{GPIOLINE_FLAG_ACTIVE_LOW, "name", "consumer"}; in TEST_F()
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/docs/designs/
H A Dbmc-health-monitor.md17 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 Dredfish-pcie.md33 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 Dti,sci-reset.txt20 - #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 Dreset.txt10 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/u-boot/arch/sandbox/include/asm/
H A Dgetopt.h18 * consumer code should focus on the macros below and
30 /* Callback into the end consumer code with the option */
/openbmc/gpioplus/src/gpioplus/
H A Dchip.hpp50 /** @brief the name of the consumer of the line */
51 std::string consumer; member
H A Dchip.cpp53 return LineInfo{info.flags, info.name, info.consumer}; in getLineInfo()
/openbmc/qemu/include/hw/timer/
H A Dsse-counter.h26 * consumer device should have a QOM link property which the board
64 * These functions are the interface by which a consumer of
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Console/
H A DAccess.interface.yaml8 Returns the unix socket file descriptor. The consumer can user this
/openbmc/u-boot/arch/arm/mach-owl/
H A DKconfig14 96Board Consumer Edition Specification. Features:
/openbmc/qemu/util/
H A Drcu.c179 /* Multi-producer, single-consumer queue based on urcu/static/wfqueue.h
180 * from liburcu. Note that head is only used by the consumer.
229 * the consumer head and tail are always consistent. The head in try_dequeue()
230 * is consistent because only the consumer reads/writes it. in try_dequeue()
239 * Since we are the sole consumer, and we excluded the empty case in try_dequeue()
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/librdkafka/
H A Dlibrdkafka_1.8.2.bb3 providing Producer, Consumer and Admin clients."
/openbmc/obmc-console/
H A Dconsole-dbus.c133 /* Register the consumer. */ in method_connect()
137 warnx("Failed to create socket consumer: %s", strerror(rc)); in method_connect()
139 "Failed to create socket consumer"); in method_connect()
H A Dconsole-server.h40 * Handlers will almost always want to register a ringbuffer consumer, which
240 /* console wrapper around ringbuffer consumer registration */
/openbmc/u-boot/board/hisilicon/hikey/
H A DREADME4 HiKey is the first certified 96Boards Consumer Edition board. The board/SoC has: -
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…
/openbmc/u-boot/doc/device-tree-bindings/exynos/
H A Ddwmmc.txt7 . Consumer Electronics Advanced Transport Architecture (CE-ATA-version 1.1)
/openbmc/u-boot/doc/device-tree-bindings/gpio/
H A Dnvidia,tegra186-gpio.txt100 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/openpower-proc-control/procedures/common/
H A Dcfam_reset.cpp56 conf.consumer = "cfamReset"; in cfamReset()
/openbmc/u-boot/doc/device-tree-bindings/memory-controllers/
H A Dk3-am654-ddrss.txt26 be defined as per the appropriate clock bindings consumer
/openbmc/u-boot/examples/api/
H A Dglue.h28 * are front-end wrappers that are used by the consumer application: they
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/HardwareIsolation/
H A DCreate.interface.yaml41 the consumer of this method need to pass the bmc error log which
/openbmc/u-boot/include/
H A Ddma.h61 * DMA consumer DMA_MEM_TO_DEV (transmit) usage example (based on networking).
81 * DMA consumer DMA_DEV_TO_MEM (receive) usage example (based on networking).
100 * DMA consumer DMA_DEV_TO_MEM (receive) zero-copy usage example (based on
/openbmc/openbmc/poky/meta/files/common-licenses/
H A DMS-PL18 … express warranties, guarantees, or conditions. You may have additional consumer rights under your…

12345