| /Linux-v6.1/drivers/regulator/ |
| D | devres.c | 178 struct regulator_bulk_data *consumers; member
186 regulator_bulk_free(devres->num_consumers, devres->consumers); in devm_regulator_bulk_release()
190 * devm_regulator_bulk_get - managed get multiple regulator consumers
193 * @num_consumers: number of consumers to register
194 * @consumers: configuration of consumers; clients are stored here.
199 * consumers in one operation with management, the regulators will
205 struct regulator_bulk_data *consumers) in devm_regulator_bulk_get() argument
215 ret = regulator_bulk_get(dev, num_consumers, consumers); in devm_regulator_bulk_get()
217 devres->consumers = consumers; in devm_regulator_bulk_get()
232 * @num_consumers: number of consumers to register
[all …]
|
| D | core.c | 452 * regulator consumers
464 * Assume consumers that didn't say anything are OK in regulator_check_consumers()
2239 * or IS_ERR() condition containing errno. Other consumers will be
2244 * This is intended for use by consumers which cannot tolerate shared
2268 * This is intended for use by consumers for devices which can have
2738 * regulator enabled. Explained in example with two consumers of the same
3839 * demanded by consumers. in regulator_get_optimal_voltage()
3843 * If consumers don't provide any demands, set voltage in regulator_get_optimal_voltage()
4686 * Allow the regulator to go into bypass mode if all other consumers
4771 /* notify regulator consumers and downstream regulator consumers.
[all …]
|
| /Linux-v6.1/Documentation/power/regulator/ |
| D | consumer.rst | 25 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 …]
|
| D | overview.rst | 41 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
|
| D | design.rst | 32 different consumers.
37 very easy to handle and so that consumers will work with shared
|
| /Linux-v6.1/virt/lib/ |
| D | irqbypass.c | 13 * interrupt producers and consumers to find each other to enable this sort of
26 static LIST_HEAD(consumers);
82 * with any matching token found on the IRQ consumers list.
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()
176 * Add the provided IRQ consumer to the list of consumers and connect
196 list_for_each_entry(tmp, &consumers, node) { in irq_bypass_register_consumer()
212 list_add(&consumer->node, &consumers); in irq_bypass_register_consumer()
228 * Remove a previously registered IRQ consumer from the list of consumers
246 list_for_each_entry(tmp, &consumers, node) { in irq_bypass_unregister_consumer()
|
| /Linux-v6.1/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 …]
|
| /Linux-v6.1/include/linux/regulator/ |
| D | consumer.h | 124 * is such that the HW is likely to still be working but consumers should
183 * a convenience to consumers which require multiple supplies. This
246 struct regulator_bulk_data *consumers);
248 struct regulator_bulk_data *consumers);
249 void devm_regulator_bulk_put(struct regulator_bulk_data *consumers);
255 struct regulator_bulk_data *consumers);
259 struct regulator_bulk_data *consumers);
261 struct regulator_bulk_data *consumers);
263 struct regulator_bulk_data *consumers);
318 void regulator_bulk_set_supply_names(struct regulator_bulk_data *consumers,
[all …]
|
| D | machine.h | 101 * @min_uV: Smallest voltage consumers may set.
102 * @max_uV: Largest voltage consumers may set.
106 * @min_uA: Smallest current consumers may set.
107 * @max_uA: Largest current consumers may set.
118 * @valid_modes_mask: Mask of modes which may be configured by consumers.
119 * @valid_ops_mask: Operations which may be performed by consumers.
248 * Initialisation constraints, our supply and consumers supplies.
|
| /Linux-v6.1/Documentation/driver-api/hte/ |
| D | tegra194-hte.rst | 24 and userspace consumers. The kernel space consumers can directly talk to HTE
25 subsystem while userspace consumers timestamp requests go through GPIOLIB CDEV
30 For userspace consumers, GPIO_V2_LINE_FLAG_EVENT_CLOCK_HTE flag must be
41 one-to-one mapping with IRQ GTE provider, consumers can simply specify the IRQ
|
| 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-v6.1/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
55 order as the interconnects property. Consumers drivers will use
|
| /Linux-v6.1/Documentation/driver-api/ |
| 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
|
| 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.
|
| 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 | 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,
|
| D | nvmem.rst | 93 NVMEM Consumers
96 NVMEM consumers are the entities which make use of the NVMEM provider to
123 To facilitate such consumers NVMEM framework provides below apis::
140 Before the consumers can read/write NVMEM directly, it should get hold
|
| /Linux-v6.1/drivers/soc/microchip/ |
| D | mpfs-sys-controller.c | 26 struct kref consumers; member
70 consumers); in mpfs_sys_controller_delete()
80 kref_put(&sys_controller->consumers, mpfs_sys_controller_delete); in mpfs_sys_controller_put()
117 kref_init(&sys_controller->consumers); in mpfs_sys_controller_probe()
165 if (!kref_get_unless_zero(&sys_controller->consumers)) in mpfs_sys_controller_get()
|
| /Linux-v6.1/scripts/ |
| D | dev-needs.sh | 104 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-v6.1/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
|
| /Linux-v6.1/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
|
| /Linux-v6.1/Documentation/devicetree/bindings/reset/ |
| D | reset.txt | 20 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-v6.1/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
|
| /Linux-v6.1/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()
279 kref_init(&fw->consumers); in rpi_firmware_probe()
334 if (!kref_get_unless_zero(&fw->consumers)) in rpi_firmware_get()
|
| /Linux-v6.1/include/linux/ |
| D | hte.h | 90 * @line_id: The logical ID understood by the consumers and providers.
107 * This structure is a communication token between consumers to subsystem
157 * @xlate_plat: Same as above but for the consumers with no DT node.
187 /* HTE APIs for the consumers */
|
