Home
last modified time | relevance | path

Searched full:consumers (Results 1 – 25 of 195) sorted by relevance

12345678

/Linux-v5.10/Documentation/power/regulator/
Dconsumer.rst25 Consumers can be supplied by more than one regulator e.g. codec consumer with
60 This may not disable the supply if it's shared with other consumers. The
69 consumers will be powered off.
80 Consumers can control their supply voltage by calling::
111 Consumers can control their supply current limit by calling::
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.
[all …]
Doverview.rst41 Consumers can be classified into two types:-
67 - Domain 1: Switch-1, Consumers D & E.
68 - Domain 2: Switch-2, Consumers B & C.
147 allow consumers complete control over their supply voltage and current
Ddesign.rst32 different consumers.
37 very easy to handle and so that consumers will work with shared
/Linux-v5.10/virt/lib/
Dirqbypass.c13 * interrupt producers and consumers to find each other to enable this sort of
26 static LIST_HEAD(consumers);
86 * with any matching token found on the IRQ consumers list.
111 list_for_each_entry(consumer, &consumers, node) { in irq_bypass_register_producer()
158 list_for_each_entry(consumer, &consumers, node) { in irq_bypass_unregister_producer()
180 * Add the provided IRQ consumer to the list of consumers and connect
200 list_for_each_entry(tmp, &consumers, node) { in irq_bypass_register_consumer()
216 list_add(&consumer->node, &consumers); in irq_bypass_register_consumer()
232 * Remove a previously registered IRQ consumer from the list of consumers
250 list_for_each_entry(tmp, &consumers, node) { in irq_bypass_unregister_consumer()
/Linux-v5.10/Documentation/driver-api/driver-model/
Ddriver.rst191 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-v5.10/include/linux/regulator/
Dconsumer.h166 * a convenience to consumers which require multiple supplies. This
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
[all …]
Dmachine.h93 * @min_uV: Smallest voltage consumers may set.
94 * @max_uV: Largest voltage consumers may set.
98 * @min_uA: Smallest current consumers may set.
99 * @max_uA: Largest current consumers may set.
105 * @valid_modes_mask: Mask of modes which may be configured by consumers.
106 * @valid_ops_mask: Operations which may be performed by consumers.
222 * Initialisation constraints, our supply and consumers supplies.
/Linux-v5.10/Documentation/devicetree/bindings/interconnect/
Dinterconnect.txt5 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
55 order as the interconnects property. Consumers drivers will use
/Linux-v5.10/drivers/regulator/
Ddevres.c119 struct regulator_bulk_data *consumers; member
127 regulator_bulk_free(devres->num_consumers, devres->consumers); in devm_regulator_bulk_release()
131 * devm_regulator_bulk_get - managed get multiple regulator consumers
134 * @num_consumers: number of consumers to register
135 * @consumers: configuration of consumers; clients are stored here.
140 * consumers in one operation with management, the regulators will
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()
Dcore.c461 * regulator consumers
473 * Assume consumers that didn't say anything are OK in regulator_check_consumers()
2040 * or IS_ERR() condition containing errno. Other consumers will be
2045 * This is intended for use by consumers which cannot tolerate shared
2069 * This is intended for use by consumers for devices which can have
2552 * regulator enabled. Explained in example with two consumers of the same
3651 * demanded by consumers. in regulator_get_optimal_voltage()
3655 * If consumers don't provide any demands, set voltage in regulator_get_optimal_voltage()
4448 * Allow the regulator to go into bypass mode if all other consumers
4533 /* notify regulator consumers and downstream regulator consumers.
[all …]
/Linux-v5.10/scripts/
Ddev-needs.sh104 CONSUMERS+=($PARENT)
138 CONSUMERS+=($SUPPLIER)
264 CONSUMERS=($@)
270 while [ $i -lt ${#CONSUMERS[@]} ]
272 CONSUMER=$(realpath ${CONSUMERS[$i]})
289 # Add suppliers to CONSUMERS list and output the consumer details.
/Linux-v5.10/Documentation/driver-api/
Dregulator.rst68 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.
Dinterconnect.rst72 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
Ddevice_link.rst177 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,
Dnvmem.rst97 NVMEM Consumers
100 NVMEM consumers are the entities which make use of the NVMEM provider to
127 To facilitate such consumers NVMEM framework provides below apis::
144 Before the consumers can read/write NVMEM directly, it should get hold
/Linux-v5.10/Documentation/infiniband/
Dcore_locking.rst29 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-v5.10/tools/testing/selftests/bpf/
Dbench.c123 { "consumers", 'c', "NUM", 0, "Number of consumer threads"},
194 fprintf(stderr, "Invalid format of CPU set for consumers."); in parse_arg()
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()
/Linux-v5.10/Documentation/crypto/
Dintro.rst25 - 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-v5.10/Documentation/devicetree/bindings/reset/
Dreset.txt20 A word on where to place reset signal consumers in device tree: It is possible
45 = Reset consumers =
56 the resets property. Consumers drivers will use reset-names to
/Linux-v5.10/Documentation/devicetree/bindings/mux/
Dmux-controller.txt10 A mux controller provides a number of states to its consumers, and the state
15 Consumers
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
/Linux-v5.10/Documentation/devicetree/bindings/arm/
Dsecure.txt4 "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-v5.10/Documentation/devicetree/bindings/regulator/
Dregulator.yaml19 description: smallest voltage consumers may set
22 description: largest voltage consumers may set
28 description: smallest current consumers may set
31 description: largest current consumers may set
/Linux-v5.10/Documentation/devicetree/bindings/clock/
Dnvidia,tegra210-car.txt15 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
Dnvidia,tegra114-car.txt15 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
Dnvidia,tegra20-car.txt15 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

12345678