/Linux-v4.19/include/linux/regulator/ |
D | consumer.h | 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); 243 struct regulator_bulk_data *consumers); 424 struct regulator_bulk_data *consumers) in regulator_bulk_get() argument 430 struct regulator_bulk_data *consumers) in devm_regulator_bulk_get() argument 436 struct regulator_bulk_data *consumers) in regulator_bulk_enable() argument 442 struct regulator_bulk_data *consumers) in regulator_bulk_disable() argument [all …]
|
/Linux-v4.19/virt/lib/ |
D | irqbypass.c | 29 static LIST_HEAD(consumers); 110 list_for_each_entry(consumer, &consumers, node) { in irq_bypass_register_producer() 156 list_for_each_entry(consumer, &consumers, node) { in irq_bypass_unregister_producer() 197 list_for_each_entry(tmp, &consumers, node) { in irq_bypass_register_consumer() 217 list_add(&consumer->node, &consumers); in irq_bypass_register_consumer() 247 list_for_each_entry(tmp, &consumers, node) { in irq_bypass_unregister_consumer()
|
/Linux-v4.19/Documentation/power/regulator/ |
D | consumer.txt | 56 NOTE: This may not disable the supply if it's shared with other consumers. The 64 consumers will be powered off. 129 Some consumers can further save system power by changing the operating mode of 130 their supply regulator to be more efficient when the consumers operating state 143 on all its consumers) and change operating mode (if necessary and permitted) 150 Most consumers will use indirect operating mode control since they have no 152 consumers. 163 Direct mode will only be used by consumers that *know* about the regulator and 164 are not sharing the regulator with other consumers. 169 Regulators can notify consumers of external events. Events could be received by [all …]
|
D | design.txt | 29 different consumers. 32 very easy to handle and so that consumers will work with shared
|
D | machine.txt | 13 The drivers for consumers A & B must be mapped to the correct regulator in 37 for each regulator power domain. This structure also maps the consumers
|
/Linux-v4.19/drivers/regulator/ |
D | devres.c | 124 struct regulator_bulk_data *consumers; member 132 regulator_bulk_free(devres->num_consumers, devres->consumers); in devm_regulator_bulk_release() 151 struct regulator_bulk_data *consumers) in devm_regulator_bulk_get() argument 161 ret = regulator_bulk_get(dev, num_consumers, consumers); in devm_regulator_bulk_get() 163 devres->consumers = consumers; in devm_regulator_bulk_get()
|
D | core.c | 3762 struct regulator_bulk_data *consumers) in regulator_bulk_get() argument 3768 consumers[i].consumer = NULL; in regulator_bulk_get() 3771 consumers[i].consumer = regulator_get(dev, in regulator_bulk_get() 3772 consumers[i].supply); in regulator_bulk_get() 3773 if (IS_ERR(consumers[i].consumer)) { in regulator_bulk_get() 3774 ret = PTR_ERR(consumers[i].consumer); in regulator_bulk_get() 3776 consumers[i].supply, ret); in regulator_bulk_get() 3777 consumers[i].consumer = NULL; in regulator_bulk_get() 3786 regulator_put(consumers[i].consumer); in regulator_bulk_get() 3812 struct regulator_bulk_data *consumers) in regulator_bulk_enable() argument [all …]
|
/Linux-v4.19/Documentation/infiniband/ |
D | core_locking.txt | 27 consumers: 58 consumers are not required to perform any serialization. However, 93 Upper level protocol consumers may not sleep in a callback. 98 consumers when it calls ib_register_device(), all initialization
|
/Linux-v4.19/Documentation/devicetree/bindings/clock/ |
D | nvidia,tegra210-car.txt | 15 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
|
D | nvidia,tegra114-car.txt | 15 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
|
D | nvidia,tegra20-car.txt | 15 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
|
D | nvidia,tegra30-car.txt | 15 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
|
/Linux-v4.19/Documentation/driver-api/ |
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 | device_link.rst | 142 device links from the hotplug ports (consumers) to the NHI device 196 entire sub-graph below it (all children and consumers of the consumer) 202 on the consumer or any children or consumers of the consumer. 239 * When a supplier device is bound to a driver, links to its consumers 265 * Before a supplier's driver is removed, links to consumers that are not 269 This prevents the consumers from binding. 272 Consumers that are bound are freed from their driver; consumers that are 276 Once all links to consumers are in ``DL_STATE_SUPPLIER_UNBIND`` state,
|
/Linux-v4.19/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-v4.19/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
|
D | regulator.txt | 5 - regulator-min-microvolt: smallest voltage consumers may set 6 - regulator-max-microvolt: largest voltage consumers may set 8 - regulator-min-microamp: smallest current consumers may set 9 - regulator-max-microamp: largest current consumers may set
|
/Linux-v4.19/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-v4.19/Documentation/devicetree/bindings/phy/ |
D | qcom,usb-8x16-phy.txt | 16 Definition: See clock-bindings.txt section "consumers". List of 43 Definition: See reset.txt section "consumers". PHY reset specifier.
|
/Linux-v4.19/Documentation/devicetree/bindings/iio/adc/ |
D | sigma-delta-modulator.txt | 6 - #io-channel-cells = <0>: See the IIO bindings section "IIO consumers".
|
/Linux-v4.19/Documentation/devicetree/bindings/nvmem/ |
D | amlogic-efuse.txt | 30 = Data consumers =
|
/Linux-v4.19/Documentation/devicetree/bindings/hwlock/ |
D | sirf,hwspinlock.txt | 13 Please look at the generic hwlock binding for usage information for consumers,
|
/Linux-v4.19/Documentation/nvmem/ |
D | nvmem.txt | 64 NVMEM consumers are the entities which make use of the NVMEM provider to 91 To facilitate such consumers NVMEM framework provides below apis. 106 Before the consumers can read/write NVMEM directly, it should get hold
|
/Linux-v4.19/Documentation/devicetree/bindings/mux/ |
D | mux-controller.txt | 10 A mux controller provides a number of states to its consumers, and the state 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-v4.19/drivers/iio/ |
D | Kconfig | 42 int "Maximum number of consumers per trigger" 46 This value controls the maximum number of consumers that a
|