| /kernel/linux/linux-5.10/include/linux/regulator/ |
| D | consumer.h | 231 struct regulator_bulk_data *consumers);
233 struct regulator_bulk_data *consumers);
235 struct regulator_bulk_data *consumers);
237 struct regulator_bulk_data *consumers);
239 struct regulator_bulk_data *consumers);
241 struct regulator_bulk_data *consumers);
296 void regulator_bulk_set_supply_names(struct regulator_bulk_data *consumers,
438 struct regulator_bulk_data *consumers) in regulator_bulk_get() argument
444 struct regulator_bulk_data *consumers) in devm_regulator_bulk_get() argument
450 struct regulator_bulk_data *consumers) in regulator_bulk_enable() argument
[all …]
|
| /kernel/linux/linux-5.10/virt/lib/ |
| 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()
|
| /kernel/linux/linux-5.10/Documentation/power/regulator/ |
| 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.
179 Regulators can notify consumers of external events. Events could be received by
[all …]
|
| D | design.rst | 32 different consumers.
37 very easy to handle and so that consumers will work with shared
|
| 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
|
| /kernel/linux/linux-5.10/drivers/regulator/ |
| 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()
|
| D | core.c | 4592 struct regulator_bulk_data *consumers) in regulator_bulk_get() argument
4598 consumers[i].consumer = NULL; in regulator_bulk_get()
4601 consumers[i].consumer = regulator_get(dev, in regulator_bulk_get()
4602 consumers[i].supply); in regulator_bulk_get()
4603 if (IS_ERR(consumers[i].consumer)) { in regulator_bulk_get()
4604 ret = PTR_ERR(consumers[i].consumer); in regulator_bulk_get()
4605 consumers[i].consumer = NULL; in regulator_bulk_get()
4615 consumers[i].supply, ERR_PTR(ret)); in regulator_bulk_get()
4618 consumers[i].supply); in regulator_bulk_get()
4621 regulator_put(consumers[i].consumer); in regulator_bulk_get()
[all …]
|
| /kernel/linux/linux-5.10/drivers/firmware/ |
| 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()
272 kref_init(&fw->consumers); in rpi_firmware_probe()
327 if (!kref_get_unless_zero(&fw->consumers)) in rpi_firmware_get()
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/interconnect/ |
| 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
|
| /kernel/linux/linux-5.10/Documentation/driver-api/driver-model/ |
| 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 …]
|
| /kernel/linux/linux-5.10/tools/testing/selftests/bpf/ |
| D | bench.c | 300 pthread_t *consumers; member
371 state.consumers = calloc(env.consumer_cnt, sizeof(*state.consumers)); in setup_benchmark()
374 if (!state.producers || !state.consumers || !state.results) in setup_benchmark()
383 err = pthread_create(&state.consumers[i], NULL, in setup_benchmark()
391 set_thread_affinity(state.consumers[i], in setup_benchmark()
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| 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
|
| 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.
|
| /kernel/linux/linux-5.10/Documentation/infiniband/ |
| 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
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/clock/ |
| D | nvidia,tegra210-car.txt | 15 In clock consumers, this cell represents the clock ID exposed by the
19 In clock consumers, this cell represents the bit number in the CAR's
|
| D | nvidia,tegra30-car.txt | 15 In clock consumers, this cell represents the clock ID exposed by the
19 In clock consumers, this cell represents the bit number in the CAR's
|
| D | nvidia,tegra114-car.txt | 15 In clock consumers, this cell represents the clock ID exposed by the
19 In clock consumers, this cell represents the bit number in the CAR's
|
| D | nvidia,tegra20-car.txt | 15 In clock consumers, this cell represents the clock ID exposed by the
19 In clock consumers, this cell represents the bit number in the CAR's
|
| D | nvidia,tegra124-car.txt | 15 In clock consumers, this cell represents the clock ID exposed by the
21 In clock consumers, this cell represents the bit number in the CAR's
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/regulator/ |
| D | vctrl.txt | 7 - regulator-min-microvolt : smallest voltage consumers may set
8 - regulator-max-microvolt : largest voltage consumers may set
|
| /kernel/linux/linux-5.10/Documentation/crypto/ |
| 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
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/phy/ |
| 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.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/ |
| 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
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mux/ |
| D | mux-controller.txt | 10 A mux controller provides a number of states to its consumers, and the state
18 Mux controller consumers should specify a list of mux controllers that they
68 * Two consumers (one for an ADC line and one for an i2c bus) of
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/hwlock/ |
| D | sirf,hwspinlock.txt | 13 Please look at the generic hwlock binding for usage information for consumers,
|