| /linux/include/linux/regulator/ |
| A D | consumer.h | 240 struct regulator_bulk_data *consumers);
242 struct regulator_bulk_data *consumers);
246 struct regulator_bulk_data *consumers);
248 struct regulator_bulk_data *consumers);
250 struct regulator_bulk_data *consumers);
443 struct regulator_bulk_data *consumers) in regulator_bulk_get() argument
449 struct regulator_bulk_data *consumers) in devm_regulator_bulk_get() argument
455 struct regulator_bulk_data *consumers) in regulator_bulk_enable() argument
461 struct regulator_bulk_data *consumers) in regulator_bulk_disable() argument
467 struct regulator_bulk_data *consumers) in regulator_bulk_force_disable() argument
[all …]
|
| /linux/virt/lib/ |
| A D | irqbypass.c | 26 static LIST_HEAD(consumers);
107 list_for_each_entry(consumer, &consumers, node) { in irq_bypass_register_producer()
154 list_for_each_entry(consumer, &consumers, node) { in irq_bypass_unregister_producer()
196 list_for_each_entry(tmp, &consumers, node) { in irq_bypass_register_consumer()
212 list_add(&consumer->node, &consumers); in irq_bypass_register_consumer()
246 list_for_each_entry(tmp, &consumers, node) { in irq_bypass_unregister_consumer()
|
| /linux/Documentation/power/regulator/ |
| A D | consumer.rst | 60 This may not disable the supply if it's shared with other consumers. The
69 consumers will be powered off.
137 Some consumers can further save system power by changing the operating mode of
138 their supply regulator to be more efficient when the consumers operating state
151 on all its consumers) and change operating mode (if necessary and permitted)
158 Most consumers will use indirect operating mode control since they have no
160 consumers.
172 Direct mode will only be used by consumers that *know* about the regulator and
173 are not sharing the regulator with other consumers.
180 consumers under regulator stress or failure conditions.
[all …]
|
| A D | design.rst | 32 different consumers.
37 very easy to handle and so that consumers will work with shared
|
| 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/drivers/regulator/ |
| A D | devres.c | 119 struct regulator_bulk_data *consumers; member
127 regulator_bulk_free(devres->num_consumers, devres->consumers); in devm_regulator_bulk_release()
146 struct regulator_bulk_data *consumers) in devm_regulator_bulk_get() argument
156 ret = regulator_bulk_get(dev, num_consumers, consumers); in devm_regulator_bulk_get()
158 devres->consumers = consumers; in devm_regulator_bulk_get()
|
| A D | core.c | 4739 consumers[i].consumer = NULL; in regulator_bulk_get()
4743 consumers[i].supply); in regulator_bulk_get()
4746 consumers[i].consumer = NULL; in regulator_bulk_get()
4759 consumers[i].supply); in regulator_bulk_get()
4803 if (consumers[i].ret != 0) { in regulator_bulk_enable()
4804 ret = consumers[i].ret; in regulator_bulk_enable()
4813 if (consumers[i].ret < 0) in regulator_bulk_enable()
4884 consumers[i].ret = in regulator_bulk_force_disable()
4888 if (consumers[i].ret && !ret) in regulator_bulk_force_disable()
4889 ret = consumers[i].ret; in regulator_bulk_force_disable()
[all …]
|
| /linux/Documentation/driver-api/driver-model/ |
| 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
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
223 fixed at (or additive to) the boot configuration until all its consumers have
[all …]
|
| /linux/drivers/firmware/ |
| A D | raspberrypi.c | 32 struct kref consumers; member
234 consumers); in rpi_firmware_delete()
242 kref_put(&fw->consumers, rpi_firmware_delete); in rpi_firmware_put()
279 kref_init(&fw->consumers); in rpi_firmware_probe()
334 if (!kref_get_unless_zero(&fw->consumers)) in rpi_firmware_get()
|
| /linux/Documentation/devicetree/bindings/interconnect/ |
| 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/Documentation/driver-api/ |
| A D | interconnect.rst | 72 Interconnect consumers are the entities which make use of the data paths exposed
73 by the providers. The consumers send requests to providers requesting various
74 throughput, latency and priority. Usually the consumers are device drivers, that
87 Interconnect consumers
90 Interconnect consumers are the clients which use the interconnect APIs to
|
| A D | reset.rst | 19 consumers.
63 When requesting reset controls, consumers can use symbolic names for their
98 Note that since multiple consumers may be using a shared reset control, there
111 In general, these resets can not be shared between multiple consumers, since
118 All further calls to this function have no effect until all consumers have
181 Reset consumers can control a reset line using an opaque reset control handle,
184 Given the reset control, consumers can call reset_control_assert() and
|
| 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.
|
| 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,
|
| A D | pwm.rst | 21 consumers to providers, as given in the following example::
67 consumers to get the actually implemented settings.
77 All consumers should really be reconfiguring the PWM upon resume as
158 consumers should implement it as described in the "Using PWMs" section.
|
| /linux/tools/testing/selftests/bpf/ |
| A D | bench.c | 341 pthread_t *consumers; member
422 state.consumers = calloc(env.consumer_cnt, sizeof(*state.consumers)); in setup_benchmark()
425 if (!state.producers || !state.consumers || !state.results) in setup_benchmark()
434 err = pthread_create(&state.consumers[i], NULL, in setup_benchmark()
442 set_thread_affinity(state.consumers[i], in setup_benchmark()
|
| /linux/Documentation/infiniband/ |
| 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/crypto/ |
| 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/regulator/ |
| A D | vctrl.txt | 7 - regulator-min-microvolt : smallest voltage consumers may set
8 - regulator-max-microvolt : largest voltage consumers may set
|
| /linux/include/linux/ |
| A D | fwnode.h | 41 struct list_head consumers; member
176 INIT_LIST_HEAD(&fwnode->consumers); in fwnode_init()
|
| /linux/Documentation/devicetree/bindings/phy/ |
| A D | qcom,usb-8x16-phy.txt | 16 Definition: See clock-bindings.txt section "consumers". List of
43 Definition: See reset.txt section "consumers". PHY reset specifier.
|
| /linux/Documentation/devicetree/bindings/arm/ |
| 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/drivers/base/ |
| A D | core.c | 81 list_for_each_entry(link, &sup->consumers, s_hook) in fwnode_link_add()
96 list_add(&link->s_hook, &sup->consumers); in fwnode_link_add()
297 list_for_each_entry(link, &dev->links.consumers, s_node) { in device_is_dependent()
371 list_for_each_entry(link, &dev->links.consumers, s_node) { in device_reorder_to_tail()
1058 list_for_each_entry(link, &dev->links.consumers, s_node) { in __device_links_queue_sync_state()
1252 list_for_each_entry(link, &dev->links.consumers, s_node) { in device_links_driver_bound()
1372 list_for_each_entry(link, &dev->links.consumers, s_node) { in device_links_no_driver()
1455 list_for_each_entry(link, &dev->links.consumers, s_node) { in device_links_busy()
1495 list_for_each_entry(link, &dev->links.consumers, s_node) { in device_links_unbind_consumers()
1666 list_for_each_entry(link, &dev->links.consumers, s_node) in fw_devlink_unblock_consumers()
[all …]
|
| /linux/drivers/iio/ |
| A D | Kconfig | 42 int "Maximum number of consumers per trigger"
46 This value controls the maximum number of consumers that a
|
| /linux/Documentation/devicetree/bindings/reset/ |
| A D | ti-syscon-reset.txt | 32 consumers, defined as:
60 common reset controller usage by consumers.
|