Searched full:consumers (Results 1 – 25 of 78) sorted by relevance
1234
| /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 | design.rst | 32 different consumers.
37 very easy to handle and so that consumers will work with shared
|
| 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
|
| /Documentation/driver-api/ |
| 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:
|
| 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 | 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 | 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.
|
| 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,
|
| /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
|
| /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
|
| /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 …]
|
| /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
|
| /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
|
| /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
|
| /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
|
| /Documentation/devicetree/bindings/hwlock/ |
| 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
|
| /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
|
| /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
|
| /Documentation/dev-tools/kunit/api/ |
| D | clk.rst | 7 The KUnit clk API is used to test clk providers and clk consumers.
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | mediatek,gce-props.yaml | 16 mailbox framework. It is used to receive messages from mailbox consumers
25 provider and consumers.
|
| /Documentation/devicetree/bindings/mux/ |
| D | mux-consumer.yaml | 13 Mux controller consumers should specify a list of mux controllers that they
34 the consumers want to control the mux controller. If the consumer needs
|
| /Documentation/networking/ |
| D | xdp-rx-metadata.rst | 9 and how it can pass that metadata on to other consumers.
33 consumers, an XDP program can store it into the metadata area carried
53 area in whichever format it chooses. Later consumers of the metadata
|
1234