| /Linux-v5.10/virt/lib/ |
| D | irqbypass.c | 91 struct irq_bypass_consumer *consumer; in irq_bypass_register_producer() local
111 list_for_each_entry(consumer, &consumers, node) { in irq_bypass_register_producer()
112 if (consumer->token == producer->token) { in irq_bypass_register_producer()
113 ret = __connect(producer, consumer); in irq_bypass_register_producer()
142 struct irq_bypass_consumer *consumer; in irq_bypass_unregister_producer() local
158 list_for_each_entry(consumer, &consumers, node) { in irq_bypass_unregister_producer()
159 if (consumer->token == producer->token) { in irq_bypass_unregister_producer()
160 __disconnect(producer, consumer); in irq_bypass_unregister_producer()
183 int irq_bypass_register_consumer(struct irq_bypass_consumer *consumer) in irq_bypass_register_consumer() argument
189 if (!consumer->token || in irq_bypass_register_consumer()
[all …]
|
| /Linux-v5.10/Documentation/driver-api/iio/ |
| D | hw-consumer.rst | 2 HW consumer
5 case the buffers between IIO provider and IIO consumer are handled by hardware.
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
[all …]
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | sysfs-class-devlink | 7 denoted as ... above, is of the form <supplier>--<consumer>
8 where <supplier> is the supplier device name and <consumer> is
9 the consumer device name.
16 automatically removed by the driver core when the consumer and
21 - 'consumer unbind'
25 'consumer unbind' means the device link will be removed when
26 the consumer's driver is unbound from the consumer device.
32 when as long as the supplier and consumer devices themselves
35 What: /sys/class/devlink/.../consumer
39 This file is a symlink to the consumer device's sysfs directory.
[all …]
|
| 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. There can be zero or
|
| /Linux-v5.10/kernel/trace/ |
| D | ring_buffer_benchmark.c | 34 static struct task_struct *consumer; variable
267 if (consumer && !(cnt % wakeup_interval)) in ring_buffer_producer()
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()
407 wake_up_process(consumer); in ring_buffer_producer_thread()
440 consumer = kthread_create(ring_buffer_consumer_thread, in ring_buffer_benchmark_init()
442 ret = PTR_ERR(consumer); in ring_buffer_benchmark_init()
443 if (IS_ERR(consumer)) in ring_buffer_benchmark_init()
[all …]
|
| /Linux-v5.10/drivers/staging/iio/Documentation/ |
| 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.
|
| /Linux-v5.10/tools/testing/selftests/bpf/benchs/ |
| D | bench_rename.c | 109 static void *consumer(void *input) in consumer() function
119 .consumer_thread = consumer,
130 .consumer_thread = consumer,
141 .consumer_thread = consumer,
152 .consumer_thread = consumer,
163 .consumer_thread = consumer,
174 .consumer_thread = consumer,
|
| /Linux-v5.10/Documentation/core-api/ |
| 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
118 To the consumer it will show an upper bound as the producer may be busy
121 (2) CIRC_CNT*() are intended to be used in the consumer. To the consumer they
122 will return a lower bound as the consumer controls the tail index, but the
126 To the producer it will show an upper bound as the consumer may be busy
130 producer and consumer become visible cannot be guaranteed as they are
[all …]
|
| /Linux-v5.10/Documentation/devicetree/bindings/net/ |
| D | mdio-mux-multiplexer.txt | 1 Properties for an MDIO bus multiplexer consumer device
3 This is a special case of MDIO mux when MDIO mux is defined as a consumer
13 each child node of mdio bus multiplexer consumer device represent a mdio
21 In below example the Mux producer and consumer are separate nodes.
38 mdio-mux-1 { // Mux consumer
61 mdio-mux-2 { // Mux consumer
|
| /Linux-v5.10/tools/lib/bpf/ |
| D | xsk.c | 90 __u64 consumer; member
173 off->rx.consumer = off_v1.rx.consumer; in xsk_mmap_offsets_v1()
175 off->rx.flags = off_v1.rx.consumer + sizeof(__u32); in xsk_mmap_offsets_v1()
178 off->tx.consumer = off_v1.tx.consumer; in xsk_mmap_offsets_v1()
180 off->tx.flags = off_v1.tx.consumer + sizeof(__u32); in xsk_mmap_offsets_v1()
183 off->fr.consumer = off_v1.fr.consumer; in xsk_mmap_offsets_v1()
185 off->fr.flags = off_v1.fr.consumer + sizeof(__u32); in xsk_mmap_offsets_v1()
188 off->cr.consumer = off_v1.cr.consumer; in xsk_mmap_offsets_v1()
190 off->cr.flags = off_v1.cr.consumer + sizeof(__u32); in xsk_mmap_offsets_v1()
247 fill->consumer = map + off.fr.consumer; in xsk_create_umem_rings()
[all …]
|
| /Linux-v5.10/Documentation/driver-api/ |
| 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
65 non-presence. [Note that it is valid to create a link from the consumer's
66 ``->probe`` callback while the supplier is still probing, but the consumer must
68 the case, for instance, if the consumer has just acquired some resources that
72 is added in the ``->probe`` callback of the supplier or consumer driver, it is
[all …]
|
| /Linux-v5.10/Documentation/power/regulator/ |
| 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::
45 This may happen if the consumer shares the regulator or the regulator has been
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::
[all …]
|
| 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"),
|
| D | overview.rst | 43 Static: consumer does not change its supply voltage or
48 Dynamic: consumer needs to change its supply voltage or
112 Consumer Level: This is defined by consumer drivers
115 e.g. a consumer backlight driver asks for a current increase
121 consumer driver could be used on several different
144 This uses a similar API to the kernel clock interface in that consumer
151 See Documentation/power/regulator/consumer.rst
|
| /Linux-v5.10/Documentation/infiniband/ |
| 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.
|
| /Linux-v5.10/net/xdp/ |
| D | xsk_queue.h | 22 u32 consumer ____cacheline_aligned_in_smp;
205 WRITE_ONCE(q->ring->consumer, q->cached_cons); in __xskq_cons_release()
263 return READ_ONCE(q->ring->producer) - READ_ONCE(q->ring->consumer) == in xskq_cons_is_full()
270 return READ_ONCE(q->ring->producer) - READ_ONCE(q->ring->consumer); in xskq_cons_present_entries()
283 q->cached_cons = READ_ONCE(q->ring->consumer); in xskq_prod_is_full()
358 return READ_ONCE(q->ring->consumer) == READ_ONCE(q->ring->producer); in xskq_prod_is_empty()
|
| /Linux-v5.10/drivers/base/ |
| D | core.c | 142 if (link->consumer == target) in device_is_dependent()
145 ret = device_is_dependent(link->consumer, target); in device_is_dependent()
153 struct device *consumer, in device_link_init_status() argument
158 switch (consumer->links.status) { in device_link_init_status()
175 switch (consumer->links.status) { in device_link_init_status()
214 device_reorder_to_tail(link->consumer, NULL); in device_reorder_to_tail()
325 put_device(link->consumer); in device_link_free()
363 struct device *con = link->consumer; in devlink_add_symlinks()
410 struct device *con = link->consumer; in devlink_remove_symlinks()
517 struct device_link *device_link_add(struct device *consumer, in device_link_add() argument
[all …]
|
| /Linux-v5.10/drivers/net/ethernet/qlogic/qlcnic/ |
| D | qlcnic_io.c | 1366 u32 consumer = sds_ring->consumer; in qlcnic_process_rcv_ring() local
1369 desc = &sds_ring->desc_head[consumer]; in qlcnic_process_rcv_ring()
1392 qlcnic_handle_fw_message(desc_cnt, consumer, sds_ring); in qlcnic_process_rcv_ring()
1404 desc = &sds_ring->desc_head[consumer]; in qlcnic_process_rcv_ring()
1406 consumer = get_next_index(consumer, sds_ring->num_desc); in qlcnic_process_rcv_ring()
1429 sds_ring->consumer = consumer; in qlcnic_process_rcv_ring()
1430 writel(consumer, sds_ring->crb_sts_consumer); in qlcnic_process_rcv_ring()
1542 u32 consumer = sds_ring->consumer; in qlcnic_82xx_process_rcv_ring_diag() local
1544 desc = &sds_ring->desc_head[consumer]; in qlcnic_82xx_process_rcv_ring_diag()
1554 qlcnic_handle_fw_message(desc_cnt, consumer, sds_ring); in qlcnic_82xx_process_rcv_ring_diag()
[all …]
|
| /Linux-v5.10/Documentation/crypto/ |
| 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
|
| /Linux-v5.10/Documentation/devicetree/bindings/mux/ |
| D | mux-controller.txt | 4 A multiplexer (or mux) controller will have one, or several, consumer devices
7 multiplexer needed by each consumer, but a single mux controller can of course
8 control several multiplexers for a single consumer.
29 each consumer. An optional property "mux-control-names" may contain a list of
43 /* One consumer of a 2-way mux controller (one GPIO-line) */
64 for the consumer node in fact asks for a named mux controller, that name is of
|
| /Linux-v5.10/Documentation/devicetree/bindings/clock/ |
| D | ux500.txt | 15 clock in the prcmu-clock node the consumer wants to use.
18 The first cell indicates which PRCC block the consumer
24 The first cell indicates which PRCC block the consumer
|
| /Linux-v5.10/include/uapi/linux/ |
| D | gpio.h | 193 char consumer[GPIO_MAX_NAME_SIZE]; member
221 char consumer[GPIO_MAX_NAME_SIZE]; member
330 char consumer[GPIO_MAX_NAME_SIZE]; member
|
| /Linux-v5.10/drivers/iio/adc/ |
| D | rcar-gyroadc.c | 184 struct regulator *consumer; in rcar_gyroadc_read_raw() local
194 consumer = priv->vref[0]; in rcar_gyroadc_read_raw()
196 consumer = priv->vref[chan->channel]; in rcar_gyroadc_read_raw()
204 if (!consumer) in rcar_gyroadc_read_raw()
228 if (!consumer) in rcar_gyroadc_read_raw()
231 vref = regulator_get_voltage(consumer); in rcar_gyroadc_read_raw()
|
| /Linux-v5.10/drivers/of/unittest-data/ |
| D | tests-phandle.dtsi | 41 consumer-a {
60 consumer-b {
|
| /Linux-v5.10/Documentation/devicetree/bindings/power/ |
| D | power_domain.txt | 7 This device tree binding can be used to bind PM domain consumer devices with
10 domains. A consumer node can refer to the provider by a phandle and a set of
46 The first example above defines a typical PM domain consumer device, which is
49 In the second example the consumer device are partitioned across two PM domains,
|
