| /linux/Documentation/power/regulator/ |
| H A 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 …]
|
| H A 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
|
| H A D | design.rst | 32 different consumers.
37 very easy to handle and so that consumers will work with shared
|
| /linux/Documentation/driver-api/driver-model/ |
| H 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
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/Documentation/driver-api/ |
| H A D | wbrf.rst | 13 frequencies in use and consumers can use this information to avoid using
20 * Consumers with this _DSM will be able to register for notifications of
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:
|
| H 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
|
| H 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.
|
| H 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,
|
| H 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
|
| H A D | pwm.rst | 21 consumers to providers, as given in the following example::
38 Consumers use the pwm_get() function and pass to it the consumer device or a
78 consumers to get the actually implemented settings.
88 All consumers should really be reconfiguring the PWM upon resume as
170 consumers should implement it as described in the "Using PWMs" section.
|
| H A D | nvmem.rst | 87 NVMEM Consumers
90 NVMEM consumers are the entities which make use of the NVMEM provider to
117 To facilitate such consumers NVMEM framework provides below apis::
134 Before the consumers can read/write NVMEM directly, it should get hold
|
| /linux/Documentation/driver-api/hte/ |
| H A 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
|
| H A 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/Documentation/devicetree/bindings/interconnect/ |
| H 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
55 order as the interconnects property. Consumers drivers will use
|
| /linux/virt/lib/ |
| H A D | irqbypass.c | 13 * interrupt producers and consumers to find each other to enable this sort of
26 static DEFINE_XARRAY(consumers);
111 consumer = xa_load(&consumers, index); in irq_bypass_register_producer()
155 * Add the provided IRQ consumer to the set of consumers and connect with the
173 ret = xa_insert(&consumers, index, consumer, GFP_KERNEL); in irq_bypass_register_consumer()
181 WARN_ON_ONCE(xa_erase(&consumers, index) != consumer); in irq_bypass_register_consumer()
211 WARN_ON_ONCE(xa_erase(&consumers, index) != consumer); in irq_bypass_unregister_consumer()
|
| /linux/include/linux/ |
| H A D | irqbypass.h | 21 * consumers (ex. virtualization hardware that allows IRQ bypass or offload)
22 * via a shared eventfd_ctx. Producers and consumers register independently.
36 * @eventfd: eventfd context used to match producers and consumers
62 * @eventfd: eventfd context used to match producers and consumers
|
| H A 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 */
|
| /linux/scripts/ |
| H A 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/Documentation/infiniband/ |
| H 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/drivers/regulator/ |
| H A D | core.c | 456 * regulator consumers
468 * Assume consumers that didn't say anything are OK in regulator_check_consumers()
2365 * Other consumers will be unable to obtain this regulator while this
2369 * This is intended for use by consumers which cannot tolerate shared
2393 * This is intended for use by consumers for devices which can have
2829 * regulator enabled. Explained in example with two consumers of the same
4020 * demanded by consumers. in regulator_get_optimal_voltage()
4024 * If consumers don't provide any demands, set voltage in regulator_get_optimal_voltage()
4965 * Allow the regulator to go into bypass mode if all other consumers
5057 /* notify regulator consumers and downstream regulator consumers.
[all …]
|
| /linux/Documentation/crypto/ |
| H 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/reset/ |
| H A 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/Documentation/devicetree/bindings/arm/ |
| H 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/tools/testing/selftests/bpf/ |
| H A D | bench.c | 264 { "consumers", 'c', "NUM", 0, "Number of consumer threads"},
363 fprintf(stderr, "Invalid format of CPU set for consumers."); in parse_arg()
487 pthread_t *consumers;
658 state.consumers = calloc(env.consumer_cnt, sizeof(*state.consumers)); in setup_benchmark()
661 if (!state.producers || !state.consumers || !state.results) in setup_benchmark()
671 fprintf(stderr, "benchmark doesn't support consumers!\n"); in setup_benchmark()
674 err = pthread_create(&state.consumers[i], NULL, in setup_benchmark()
682 set_thread_affinity(state.consumers[i], in setup_benchmark()
485 pthread_t *consumers; global() member
|
| /linux/Documentation/devicetree/bindings/hwlock/ |
| H A D | hwlock.txt | 21 Consumers that require specific hwlock(s) should specify them using the
33 as the hwlocks, with one name per hwlock. Consumers can
|