| /linux/virt/lib/ |
| H A 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()
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()
179 int irq_bypass_register_consumer(struct irq_bypass_consumer *consumer) in irq_bypass_register_consumer() argument
185 if (!consumer->token || in irq_bypass_register_consumer()
[all …]
|
| /linux/Documentation/driver-api/iio/ |
| H A 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/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.
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 …]
|
| 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
|
| /linux/kernel/trace/ |
| H A D | ring_buffer_benchmark.c | 34 static struct task_struct *consumer; variable
269 if (consumer && !(cnt % wakeup_interval)) in ring_buffer_producer()
270 wake_up_process(consumer); in ring_buffer_producer()
288 if (consumer) { in ring_buffer_producer()
295 wake_up_process(consumer); in ring_buffer_producer()
408 if (consumer) { in ring_buffer_producer_thread()
409 wake_up_process(consumer); in ring_buffer_producer_thread()
442 consumer = kthread_create(ring_buffer_consumer_thread, in ring_buffer_benchmark_init()
444 ret = PTR_ERR(consumer); in ring_buffer_benchmark_init()
445 if (IS_ERR(consumer)) in ring_buffer_benchmark_init()
[all …]
|
| /linux/drivers/gpu/drm/panel/ |
| H A D | panel-boe-bf060y8m-aj0.c | 136 ret = regulator_enable(boe->vregs[BF060Y8M_VREG_EL_VDD].consumer); in boe_bf060y8m_aj0_prepare()
139 ret = regulator_enable(boe->vregs[BF060Y8M_VREG_EL_VSS].consumer); in boe_bf060y8m_aj0_prepare()
143 ret = regulator_enable(boe->vregs[BF060Y8M_VREG_VCC].consumer); in boe_bf060y8m_aj0_prepare()
147 ret = regulator_enable(boe->vregs[BF060Y8M_VREG_VDDIO].consumer); in boe_bf060y8m_aj0_prepare()
151 ret = regulator_enable(boe->vregs[BF060Y8M_VREG_VCI].consumer); in boe_bf060y8m_aj0_prepare()
168 regulator_disable(boe->vregs[BF060Y8M_VREG_VDDIO].consumer); in boe_bf060y8m_aj0_prepare()
170 regulator_disable(boe->vregs[BF060Y8M_VREG_VCC].consumer); in boe_bf060y8m_aj0_prepare()
172 regulator_disable(boe->vregs[BF060Y8M_VREG_EL_VSS].consumer); in boe_bf060y8m_aj0_prepare()
174 regulator_disable(boe->vregs[BF060Y8M_VREG_EL_VDD].consumer); in boe_bf060y8m_aj0_prepare()
297 vreg = boe->vregs[BF060Y8M_VREG_VCC].consumer; in boe_bf060y8m_aj0_init_vregs()
[all …]
|
| H A D | panel-novatek-nt35950.c | 335 ret = regulator_is_supported_voltage(nt->vregs[0].consumer, in nt35950_sharp_init_vregs()
339 ret = regulator_is_supported_voltage(nt->vregs[1].consumer, in nt35950_sharp_init_vregs()
344 ret = regulator_is_supported_voltage(nt->vregs[2].consumer, in nt35950_sharp_init_vregs()
349 ret = regulator_is_supported_voltage(nt->vregs[3].consumer, in nt35950_sharp_init_vregs()
362 ret = regulator_enable(nt->vregs[0].consumer); in nt35950_prepare()
367 ret = regulator_enable(nt->vregs[3].consumer); in nt35950_prepare()
372 ret = regulator_enable(nt->vregs[1].consumer); in nt35950_prepare()
376 ret = regulator_enable(nt->vregs[2].consumer); in nt35950_prepare()
|
| /linux/Documentation/admin-guide/gpio/ |
| H A D | gpio-virtuser.rst | 8 consumer devices can be instantiated from device-tree or over configfs.
10 A virtual consumer uses the driver-facing GPIO APIs and allows to cover it with
17 The gpio-consumer module registers a configfs subsystem called
22 values of exposed attributes. Once the consumer is instantiated, this hierarchy
27 This is the top directory of the gpio-consumer configfs tree.
29 **Group:** ``/config/gpio-consumer/example-name``
31 **Attribute:** ``/config/gpio-consumer/example-name/live``
33 **Attribute:** ``/config/gpio-consumer/example-name/dev_name``
35 This is a directory representing a GPIO consumer device.
51 **Group:** ``/config/gpio-consumer/example-name/con_id``
[all …]
|
| /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
65 The @ta_sock field references an open and connected socket. The consumer
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
79 The consumer can fill in the @ta_timeout_ms field to force the servicing
86 that are instantiated by the consumer before making the handshake
87 request. The consumer can provide a private keyring that is linked into
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
[all …]
|
| /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.
|
| /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
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/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
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 …]
|
| 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
|
| /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::
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 …]
|
| 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"),
|
| /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.
|
| /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()
|
| /linux/drivers/net/ethernet/qlogic/qlcnic/ |
| H A 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()
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/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
|
| /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()
|
| H A D | kunit_clk_assigned_rates_zero_consumer.dtso | 11 kunit-clock-consumer {
12 compatible = "test,clk-consumer";
|
| H A D | kunit_clk_assigned_rates_without_consumer.dtso | 13 kunit-clock-consumer {
14 compatible = "test,clk-consumer";
|
| H A D | kunit_clk_assigned_rates_null_consumer.dtso | 13 kunit-clock-consumer {
14 compatible = "test,clk-consumer";
|
| H A D | kunit_clk_assigned_rates_one_consumer.dtso | 13 kunit-clock-consumer {
14 compatible = "test,clk-consumer";
|
| H A D | kunit_clk_fixed_rate_test.dtso | 15 kunit-clock-consumer {
16 compatible = "test,single-clk-consumer";
|