/openbmc/linux/virt/lib/ |
H A D | irqbypass.c | 87 struct irq_bypass_consumer *consumer; in irq_bypass_register_producer() local 109 ret = __connect(producer, consumer); in irq_bypass_register_producer() 138 struct irq_bypass_consumer *consumer; in irq_bypass_unregister_producer() local 156 __disconnect(producer, consumer); in irq_bypass_unregister_producer() 185 if (!consumer->token || in irq_bypass_register_consumer() 186 !consumer->add_producer || !consumer->del_producer) in irq_bypass_register_consumer() 197 if (tmp->token == consumer->token || tmp == consumer) { in irq_bypass_register_consumer() 236 if (!consumer->token) in irq_bypass_unregister_consumer() 247 if (tmp != consumer) in irq_bypass_unregister_consumer() 252 __disconnect(producer, consumer); in irq_bypass_unregister_consumer() [all …]
|
/openbmc/linux/Documentation/driver-api/iio/ |
H A D | hw-consumer.rst | 2 HW consumer 6 The Industrial I/O HW consumer offers a way to bond these IIO devices without 8 :file:`drivers/iio/buffer/hw-consumer.c` 11 * struct iio_hw_consumer — Hardware consumer structure 12 * :c:func:`iio_hw_consumer_alloc` — Allocate IIO hardware consumer 13 * :c:func:`iio_hw_consumer_free` — Free IIO hardware consumer 14 * :c:func:`iio_hw_consumer_enable` — Enable IIO hardware consumer 15 * :c:func:`iio_hw_consumer_disable` — Disable IIO hardware consumer 18 HW consumer setup 22 A typical IIO HW consumer setup looks like this:: [all …]
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-class-devlink | 7 denoted as ... above, is of the form <supplier>--<consumer> 8 where <supplier> is the supplier bus:device name and <consumer> 9 is the consumer bus:device name. 21 - 'consumer unbind' 26 the consumer's driver is unbound from the consumer device. 35 What: /sys/class/devlink/.../consumer 48 runtime suspend while the consumer is active. 63 consumer devices have been bound to their corresponding 76 - 'consumer probing' 89 available to supply resources to the consumer device. [all …]
|
H A D | sysfs-devices-consumer | 1 What: /sys/devices/.../consumer:<consumer> 5 The /sys/devices/.../consumer:<consumer> are symlinks to device 6 links where this device is the supplier. <consumer> denotes the 7 name of the consumer in that device link and is of the form
|
/openbmc/linux/kernel/trace/ |
H A D | ring_buffer_benchmark.c | 268 wake_up_process(consumer); in ring_buffer_producer() 286 if (consumer) { in ring_buffer_producer() 293 wake_up_process(consumer); in ring_buffer_producer() 406 if (consumer) { in ring_buffer_producer_thread() 442 ret = PTR_ERR(consumer); in ring_buffer_benchmark_init() 443 if (IS_ERR(consumer)) in ring_buffer_benchmark_init() 459 sched_set_fifo(consumer); in ring_buffer_benchmark_init() 476 if (consumer) in ring_buffer_benchmark_init() 477 kthread_stop(consumer); in ring_buffer_benchmark_init() 487 if (consumer) in ring_buffer_benchmark_exit() [all …]
|
/openbmc/linux/drivers/gpu/drm/panel/ |
H A D | panel-boe-bf060y8m-aj0.c | 173 regulator_disable(boe->vregs[BF060Y8M_VREG_VDDIO].consumer); in boe_bf060y8m_aj0_prepare() 175 regulator_disable(boe->vregs[BF060Y8M_VREG_VCC].consumer); in boe_bf060y8m_aj0_prepare() 177 regulator_disable(boe->vregs[BF060Y8M_VREG_EL_VSS].consumer); in boe_bf060y8m_aj0_prepare() 179 regulator_disable(boe->vregs[BF060Y8M_VREG_EL_VDD].consumer); in boe_bf060y8m_aj0_prepare() 306 vreg = boe->vregs[BF060Y8M_VREG_VCC].consumer; in boe_bf060y8m_aj0_init_vregs() 311 vreg = boe->vregs[BF060Y8M_VREG_VDDIO].consumer; in boe_bf060y8m_aj0_init_vregs() 316 vreg = boe->vregs[BF060Y8M_VREG_VCI].consumer; in boe_bf060y8m_aj0_init_vregs() 321 vreg = boe->vregs[BF060Y8M_VREG_EL_VDD].consumer; in boe_bf060y8m_aj0_init_vregs() 327 vreg = boe->vregs[BF060Y8M_VREG_EL_VSS].consumer; in boe_bf060y8m_aj0_init_vregs() 341 vreg = boe->vregs[BF060Y8M_VREG_VDDIO].consumer; in boe_bf060y8m_aj0_init_vregs() [all …]
|
/openbmc/linux/drivers/staging/iio/Documentation/ |
H A D | inkernel.txt | 20 consumer_dev_name allows identification of the consumer device. 21 This are then used to find the channel mapping from the consumer device (see 24 Finally consumer_channel is a string identifying the channel to the consumer. 37 to associate a given channel with the consumer requesting it. 39 Acting as an IIO consumer (consumer.h) 41 The consumer first has to obtain an iio_channel structure from the core 55 with a given consumer. This is useful for generic drivers such as 57 consumer driver. To do this, use iio_channel_get_all.
|
/openbmc/linux/Documentation/networking/ |
H A D | tls-handshake.rst | 31 kernel consumer might require a TLS handshake. Handshake agents listen 46 A kernel TLS consumer initiates a client-side TLS handshake on an open 67 while the handshake is in progress. The consumer must also have 75 The consumer can provide a NUL-terminated hostname in the @ta_peername 86 that are instantiated by the consumer before making the handshake 91 To request an x.509-authenticated TLS session, the consumer fills in 113 However, in this case, the consumer fills in the @ta_my_peerids array 147 or other exigent event, the consumer can invoke: 174 The consumer provides a cookie in the @ta_data field of the 210 While a handshake is under way, the kernel consumer must alter the [all …]
|
/openbmc/linux/Documentation/core-api/ |
H A D | circular-buffers.rst | 15 (2) Memory barriers for when the producer and the consumer of objects in the 19 producer and just one consumer. It is possible to handle multiple producers by 31 - The consumer. 44 (2) A 'tail' index - the point at which the consumer finds the next item in 115 but the consumer may still be depleting the buffer on another CPU and 121 (2) CIRC_CNT*() are intended to be used in the consumer. To the consumer they 130 producer and consumer become visible cannot be guaranteed as they are 173 wake_up(consumer); 186 element currently being read by the consumer. Therefore, the unlock-lock 188 ordering between the read of the index indicating that the consumer has [all …]
|
/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/linux/Documentation/driver-api/ |
H A D | device_link.rst | 29 "supplier" device and its "consumer" devices, and it guarantees driver 30 presence on the supplier. The consumer devices are not probed before the 42 whenever and for as long as the consumer is runtime resumed. 49 :c:func:`device_initialize()` has been called for the consumer. 60 represents a driver presence dependency, yet is added from the consumer's 63 consumer in the first place. The onus is thus on the consumer to check 114 consumer will never be probed. 160 runtime PM integration is added from the busmaster device (consumer) 230 To ensure this, upon addition of the device link the consumer and the 237 on the consumer or any children or consumers of the consumer. [all …]
|
H A D | reset.rst | 13 the `consumer driver interface <#consumer-driver-interface>`__ (`API reference 14 <#reset-consumer-api>`__), which allows peripheral drivers to request control 49 Reset consumer 104 consumer has requested it to be deasserted. 112 requesting a pulse from any consumer driver will reset all connected 175 the `reset consumer API <#reset-consumer-api>`__ and the `reset controller 178 Reset consumer API
|
/openbmc/linux/arch/powerpc/platforms/pseries/ |
H A D | plpks.c | 44 u8 consumer; member 132 u8 *password, consumer = PLPKS_OS_OWNER; in plpks_gen_password() local 146 rc = plpar_hcall(H_PKS_GEN_PASSWORD, retbuf, consumer, 0, in plpks_gen_password() 171 static struct plpks_auth *construct_auth(u8 consumer) in construct_auth() argument 175 if (consumer > PLPKS_OS_OWNER) in construct_auth() 185 auth->consumer = consumer; in construct_auth() 187 if (consumer == PLPKS_FW_OWNER || consumer == PLPKS_BOOTLOADER_OWNER) in construct_auth() 557 static int plpks_read_var(u8 consumer, struct plpks_var *var) in plpks_read_var() argument 568 auth = construct_auth(consumer); in plpks_read_var() 572 if (consumer == PLPKS_OS_OWNER) { in plpks_read_var() [all …]
|
/openbmc/linux/Documentation/power/regulator/ |
H A D | consumer.rst | 5 This text describes the regulator interface for consumer device drivers. 12 A consumer driver can get access to its supply regulator by calling :: 16 The consumer passes in its struct device pointer and power supply ID. The core 19 regulator that supplies this consumer. 21 To release the regulator the consumer driver should call :: 25 Consumers can be supplied by more than one regulator e.g. codec consumer with 39 A consumer can enable its power supply by calling:: 48 A consumer can determine if a regulator is enabled by calling:: 55 A consumer can disable its supply when no longer needed by calling:: 75 Some consumer drivers need to be able to dynamically change their supply [all …]
|
H A D | machine.rst | 20 const char *dev_name; /* consumer dev_name() */ 21 const char *supply; /* consumer supply - e.g. "vcc" */ 27 REGULATOR_SUPPLY("Vcc", "consumer B"), 31 REGULATOR_SUPPLY("Vcc", "consumer A"),
|
/openbmc/linux/Documentation/infiniband/ |
H A D | core_locking.rst | 62 example, a consumer may safely call ib_poll_cq() on multiple CPUs 71 allowed for a low-level driver to call a consumer's completion event 85 consumer CQ event callback: 89 /* ... */ consumer CQ event callback: 108 semaphores that could cause deadlock if a consumer calls back into 111 An upper level protocol consumer may begin using an IB device as 113 device. A consumer must finish all cleanup and free all resources 116 A consumer is permitted to sleep in its add and remove methods.
|
/openbmc/linux/Documentation/devicetree/bindings/net/ |
H A D | mdio-mux-multiplexer.yaml | 7 title: Properties for an MDIO bus multiplexer consumer device 13 This is a special case of MDIO mux when MDIO mux is defined as a consumer 43 mdio-mux-1 { // Mux consumer 63 mdio-mux-2 { // Mux consumer
|
/openbmc/linux/drivers/platform/x86/intel/int3472/ |
H A D | tps68470.c | 107 struct acpi_device *consumer; in skl_int3472_fill_clk_pdata() local 112 for_each_acpi_consumer_dev(adev, consumer) in skl_int3472_fill_clk_pdata() 128 for_each_acpi_consumer_dev(adev, consumer) { in skl_int3472_fill_clk_pdata() 130 acpi_dev_name(consumer)); in skl_int3472_fill_clk_pdata() 132 acpi_dev_put(consumer); in skl_int3472_fill_clk_pdata()
|
/openbmc/linux/drivers/base/ |
H A D | core.c | 83 link->consumer = con; in __fwnode_link_add() 733 if (!consumer || !supplier || consumer == supplier || in device_link_add() 792 if (link->consumer != consumer) in device_link_add() 857 get_device(consumer); in device_link_add() 858 link->consumer = consumer; in device_link_add() 867 dev_bus_name(consumer), dev_name(consumer)); in device_link_add() 899 dev_dbg(consumer, in device_link_add() 986 if (link->consumer == consumer) { in device_link_remove() 1606 struct device *consumer = link->consumer; in device_links_unbind_consumers() local 1608 get_device(consumer); in device_links_unbind_consumers() [all …]
|
/openbmc/linux/drivers/net/ethernet/qlogic/qlcnic/ |
H A D | qlcnic_io.c | 1367 u32 consumer = sds_ring->consumer; in qlcnic_process_rcv_ring() local 1431 sds_ring->consumer = consumer; in qlcnic_process_rcv_ring() 1544 u32 consumer = sds_ring->consumer; in qlcnic_82xx_process_rcv_ring_diag() local 1567 consumer = get_next_index(consumer, sds_ring->num_desc); in qlcnic_82xx_process_rcv_ring_diag() 1570 sds_ring->consumer = consumer; in qlcnic_82xx_process_rcv_ring_diag() 1890 u32 consumer = sds_ring->consumer; in qlcnic_83xx_process_rcv_ring() local 1924 consumer = get_next_index(consumer, sds_ring->num_desc); in qlcnic_83xx_process_rcv_ring() 1943 sds_ring->consumer = consumer; in qlcnic_83xx_process_rcv_ring() 2211 u32 consumer = sds_ring->consumer; in qlcnic_83xx_process_rcv_ring_diag() local 2224 consumer = get_next_index(consumer, sds_ring->num_desc); in qlcnic_83xx_process_rcv_ring_diag() [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/mux/ |
H A D | mux-consumer.yaml | 4 $id: http://devicetree.org/schemas/mux/mux-consumer.yaml# 7 title: Common multiplexer controller consumer 24 each consumer. An optional property "mux-control-names" may contain a list of 34 the consumers want to control the mux controller. If the consumer needs 36 "mux-controls" can be used. If the consumer needs to set the mux
|
/openbmc/linux/drivers/clk/ |
H A D | clk-tps68470.c | 203 struct tps68470_clk_consumer *consumer; in tps68470_clk_probe() local 229 consumer = &pdata->consumers[i]; in tps68470_clk_probe() 232 consumer->consumer_con_id, in tps68470_clk_probe() 233 consumer->consumer_dev_name); in tps68470_clk_probe()
|
/openbmc/linux/Documentation/crypto/ |
H A D | intro.rst | 50 transformation objects is held by a crypto API consumer or another 52 consumer requests a transformation implementation. The consumer is then 68 returned to the consumer. Therefore, please refer to all initialization 69 API calls that refer to the data structure type a consumer is expected
|
/openbmc/linux/tools/testing/selftests/bpf/ |
H A D | xsk.h | 34 __u32 *consumer; \ 100 r->cached_cons = __atomic_load_n(r->consumer, __ATOMIC_ACQUIRE); in xsk_prod_nb_free() 164 __atomic_store_n(cons->consumer, *cons->consumer + nb, __ATOMIC_RELEASE); in xsk_ring_cons__release()
|