| /Linux-v4.19/virt/lib/ |
| D | irqbypass.c | 90 struct irq_bypass_consumer *consumer; in irq_bypass_register_producer() local
110 list_for_each_entry(consumer, &consumers, node) { in irq_bypass_register_producer()
111 if (consumer->token == producer->token) { in irq_bypass_register_producer()
112 int ret = __connect(producer, consumer); in irq_bypass_register_producer()
140 struct irq_bypass_consumer *consumer; in irq_bypass_unregister_producer() local
156 list_for_each_entry(consumer, &consumers, node) { in irq_bypass_unregister_producer()
157 if (consumer->token == producer->token) { in irq_bypass_unregister_producer()
158 __disconnect(producer, consumer); in irq_bypass_unregister_producer()
181 int irq_bypass_register_consumer(struct irq_bypass_consumer *consumer) in irq_bypass_register_consumer() argument
186 if (!consumer->token || in irq_bypass_register_consumer()
[all …]
|
| /Linux-v4.19/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 :c:type:`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-v4.19/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 …]
|
| D | trace_uprobe.c | 45 struct uprobe_consumer consumer; member
229 return tu->consumer.ret_handler != NULL; in is_ret_probe()
261 tu->consumer.handler = uprobe_dispatcher; in alloc_trace_uprobe()
263 tu->consumer.ret_handler = uretprobe_dispatcher; in alloc_trace_uprobe()
906 tu->consumer.filter = filter; in probe_event_enable()
908 ret = uprobe_register(tu->inode, tu->offset, &tu->consumer); in probe_event_enable()
952 uprobe_unregister(tu->inode, tu->offset, &tu->consumer); in probe_event_disable()
1028 return uprobe_apply(tu->inode, tu->offset, &tu->consumer, false); in uprobe_perf_close()
1060 err = uprobe_apply(tu->inode, tu->offset, &tu->consumer, true); in uprobe_perf_open()
1073 tu = container_of(uc, struct trace_uprobe, consumer); in uprobe_perf_filter()
[all …]
|
| /Linux-v4.19/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-v4.19/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-v4.19/Documentation/power/regulator/ |
| D | consumer.txt | 4 This text describes the regulator interface for consumer device drivers.
11 A consumer driver can get access to its supply regulator by calling :-
15 The consumer passes in its struct device pointer and power supply ID. The core
18 regulator that supplies this consumer.
20 To release the regulator the consumer driver should call :-
24 Consumers can be supplied by more than one regulator e.g. codec consumer with
37 A consumer can enable its power supply by calling:-
42 This may happen if the consumer shares the regulator or the regulator has been
45 A consumer can determine if a regulator is enabled by calling :-
52 A consumer can disable its supply when no longer needed by calling :-
[all …]
|
| D | machine.txt | 19 const char *dev_name; /* consumer dev_name() */
20 const char *supply; /* consumer supply - e.g. "vcc" */
26 REGULATOR_SUPPLY("Vcc", "consumer B"),
30 REGULATOR_SUPPLY("Vcc", "consumer A"),
|
| D | overview.txt | 38 Static: consumer does not change its supply voltage or
43 Dynamic: consumer needs to change its supply voltage or
105 Consumer Level: This is defined by consumer drivers
108 e.g. a consumer backlight driver asks for a current increase
114 consumer driver could be used on several different
137 This uses a similar API to the kernel clock interface in that consumer
144 See Documentation/power/regulator/consumer.txt
|
| /Linux-v4.19/Documentation/infiniband/ |
| D | core_locking.txt | 60 example, a consumer may safely call ib_poll_cq() on multiple CPUs
68 allowed for a low-level driver to call a consumer's completion event
82 consumer CQ event callback:
86 /* ... */ consumer CQ event callback:
104 semaphores that could cause deadlock if a consumer calls back into
107 An upper level protocol consumer may begin using an IB device as
109 device. A consumer must finish all cleanup and free all resources
112 A consumer is permitted to sleep in its add and remove methods.
|
| /Linux-v4.19/Documentation/driver-api/ |
| D | device_link.rst | 30 "supplier" device and its "consumer" devices, and it guarantees driver
31 presence on the supplier. The consumer devices are not probed before the
43 whenever and for as long as the consumer is runtime resumed.
50 :c:func:`device_initialize()` has been called for the consumer.
61 represents a driver presence dependency, yet is added from the consumer's
64 consumer in the first place. The onus is thus on the consumer to check
69 consumer driver, it is typically deleted in its ``->remove`` callback for
82 link is added from the consumer's ``->probe`` callback: ``DL_FLAG_RPM_ACTIVE``
85 automatically purged when the consumer fails to probe or later unbinds.
98 the consumer to be deferred indefinitely. This can become a problem if the
[all …]
|
| /Linux-v4.19/drivers/net/ethernet/qlogic/qlcnic/ |
| D | qlcnic_io.c | 1365 u32 consumer = sds_ring->consumer; in qlcnic_process_rcv_ring() local
1368 desc = &sds_ring->desc_head[consumer]; in qlcnic_process_rcv_ring()
1391 qlcnic_handle_fw_message(desc_cnt, consumer, sds_ring); in qlcnic_process_rcv_ring()
1403 desc = &sds_ring->desc_head[consumer]; in qlcnic_process_rcv_ring()
1405 consumer = get_next_index(consumer, sds_ring->num_desc); in qlcnic_process_rcv_ring()
1428 sds_ring->consumer = consumer; in qlcnic_process_rcv_ring()
1429 writel(consumer, sds_ring->crb_sts_consumer); in qlcnic_process_rcv_ring()
1541 u32 consumer = sds_ring->consumer; in qlcnic_82xx_process_rcv_ring_diag() local
1543 desc = &sds_ring->desc_head[consumer]; in qlcnic_82xx_process_rcv_ring_diag()
1553 qlcnic_handle_fw_message(desc_cnt, consumer, sds_ring); in qlcnic_82xx_process_rcv_ring_diag()
[all …]
|
| /Linux-v4.19/arch/arm64/boot/dts/qcom/ |
| D | msm8994-smd-rpm.dtsi | 125 qcom,proxy-consumer-enable;
126 qcom,proxy-consumer-current = <10000>;
142 qcom,proxy-consumer-enable;
143 qcom,proxy-consumer-current = <10000>;
240 qcom,proxy-consumer-enable;
241 qcom,proxy-consumer-current = <10000>;
|
| /Linux-v4.19/samples/bpf/ |
| D | xdpsock_user.c | 86 u32 *consumer; member
104 u32 *consumer; member
172 q->cached_cons = *q->consumer + q->size; in umem_nb_free()
185 q->cached_cons = *q->consumer + q->size; in xq_nb_free()
271 *cq->consumer = cq->cached_cons; in umem_complete_from_kernel()
347 *uq->consumer = uq->cached_cons; in xq_deq()
446 umem->fq.consumer = umem->fq.map + off.fr.consumer; in xdp_umem_configure()
460 umem->cq.consumer = umem->cq.map + off.cr.consumer; in xdp_umem_configure()
537 xsk->rx.consumer = xsk->rx.map + off.rx.consumer; in xsk_configure()
543 xsk->tx.consumer = xsk->tx.map + off.tx.consumer; in xsk_configure()
|
| /Linux-v4.19/drivers/base/ |
| D | core.c | 116 if (link->consumer == target) in device_is_dependent()
119 ret = device_is_dependent(link->consumer, target); in device_is_dependent()
142 device_reorder_to_tail(link->consumer, NULL); in device_reorder_to_tail()
195 struct device_link *device_link_add(struct device *consumer, in device_link_add() argument
200 if (!consumer || !supplier || in device_link_add()
214 || device_is_dependent(consumer, supplier)) { in device_link_add()
220 if (link->consumer == consumer) { in device_link_add()
239 pm_runtime_new_link(consumer); in device_link_add()
245 if (consumer->links.status == DL_DEV_PROBING) in device_link_add()
251 get_device(consumer); in device_link_add()
[all …]
|
| /Linux-v4.19/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-v4.19/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-v4.19/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
|
| D | csr,atlas7-car.txt | 9 The clock consumer should specify the desired clock by having the clock
13 The reset consumer should specify the desired reset by having the reset
|
| /Linux-v4.19/net/xdp/ |
| D | xsk_queue.h | 18 u32 consumer ____cacheline_aligned_in_smp;
73 q->cons_tail = READ_ONCE(q->ring->consumer); in xskq_nb_free()
108 WRITE_ONCE(q->ring->consumer, q->cons_tail); in xskq_peek_addr()
206 WRITE_ONCE(q->ring->consumer, q->cons_tail); in xskq_peek_desc()
|
| /Linux-v4.19/Documentation/networking/ |
| D | af_xdp.rst | 64 single-consumer / single-producer (for performance reasons), the new
116 The UMEM has two single-producer/single-consumer rings, that are used
124 TX. All rings are single-producer/single-consumer, so the user-space
133 The rings are head(producer)/tail(consumer) based rings. A producer
135 producer member, and increasing the producer index. A consumer reads
136 the data ring at the index pointed out by struct xdp_ring consumer
137 member, and increasing the consumer index.
229 // __u32 *consumer;
235 // __u32 *consumer;
247 __u32 entries = *ring->producer - *ring->consumer;
[all …]
|
| /Linux-v4.19/drivers/iio/adc/ |
| D | rcar-gyroadc.c | 193 struct regulator *consumer; in rcar_gyroadc_read_raw() local
203 consumer = priv->vref[0]; in rcar_gyroadc_read_raw()
205 consumer = priv->vref[chan->channel]; in rcar_gyroadc_read_raw()
213 if (!consumer) in rcar_gyroadc_read_raw()
237 if (!consumer) in rcar_gyroadc_read_raw()
240 vref = regulator_get_voltage(consumer); in rcar_gyroadc_read_raw()
|
| /Linux-v4.19/drivers/of/unittest-data/ |
| D | tests-phandle.dtsi | 41 consumer-a {
60 consumer-b {
|
| /Linux-v4.19/Documentation/devicetree/bindings/reset/ |
| D | ti,sci-reset.txt | 21 - #reset-cells : Should be 2. Please see the reset consumer node below for
26 Each of the reset consumer nodes should have the following properties,
47 consumer (a DSP device) on the 66AK2G SoC.
|
| /Linux-v4.19/Documentation/nvmem/ |
| D | nvmem.txt | 23 representation for consumer devices to go get the data they require (MAC
67 3. NVMEM cell based consumer APIs
84 Once the usage of the cell is finished the consumer should call *nvmem_cell_put()
87 4. Direct NVMEM device based consumer APIs
115 When a consumer no longer needs the NVMEM, it has to release the reference
|
