| /Linux-v5.4/drivers/regulator/ |
| D | of_regulator.c | 29 struct regulation_constraints *constraints = &(*init_data)->constraints; in of_get_regulation_constraints() local
41 constraints->name = of_get_property(np, "regulator-name", NULL); in of_get_regulation_constraints()
44 constraints->min_uV = pval; in of_get_regulation_constraints()
47 constraints->max_uV = pval; in of_get_regulation_constraints()
50 if (constraints->min_uV != constraints->max_uV) in of_get_regulation_constraints()
51 constraints->valid_ops_mask |= REGULATOR_CHANGE_VOLTAGE; in of_get_regulation_constraints()
54 if (constraints->min_uV && constraints->max_uV) in of_get_regulation_constraints()
55 constraints->apply_uV = true; in of_get_regulation_constraints()
58 constraints->uV_offset = pval; in of_get_regulation_constraints()
60 constraints->min_uA = pval; in of_get_regulation_constraints()
[all …]
|
| D | core.c | 112 if (rdev->constraints && rdev->constraints->name) in rdev_get_name()
113 return rdev->constraints->name; in rdev_get_name()
127 if (!rdev->constraints) { in regulator_ops_is_valid()
128 rdev_err(rdev, "no constraints\n"); in regulator_ops_is_valid()
132 if (rdev->constraints->valid_ops_mask & ops) in regulator_ops_is_valid()
438 if (*max_uV > rdev->constraints->max_uV) in regulator_check_voltage()
439 *max_uV = rdev->constraints->max_uV; in regulator_check_voltage()
440 if (*min_uV < rdev->constraints->min_uV) in regulator_check_voltage()
441 *min_uV = rdev->constraints->min_uV; in regulator_check_voltage()
503 if (*max_uA > rdev->constraints->max_uA) in regulator_check_current_limit()
[all …]
|
| D | ab8500-ext.c | 308 .constraints = {
322 .constraints = {
338 .constraints = {
353 .constraints = {
362 .constraints = {
371 .constraints = {
380 .constraints = {
389 .constraints = {
398 .constraints = {
415 .constraints = {
[all …]
|
| D | fixed.c | 111 init_data->constraints.apply_uV = 0; in of_get_fixed_voltage_config()
113 config->supply_name = init_data->constraints.name; in of_get_fixed_voltage_config()
114 if (init_data->constraints.min_uV == init_data->constraints.max_uV) { in of_get_fixed_voltage_config()
115 config->microvolts = init_data->constraints.min_uV; in of_get_fixed_voltage_config()
122 if (init_data->constraints.boot_on) in of_get_fixed_voltage_config()
|
| D | vexpress-regulator.c | 66 init_data->constraints.apply_uV = 0; in vexpress_regulator_probe()
67 if (init_data->constraints.min_uV && init_data->constraints.max_uV) in vexpress_regulator_probe()
|
| D | wm8994-regulator.c | 107 .constraints = {
113 .constraints = {
157 /* Use default constraints if none set up */ in wm8994_ldo_probe()
165 ldo->init_data.constraints.valid_ops_mask = 0; in wm8994_ldo_probe()
|
| D | pwm-regulator.c | 151 int min_uV = rdev->constraints->min_uV; in pwm_regulator_get_voltage()
152 int max_uV = rdev->constraints->max_uV; in pwm_regulator_get_voltage()
188 int min_uV = rdev->constraints->min_uV; in pwm_regulator_set_voltage()
189 int max_uV = rdev->constraints->max_uV; in pwm_regulator_set_voltage()
361 if (init_data->constraints.boot_on || init_data->constraints.always_on) in pwm_regulator_probe()
|
| /Linux-v5.4/arch/arm/mach-imx/ |
| D | mach-mx35_3ds.c | 240 .constraints = {
254 .constraints = {
262 .constraints = {
270 .constraints = {
278 .constraints = {
285 .constraints = {
292 .constraints = {
299 .constraints = {
306 .constraints = {
313 .constraints = {
[all …]
|
| D | mach-mx31ads.c | 256 .constraints = {
279 .constraints = {
296 .constraints = {
313 .constraints = {
334 .constraints = {
351 .constraints = {
365 .constraints = {
378 .constraints = {
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-class-regulator | 154 for regulators which support voltage constraints.
169 for regulators which support voltage constraints.
184 microamps, for regulators which support current constraints.
199 microamps, for regulators which support current constraints.
257 implementing suspend voltage configuration constraints.
268 implementing suspend voltage configuration constraints.
279 implementing suspend voltage configuration constraints.
290 configuration constraints.
301 constraints.
312 configuration constraints.
[all …]
|
| /Linux-v5.4/arch/arm/mach-s3c64xx/ |
| D | mach-smdk6410.c | 214 .constraints = {
297 .constraints = {
310 .constraints = {
321 .constraints = {
329 .constraints = {
337 .constraints = {
345 .constraints = {
353 .constraints = {
361 .constraints = {
369 .constraints = {
[all …]
|
| D | mach-crag6410.c | 345 .constraints = {
409 .constraints = {
427 .constraints = {
440 .constraints = {
447 .constraints = {
460 .constraints = {
470 .constraints = {
478 .constraints = {
486 .constraints = {
494 .constraints = {
[all …]
|
| /Linux-v5.4/kernel/power/ |
| D | qos.c | 53 * locking rule: all changes to constraints or notifiers lists
58 struct pm_qos_constraints *constraints; member
77 .constraints = &cpu_dma_constraints,
154 c = qos->constraints; in pm_qos_debug_show()
156 pr_err("%s: Bad constraints on qos?\n", __func__); in pm_qos_debug_show()
204 * pm_qos_update_target - manages the constraints list and calls the notifiers
206 * @c: constraints data struct
208 * @action: action to take on the constraints list
340 return pm_qos_read_value(pm_qos_array[pm_qos_class]->constraints); in pm_qos_request()
357 pm_qos_array[req->pm_qos_class]->constraints, in __pm_qos_update_request()
[all …]
|
| /Linux-v5.4/include/linux/regulator/ |
| D | machine.h | 87 * struct regulation_constraints - regulator operating constraints.
89 * This struct describes regulator and board/machine specific constraints.
91 * @name: Descriptive name for the constraints, used for display purposes.
110 * bootloader then it will be enabled when the constraints are
221 * Initialisation constraints, our supply and consumers supplies.
225 * be explicitly set using the constraints field 'name'.
227 * @constraints: Constraints. These must be specified for the regulator to
238 struct regulation_constraints constraints; member
|
| /Linux-v5.4/arch/arm/mach-s3c24xx/ |
| D | mach-gta02.c | 253 .constraints = {
262 .constraints = {
271 .constraints = {
280 .constraints = {
289 .constraints = {
298 .constraints = {
306 .constraints = {
314 .constraints = {
323 .constraints = {
332 .constraints = {
[all …]
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | vidioc-g-selection.rst | 75 requested rectangle. An application may introduce constraints to control
100 1. Satisfy constraints from struct
118 constraints flags have to be violated at then ``ERANGE`` is returned. The
120 constraints.
128 .. kernel-figure:: constraints.svg
129 :alt: constraints.svg
192 ``r`` rectangle to satisfy all constraints given in the ``flags``
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | regulator.rst | 84 constraints may not allow the regulator to be disabled there is no
134 time as part of the machine constraints.
136 Constraints section in Machine interface
140 constraints defining the operations that clients are allowed to perform
149 The constraints may also specify an initial configuration for the
150 regulator in the constraints, which is particularly useful for use with
|
| /Linux-v5.4/arch/arm/mach-pxa/ |
| D | stargate2.c | 178 /* The values of the various regulator constraints are obviously dependent
184 .constraints = { /* board default 1.8V */
191 .constraints = { /* board default 2.8V */
198 .constraints = {/* default is 1.8V */
205 .constraints = {
213 .constraints = { /* default 1.8V */
220 .constraints = { /* default 2.8V */
227 .constraints = { /* default 2.8V */
234 .constraints = { /* default 2.8V */
241 .constraints = { /* default 2.8V */
[all …]
|
| /Linux-v5.4/Documentation/power/powercap/ |
| D | powercap.rst | 22 well as controls represented in the form of power constraints. If the parts of
156 to be applied (the constraints in the 'package' power zones apply to the whole
157 CPU packages and the subzone constraints only apply to the respective parts of
170 The Intel RAPL technology allows two constraints, short term and long term,
210 Constraints section in Power Zone Attributes
252 The number of constraints in a power zone and the corresponding callbacks have
|
| /Linux-v5.4/Documentation/power/regulator/ |
| D | overview.rst | 92 - Constraints
93 - Constraints are used to define power levels for performance
94 and hardware protection. Constraints exist at three levels:
164 voltage/current domains (with constraints) for each regulator. It can
165 provide regulator constraints that will prevent device damage through
|
| /Linux-v5.4/drivers/crypto/nx/ |
| D | nx-842.h | 113 * This provides the driver's constraints. Different nx842 implementations
114 * may have varying requirements. The constraints are:
120 * The constraints apply to all buffers and lengths, both input and output,
127 * The driver may succeed even if these constraints are violated;
143 struct nx842_constraints *constraints; member
|
| /Linux-v5.4/drivers/base/power/ |
| D | qos.c | 3 * Devices PM QoS constraints management
21 * . The per-device constraints data struct ptr is stored into the device
23 * . To minimize the data usage by the per-device constraints, the data struct
26 * . A global mutex protects the constraints users from the data being
137 * Internal function to update the constraints list using the PM QoS core
255 /* Flush the constraints lists for the device. */ in dev_pm_qos_constraints_destroy()
259 * Update constraints list and call the notification in dev_pm_qos_constraints_destroy()
332 * This function inserts a new entry in the device constraints list of
454 * Will remove pm qos request from the list of constraints and
478 * of per-device PM QoS constraints
[all …]
|
| /Linux-v5.4/Documentation/power/ |
| D | pm_qos_interface.rst | 12 constraints and PM QoS flags.
64 PM QoS class constraints list.
132 Returns the aggregated value for a given device's constraints list.
155 Add a request to the device's PM QoS list of resume latency constraints and
161 PM QoS list of resume latency constraints and remove sysfs attribute
182 The callback is called when the aggregated value of the device constraints list
|
| /Linux-v5.4/security/selinux/ss/ |
| D | constraint.h | 5 * Constraints are used to impose additional restrictions
7 * transition rules in `rbac'. Constraints are typically
10 * Constraints are likewise typically used to prevent a
|
| /Linux-v5.4/fs/jffs2/ |
| D | README.Locking | 37 Ordering constraints: See f->sem.
62 Ordering constraints:
115 Ordering constraints:
147 Ordering constraints:
168 Ordering constraints:
|
