| /Linux-v5.4/virt/lib/ |
| D | irqbypass.c | 87 struct irq_bypass_consumer *consumer; in irq_bypass_register_producer() local
107 list_for_each_entry(consumer, &consumers, node) { in irq_bypass_register_producer()
108 if (consumer->token == producer->token) { in irq_bypass_register_producer()
109 int ret = __connect(producer, consumer); in irq_bypass_register_producer()
137 struct irq_bypass_consumer *consumer; in irq_bypass_unregister_producer() local
153 list_for_each_entry(consumer, &consumers, node) { in irq_bypass_unregister_producer()
154 if (consumer->token == producer->token) { in irq_bypass_unregister_producer()
155 __disconnect(producer, consumer); in irq_bypass_unregister_producer()
178 int irq_bypass_register_consumer(struct irq_bypass_consumer *consumer) in irq_bypass_register_consumer() argument
183 if (!consumer->token || in irq_bypass_register_consumer()
[all …]
|
| /Linux-v5.4/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-v5.4/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 | 64 struct uprobe_consumer consumer; member
281 return tu->consumer.ret_handler != NULL; in is_ret_probe()
359 tu->consumer.handler = uprobe_dispatcher; in alloc_trace_uprobe()
361 tu->consumer.ret_handler = uretprobe_dispatcher; in alloc_trace_uprobe()
1050 tu->consumer.filter = filter; in trace_uprobe_enable()
1055 tu->ref_ctr_offset, &tu->consumer); in trace_uprobe_enable()
1057 ret = uprobe_register(tu->inode, tu->offset, &tu->consumer); in trace_uprobe_enable()
1077 uprobe_unregister(tu->inode, tu->offset, &tu->consumer); in __probe_event_disable()
1230 return uprobe_apply(tu->inode, tu->offset, &tu->consumer, false); in uprobe_perf_close()
1262 err = uprobe_apply(tu->inode, tu->offset, &tu->consumer, true); in uprobe_perf_open()
[all …]
|
| /Linux-v5.4/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.4/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.4/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.4/Documentation/driver-api/ |
| D | device_link.rst | 33 "supplier" device and its "consumer" devices, and it guarantees driver
34 presence on the supplier. The consumer devices are not probed before the
46 whenever and for as long as the consumer is runtime resumed.
53 :c:func:`device_initialize()` has been called for the consumer.
64 represents a driver presence dependency, yet is added from the consumer's
67 consumer in the first place. The onus is thus on the consumer to check
69 non-presence. [Note that it is valid to create a link from the consumer's
70 ``->probe`` callback while the supplier is still probing, but the consumer must
72 the case, for instance, if the consumer has just acquired some resources that
76 is added in the ``->probe`` callback of the supplier or consumer driver, it is
[all …]
|
| /Linux-v5.4/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.4/Documentation/infiniband/ |
| D | core_locking.rst | 64 example, a consumer may safely call ib_poll_cq() on multiple CPUs
73 allowed for a low-level driver to call a consumer's completion event
87 consumer CQ event callback:
91 /* ... */ consumer CQ event callback:
110 semaphores that could cause deadlock if a consumer calls back into
113 An upper level protocol consumer may begin using an IB device as
115 device. A consumer must finish all cleanup and free all resources
118 A consumer is permitted to sleep in its add and remove methods.
|
| /Linux-v5.4/drivers/net/ethernet/qlogic/qlcnic/ |
| D | qlcnic_io.c | 1367 u32 consumer = sds_ring->consumer; in qlcnic_process_rcv_ring() local
1370 desc = &sds_ring->desc_head[consumer]; in qlcnic_process_rcv_ring()
1393 qlcnic_handle_fw_message(desc_cnt, consumer, sds_ring); in qlcnic_process_rcv_ring()
1405 desc = &sds_ring->desc_head[consumer]; in qlcnic_process_rcv_ring()
1407 consumer = get_next_index(consumer, sds_ring->num_desc); in qlcnic_process_rcv_ring()
1430 sds_ring->consumer = consumer; in qlcnic_process_rcv_ring()
1431 writel(consumer, sds_ring->crb_sts_consumer); in qlcnic_process_rcv_ring()
1543 u32 consumer = sds_ring->consumer; in qlcnic_82xx_process_rcv_ring_diag() local
1545 desc = &sds_ring->desc_head[consumer]; in qlcnic_82xx_process_rcv_ring_diag()
1555 qlcnic_handle_fw_message(desc_cnt, consumer, sds_ring); in qlcnic_82xx_process_rcv_ring_diag()
[all …]
|
| /Linux-v5.4/arch/arm64/boot/dts/qcom/ |
| D | msm8994-smd-rpm.dtsi | 117 qcom,proxy-consumer-enable;
118 qcom,proxy-consumer-current = <10000>;
134 qcom,proxy-consumer-enable;
135 qcom,proxy-consumer-current = <10000>;
232 qcom,proxy-consumer-enable;
233 qcom,proxy-consumer-current = <10000>;
|
| /Linux-v5.4/drivers/base/ |
| D | core.c | 130 if (link->consumer == target) in device_is_dependent()
133 ret = device_is_dependent(link->consumer, target); in device_is_dependent()
141 struct device *consumer, in device_link_init_status() argument
146 switch (consumer->links.status) { in device_link_init_status()
163 switch (consumer->links.status) { in device_link_init_status()
200 device_reorder_to_tail(link->consumer, NULL); in device_reorder_to_tail()
288 struct device_link *device_link_add(struct device *consumer, in device_link_add() argument
293 if (!consumer || !supplier || flags & ~DL_ADD_VALID_FLAGS || in device_link_add()
319 || device_is_dependent(consumer, supplier)) { in device_link_add()
333 if (link->consumer != consumer) in device_link_add()
[all …]
|
| /Linux-v5.4/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.4/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.4/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.4/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.4/Documentation/devicetree/bindings/interconnect/ |
| D | interconnect.txt | 13 to consumer drivers. These capabilities can be throughput, latency, priority
14 etc. The consumer drivers set constraints on interconnect path (or endpoints)
40 can be multiple interconnect providers on a SoC and the consumer may consume
|
| /Linux-v5.4/drivers/of/unittest-data/ |
| D | tests-phandle.dtsi | 41 consumer-a {
60 consumer-b {
|
| /Linux-v5.4/tools/lib/bpf/ |
| D | xsk.c | 211 fill->consumer = map + off.fr.consumer; in xsk_umem__create_v0_0_4()
228 comp->consumer = map + off.cr.consumer; in xsk_umem__create_v0_0_4()
573 rx->consumer = rx_map + off.rx.consumer; in xsk_socket__create()
592 tx->consumer = tx_map + off.tx.consumer; in xsk_socket__create()
|
| D | xsk.h | 33 __u32 *consumer; \
99 r->cached_cons = *r->consumer + r->size; in xsk_prod_nb_free()
163 *cons->consumer += nb; in xsk_ring_cons__release()
|
| /Linux-v5.4/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-v5.4/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.
245 // __u32 *consumer;
251 // __u32 *consumer;
263 __u32 entries = *ring->producer - *ring->consumer;
[all …]
|
