| /linux-6.12.1/drivers/regulator/ |
| D | devres.c | 237 struct regulator_bulk_data *consumers; member
245 regulator_bulk_free(devres->num_consumers, devres->consumers); in devm_regulator_bulk_release()
249 struct regulator_bulk_data *consumers, in _devm_regulator_bulk_get() argument
260 ret = _regulator_bulk_get(dev, num_consumers, consumers, get_type); in _devm_regulator_bulk_get()
262 devres->consumers = consumers; in _devm_regulator_bulk_get()
288 struct regulator_bulk_data *consumers) in devm_regulator_bulk_get() argument
290 return _devm_regulator_bulk_get(dev, num_consumers, consumers, NORMAL_GET); in devm_regulator_bulk_get()
311 struct regulator_bulk_data *consumers) in devm_regulator_bulk_get_exclusive() argument
313 return _devm_regulator_bulk_get(dev, num_consumers, consumers, EXCLUSIVE_GET); in devm_regulator_bulk_get_exclusive()
357 return match->consumers == target; in devm_regulator_bulk_match()
[all …]
|
| D | core.c | 4936 struct regulator_bulk_data *consumers, enum regulator_get_type get_type) in _regulator_bulk_get() argument
4942 consumers[i].consumer = NULL; in _regulator_bulk_get()
4945 consumers[i].consumer = _regulator_get(dev, in _regulator_bulk_get()
4946 consumers[i].supply, get_type); in _regulator_bulk_get()
4947 if (IS_ERR(consumers[i].consumer)) { in _regulator_bulk_get()
4948 ret = dev_err_probe(dev, PTR_ERR(consumers[i].consumer), in _regulator_bulk_get()
4950 consumers[i].supply); in _regulator_bulk_get()
4951 consumers[i].consumer = NULL; in _regulator_bulk_get()
4955 if (consumers[i].init_load_uA > 0) { in _regulator_bulk_get()
4956 ret = regulator_set_load(consumers[i].consumer, in _regulator_bulk_get()
[all …]
|
| /linux-6.12.1/include/linux/regulator/ |
| D | consumer.h | 202 struct regulator_bulk_data *consumers);
204 struct regulator_bulk_data **consumers);
206 struct regulator_bulk_data *consumers);
207 void devm_regulator_bulk_put(struct regulator_bulk_data *consumers);
209 struct regulator_bulk_data *consumers);
215 struct regulator_bulk_data *consumers);
219 struct regulator_bulk_data *consumers);
221 struct regulator_bulk_data *consumers);
223 struct regulator_bulk_data *consumers);
279 void regulator_bulk_set_supply_names(struct regulator_bulk_data *consumers,
[all …]
|
| /linux-6.12.1/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()
|
| /linux-6.12.1/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
|
| /linux-6.12.1/drivers/soc/microchip/ |
| D | mpfs-sys-controller.c | 36 struct kref consumers; member
94 container_of(kref, struct mpfs_sys_controller, consumers); in mpfs_sys_controller_delete()
104 kref_put(&sys_controller->consumers, mpfs_sys_controller_delete); in mpfs_sys_controller_put()
163 kref_init(&sys_controller->consumers); in mpfs_sys_controller_probe()
210 if (!kref_get_unless_zero(&sys_controller->consumers)) in mpfs_sys_controller_get()
|
| /linux-6.12.1/Documentation/driver-api/hte/ |
| 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
|
| 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-6.12.1/Documentation/driver-api/ |
| 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:
|
| 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 | 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 | pwrseq.rst | 16 The intention is to allow consumers to obtain a power sequencing handle
63 consumers but it makes up for it in flexibility.
67 consumers may use as the final point in the sequence that they wish to reach.
76 mechanism for dynamic matching of consumers and providers. Every power sequence
|
| 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.
|
| /linux-6.12.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
|
| /linux-6.12.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-6.12.1/drivers/firmware/ |
| 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-6.12.1/drivers/platform/x86/intel/int3472/ |
| D | tps68470.c | 120 *clk_pdata = devm_kzalloc(dev, struct_size(*clk_pdata, consumers, n_consumers), in skl_int3472_fill_clk_pdata()
136 (*clk_pdata)->consumers[i].consumer_dev_name = sensor_name; in skl_int3472_fill_clk_pdata()
192 cells[0].pdata_size = struct_size(clk_pdata, consumers, n_consumers); in skl_int3472_tps68470_probe()
|
| /linux-6.12.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-6.12.1/tools/testing/selftests/bpf/ |
| D | bench.c | 485 pthread_t *consumers; member
642 state.consumers = calloc(env.consumer_cnt, sizeof(*state.consumers)); in setup_benchmark()
645 if (!state.producers || !state.consumers || !state.results) in setup_benchmark()
658 err = pthread_create(&state.consumers[i], NULL, in setup_benchmark()
666 set_thread_affinity(state.consumers[i], in setup_benchmark()
|
| /linux-6.12.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-6.12.1/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
|
| /linux-6.12.1/Documentation/admin-guide/gpio/ |
| D | gpio-virtuser.rst | 14 Creating GPIO consumers
74 For virtual consumers created using configfs we use machine lookup tables so
92 Activating GPIO consumers
104 Virtual GPIO consumers can also be defined in device-tree. The compatible string
119 Controlling virtual GPIO consumers
|
| /linux-6.12.1/include/linux/ |
| D | fwnode.h | 54 struct list_head consumers; member
203 INIT_LIST_HEAD(&fwnode->consumers); in fwnode_init()
|
| /linux-6.12.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
|