| /linux/virt/lib/ |
| H A D | irqbypass.c | 26 static DEFINE_XARRAY(consumers);
111 consumer = xa_load(&consumers, index); in irq_bypass_register_producer()
173 ret = xa_insert(&consumers, index, consumer, GFP_KERNEL); in irq_bypass_register_consumer()
181 WARN_ON_ONCE(xa_erase(&consumers, index) != consumer); in irq_bypass_register_consumer()
211 WARN_ON_ONCE(xa_erase(&consumers, index) != consumer); in irq_bypass_unregister_consumer()
|
| /linux/Documentation/driver-api/hte/ |
| H A D | tegra-hte.rst | 21 below. The GPIO GTE code supports both kernel and userspace consumers. The
22 kernel space consumers can directly talk to HTE subsystem while userspace
23 consumers timestamp requests go through GPIOLIB CDEV framework to HTE
30 For userspace consumers, GPIO_V2_LINE_FLAG_EVENT_CLOCK_HTE flag must be
40 one-to-one mapping with IRQ GTE provider, consumers can simply specify the IRQ
|
| H A D | hte.rst | 21 engine (HTE) framework. Both consumers and providers must include
30 The HTE framework APIs for the consumers
43 consumers and the providers. It expresses timestamp data in nanoseconds in
|
| /linux/drivers/soc/microchip/ |
| H A D | mpfs-sys-controller.c | 36 struct kref consumers; member
99 container_of(kref, struct mpfs_sys_controller, consumers); in mpfs_sys_controller_delete()
109 kref_put(&sys_controller->consumers, mpfs_sys_controller_delete); in mpfs_sys_controller_put()
155 kref_init(&sys_controller->consumers); in mpfs_sys_controller_probe()
249 if (!kref_get_unless_zero(&sys_controller->consumers)) in mpfs_sys_controller_get()
|
| /linux/Documentation/driver-api/ |
| H A D | wbrf.rst | 13 frequencies in use and consumers can use this information to avoid using
32 of their particular frequencies so that other consumers can make relative
62 param to get other consumers properly notified.
64 `acpi_amd_wbrf_add_remove` with 'remove' param to get other consumers notified.
66 The expected flow for the consumers:
|
| H A D | regulator.rst | 68 When requesting regulators consumers use symbolic names for their
83 Note that since multiple consumers may be using a regulator and machine
126 consumers on a given system and what the valid operating parameters are
144 consumers are rated for.
151 static consumers.
|
| H A D | device_link.rst | 177 device links from the hotplug ports (consumers) to the NHI device
231 entire sub-graph below it (all children and consumers of the consumer)
237 on the consumer or any children or consumers of the consumer.
274 * When a supplier device is bound to a driver, links to its consumers
301 * Before a supplier's driver is removed, links to consumers that are not
305 This prevents the consumers from binding.
308 Consumers that are bound are freed from their driver; consumers that are
312 Once all links to consumers are in ``DL_STATE_SUPPLIER_UNBIND`` state,
|
| H A D | pwm.rst | 21 consumers to providers, as given in the following example::
78 consumers to get the actually implemented settings.
88 All consumers should really be reconfiguring the PWM upon resume as
170 consumers should implement it as described in the "Using PWMs" section.
|
| /linux/Documentation/driver-api/driver-model/ |
| H A D | driver.rst | 191 devices of the device have successfully probed. The list of consumers of the
197 attempt at calling sync_state(), if all the consumers of the device at that
199 away. If there are no consumers of the device during the first attempt, that
200 too is considered as "all consumers of the device have probed" and sync_state()
204 still consumers that haven't probed successfully, the sync_state() call is
205 postponed and reattempted in the future only when one or more consumers of the
207 there are one or more consumers of the device that haven't probed yet, then
214 consumers of the device have probed. Once all the consumers of the device have
216 match the aggregated software state requested by all the consumers. Hence the
221 resources like IOMMUs. For example, IOMMUs with multiple consumers (devices
[all …]
|
| /linux/Documentation/devicetree/bindings/interconnect/ |
| H A D | interconnect.txt | 5 providers/consumers properties.
16 consumers, such as in the case where two network-on-chip fabrics interface
37 = interconnect consumers =
39 The interconnect consumers are device nodes which dynamically express their
|
| /linux/drivers/firmware/ |
| H A D | raspberrypi.c | 34 struct kref consumers; member
257 consumers); in rpi_firmware_delete()
265 kref_put(&fw->consumers, rpi_firmware_delete); in rpi_firmware_put()
301 kref_init(&fw->consumers); in rpi_firmware_probe()
366 if (!kref_get_unless_zero(&fw->consumers)) in rpi_firmware_get()
|
| /linux/Documentation/infiniband/ |
| H A D | core_locking.rst | 29 consumers:
60 consumers are not required to perform any serialization. However,
96 Upper level protocol consumers may not sleep in a callback.
102 consumers when it calls ib_register_device(), all initialization
|
| /linux/Documentation/power/regulator/ |
| H A D | design.rst | 32 different consumers.
37 very easy to handle and so that consumers will work with shared
|
| H A D | machine.rst | 14 The drivers for consumers A & B must be mapped to the correct regulator in
38 for each regulator power domain. This structure also maps the consumers
|
| /linux/tools/testing/selftests/bpf/ |
| H A D | bench.c | 264 { "consumers", 'c', "NUM", 0, "Number of consumer threads"},
369 fprintf(stderr, "Invalid format of CPU set for consumers."); in parse_arg()
493 pthread_t *consumers;
686 state.consumers = calloc(env.consumer_cnt, sizeof(*state.consumers)); in setup_benchmark()
689 if (!state.producers || !state.consumers || !state.results) in setup_benchmark()
699 fprintf(stderr, "benchmark doesn't support consumers!\n");
702 err = pthread_create(&state.consumers[i], NULL, in collect_measurements()
710 set_thread_affinity(state.consumers[i], in collect_measurements()
485 pthread_t *consumers; global() member
|
| /linux/Documentation/crypto/ |
| H A D | intro.rst | 25 - consumers requesting cryptographic services
28 called by consumers using the kernel crypto API
30 This specification is intended for consumers of the kernel crypto API as
|
| /linux/Documentation/devicetree/bindings/arm/ |
| H A D | secure.txt | 4 "Normal" and "Secure". Most devicetree consumers (including the Linux
6 world or the Secure world. However some devicetree consumers are
30 world consumers (like kernels that run entirely in Secure) to simply
|
| /linux/include/linux/platform_data/ |
| H A D | tps68470.h | 37 struct tps68470_clk_consumer consumers[]; member
|
| /linux/Documentation/dev-tools/kunit/api/ |
| H A D | clk.rst | 7 The KUnit clk API is used to test clk providers and clk consumers.
|
| /linux/Documentation/devicetree/bindings/reset/ |
| H A D | ti-syscon-reset.txt | 32 consumers, defined as:
60 common reset controller usage by consumers.
|
| H A D | reset.txt | 20 A word on where to place reset signal consumers in device tree: It is possible
45 = Reset consumers =
|
| /linux/drivers/base/ |
| H A D | core.c | 73 list_for_each_entry(link, &sup->consumers, s_hook) in __fwnode_link_add()
89 list_add(&link->s_hook, &sup->consumers); in __fwnode_link_add()
161 list_for_each_entry_safe(link, tmp, &fwnode->consumers, s_hook) in fwnode_links_purge_consumers()
205 list_for_each_entry_safe(link, tmp, &from->consumers, s_hook) { in __fwnode_links_move_consumers()
320 list_for_each_entry(link, &dev->links.consumers, s_node) { in device_is_dependent()
393 list_for_each_entry(link, &dev->links.consumers, s_node) { in device_reorder_to_tail()
790 list_for_each_entry(link, &supplier->links.consumers, s_node) { in device_link_add()
894 list_add_tail_rcu(&link->s_node, &supplier->links.consumers); in device_link_add()
984 list_for_each_entry(link, &supplier->links.consumers, s_node) { in device_link_remove()
1129 list_for_each_entry(link, &dev->links.consumers, s_node) { in __device_links_queue_sync_state()
[all …]
|
| /linux/drivers/iio/ |
| H A D | Kconfig | 46 int "Maximum number of consumers per trigger"
50 This value controls the maximum number of consumers that a
|
| /linux/Documentation/devicetree/bindings/clock/ |
| H A D | img,boston-clock.txt | 13 Values available for clock consumers can be found in the header file:
|
| /linux/Documentation/devicetree/bindings/arm/ux500/ |
| H A D | power_domain.txt | 21 ==PM domain consumers==
|