| /kernel/linux/linux-4.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()
135 * and disconnect it from any connected IRQ consumer.
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()
175 * irq_bypass_register_consumer - register IRQ bypass consumer
[all …]
|
| /kernel/linux/linux-5.10/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 ret = __connect(producer, consumer); in irq_bypass_register_producer()
133 * and disconnect it from any connected IRQ consumer.
138 struct irq_bypass_consumer *consumer; in irq_bypass_unregister_producer() local
154 list_for_each_entry(consumer, &consumers, node) { in irq_bypass_unregister_producer()
155 if (consumer->token == producer->token) { in irq_bypass_unregister_producer()
156 __disconnect(producer, consumer); in irq_bypass_unregister_producer()
173 * irq_bypass_register_consumer - register IRQ bypass consumer
[all …]
|
| /kernel/linux/linux-4.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 …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| 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.
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 and is of the form
|
| /kernel/linux/linux-5.10/drivers/pps/ |
| D | kc.c | 3 * PPS kernel consumer API
23 /* state variables to bind kernel consumer */
25 /* PPS API (RFC 2783): current source and mode for kernel consumer */
27 static int pps_kc_hardpps_mode; /* mode bits for kernel consumer */
29 /* pps_kc_bind - control PPS kernel consumer binding
31 * @bind_args: kernel consumer bind parameters
33 * This function is used to bind or unbind PPS kernel consumer according to
38 /* Check if another consumer is already bound */ in pps_kc_bind()
47 " consumer\n"); in pps_kc_bind()
50 dev_err(pps->dev, "selected kernel consumer" in pps_kc_bind()
[all …]
|
| /kernel/linux/linux-5.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 …]
|
| /kernel/linux/linux-4.19/Documentation/power/regulator/ |
| D | overview.txt | 35 o Consumer - Electronic device that is supplied power by a regulator.
38 Static: consumer does not change its supply voltage or
43 Dynamic: consumer needs to change its supply voltage or
53 Regulator -+-> Switch-1 -+-> Switch-2 --> [Consumer A]
55 | +-> [Consumer B], [Consumer C]
57 +-> [Consumer D], [Consumer E]
63 Domain 3: Consumer A.
72 Regulator-1 -+-> Regulator-2 -+-> [Consumer A]
74 +-> [Consumer B]
78 Domain 1: Regulator-2, Consumer B.
[all …]
|
| D | machine.txt | 9 Regulator-1 -+-> Regulator-2 --> [Consumer A @ 1.8 - 2.0V]
11 +-> [Consumer B @ 3.3V]
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"),
33 This maps Regulator-1 to the 'Vcc' supply for Consumer B and maps Regulator-2
34 to the 'Vcc' supply for Consumer A.
58 with the core so that Regulator-1 is also enabled when Consumer A enables its
|
| D | consumer.txt | 1 Regulator Consumer Driver Interface
4 This text describes the regulator interface for consumer device drivers.
8 1. Consumer Regulator Access (static & dynamic 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
[all …]
|
| /kernel/linux/linux-5.10/Documentation/power/regulator/ |
| D | overview.rst | 39 - Consumer
43 Static: consumer does not change its supply voltage or
48 Dynamic: consumer needs to change its supply voltage or
59 Regulator -+-> Switch-1 -+-> Switch-2 --> [Consumer A]
61 | +-> [Consumer B], [Consumer C]
63 +-> [Consumer D], [Consumer E]
69 - Domain 3: Consumer A.
78 Regulator-1 -+-> Regulator-2 -+-> [Consumer A]
80 +-> [Consumer B]
84 - Domain 1: Regulator-2, Consumer B.
[all …]
|
| D | consumer.rst | 2 Regulator Consumer Driver Interface
5 This text describes the regulator interface for consumer device drivers.
9 1. Consumer Regulator Access (static & dynamic 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
[all …]
|
| /kernel/linux/linux-4.19/drivers/pps/ |
| D | kc.c | 2 * PPS kernel consumer API
36 /* state variables to bind kernel consumer */
38 /* PPS API (RFC 2783): current source and mode for kernel consumer */
40 static int pps_kc_hardpps_mode; /* mode bits for kernel consumer */
42 /* pps_kc_bind - control PPS kernel consumer binding
44 * @bind_args: kernel consumer bind parameters
46 * This function is used to bind or unbind PPS kernel consumer according to
51 /* Check if another consumer is already bound */ in pps_kc_bind()
60 " consumer\n"); in pps_kc_bind()
63 dev_err(pps->dev, "selected kernel consumer" in pps_kc_bind()
[all …]
|
| /kernel/linux/linux-5.10/net/xdp/ |
| D | xsk_queue.h | 18 /* Hinder the adjacent cache prefetcher to prefetch the consumer
22 u32 consumer ____cacheline_aligned_in_smp;
50 * ring, the kernel is the producer and user space is the consumer. For
51 * the Tx and fill rings, the kernel is the consumer and user space is
54 * producer consumer
56 * if (LOAD ->consumer) { LOAD ->producer
60 * STORE ->producer STORE ->consumer
66 * the producer pointer. If this barrier was missing, the consumer
68 * before the producer has written the new data. The consumer would in
71 * (C) protects the consumer from speculatively loading the data before
[all …]
|
| /kernel/linux/linux-5.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 …]
|
| /kernel/linux/linux-5.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 …]
|
| /kernel/linux/linux-4.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 …]
|
| /kernel/linux/linux-5.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.
|
| /kernel/linux/linux-4.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.
|
| /kernel/linux/linux-4.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
66 non-presence. [Note that it is valid to create a link from the consumer's
67 ``->probe`` callback while the supplier is still probing, but the consumer must
69 the case, for instance, if the consumer has just acquired some resources that
73 is added in the ``->probe`` callback of the supplier or consumer driver, it is
[all …]
|
| /kernel/linux/linux-4.19/drivers/gpio/ |
| D | devres.c | 20 #include <linux/gpio/consumer.h>
56 * @dev: GPIO consumer
57 * @con_id: function within the GPIO consumer
74 * @dev: GPIO consumer
75 * @con_id: function within the GPIO consumer
92 * @dev: GPIO consumer
93 * @con_id: function within the GPIO consumer
94 * @idx: index of the GPIO to obtain in the consumer
132 * @index: index of the GPIO to obtain for the consumer
172 * @dev: GPIO consumer
[all …]
|
| /kernel/linux/linux-5.10/kernel/trace/ |
| D | ring_buffer_benchmark.c | 34 static struct task_struct *consumer; variable
55 MODULE_PARM_DESC(consumer_nice, "nice prio for consumer");
61 MODULE_PARM_DESC(consumer_fifo, "use fifo for consumer: 0 - disabled, 1 - low prio, 2 - fifo");
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()
307 trace_printk("Running Consumer at SCHED_FIFO %s\n", in ring_buffer_producer()
310 trace_printk("Running Consumer at nice: %d\n", in ring_buffer_producer()
406 if (consumer) { in ring_buffer_producer_thread()
[all …]
|
| /kernel/linux/linux-4.19/arch/arm/mach-sti/ |
| D | Kconfig | 2 bool "STMicroelectronics Consumer Electronics SOCs"
29 bool "STiH415 STMicroelectronics Consumer Electronics family"
32 This enables support for STMicroelectronics Digital Consumer
38 bool "STiH416 STMicroelectronics Consumer Electronics family"
41 This enables support for STMicroelectronics Digital Consumer
47 bool "STiH407 STMicroelectronics Consumer Electronics family"
51 This enables support for STMicroelectronics Digital Consumer
|
| /kernel/linux/linux-5.10/arch/arm/mach-sti/ |
| D | Kconfig | 3 bool "STMicroelectronics Consumer Electronics SOCs"
30 bool "STiH415 STMicroelectronics Consumer Electronics family"
33 This enables support for STMicroelectronics Digital Consumer
39 bool "STiH416 STMicroelectronics Consumer Electronics family"
42 This enables support for STMicroelectronics Digital Consumer
48 bool "STiH407 STMicroelectronics Consumer Electronics family"
52 This enables support for STMicroelectronics Digital Consumer
|
| /kernel/linux/linux-4.19/kernel/trace/ |
| D | ring_buffer_benchmark.c | 34 static struct task_struct *consumer; variable
55 MODULE_PARM_DESC(consumer_nice, "nice prio for consumer");
61 MODULE_PARM_DESC(consumer_fifo, "fifo prio for consumer");
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()
307 trace_printk("Running Consumer at nice: %d\n", in ring_buffer_producer()
310 trace_printk("Running Consumer at SCHED_FIFO %d\n", in ring_buffer_producer()
406 if (consumer) { in ring_buffer_producer_thread()
[all …]
|