| /linux-5.10/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 | 113 if (rdev->constraints && rdev->constraints->name) in rdev_get_name()
114 return rdev->constraints->name; in rdev_get_name()
128 if (!rdev->constraints) { in regulator_ops_is_valid()
129 rdev_err(rdev, "no constraints\n"); in regulator_ops_is_valid()
133 if (rdev->constraints->valid_ops_mask & ops) in regulator_ops_is_valid()
440 if (*max_uV > rdev->constraints->max_uV) in regulator_check_voltage()
441 *max_uV = rdev->constraints->max_uV; in regulator_check_voltage()
442 if (*min_uV < rdev->constraints->min_uV) in regulator_check_voltage()
443 *min_uV = rdev->constraints->min_uV; in regulator_check_voltage()
505 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 | 103 init_data->constraints.apply_uV = 0; in of_get_fixed_voltage_config()
105 config->supply_name = init_data->constraints.name; in of_get_fixed_voltage_config()
106 if (init_data->constraints.min_uV == init_data->constraints.max_uV) { in of_get_fixed_voltage_config()
107 config->microvolts = init_data->constraints.min_uV; in of_get_fixed_voltage_config()
114 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()
365 if (init_data->constraints.boot_on || init_data->constraints.always_on) in pwm_regulator_probe()
|
| /linux-5.10/arch/arm/mach-s3c/ |
| D | mach-smdk6410.c | 212 .constraints = {
295 .constraints = {
308 .constraints = {
319 .constraints = {
327 .constraints = {
335 .constraints = {
343 .constraints = {
351 .constraints = {
359 .constraints = {
367 .constraints = {
[all …]
|
| D | mach-gta02.c | 252 .constraints = {
261 .constraints = {
270 .constraints = {
279 .constraints = {
288 .constraints = {
297 .constraints = {
305 .constraints = {
313 .constraints = {
322 .constraints = {
331 .constraints = {
[all …]
|
| D | mach-crag6410.c | 342 .constraints = {
406 .constraints = {
424 .constraints = {
437 .constraints = {
444 .constraints = {
457 .constraints = {
467 .constraints = {
475 .constraints = {
483 .constraints = {
491 .constraints = {
[all …]
|
| /linux-5.10/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-5.10/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.
111 * bootloader then it will be enabled when the constraints are
222 * Initialisation constraints, our supply and consumers supplies.
226 * be explicitly set using the constraints field 'name'.
228 * @constraints: Constraints. These must be specified for the regulator to
239 struct regulation_constraints constraints; member
|
| /linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-selection.rst | 68 requested rectangle. An application may introduce constraints to control
93 1. Satisfy constraints from struct
111 constraints flags have to be violated at then ``ERANGE`` is returned. The
113 constraints.
120 .. kernel-figure:: constraints.svg
121 :alt: constraints.svg
182 ``r`` rectangle to satisfy all constraints given in the ``flags``
|
| /linux-5.10/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-5.10/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-5.10/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
171 one or multiple constraints like short term, long term and peak power,
215 Constraints section in Power Zone Attributes
257 The number of constraints in a power zone and the corresponding callbacks have
|
| /linux-5.10/drivers/soc/samsung/ |
| D | exynos-regulator-coupler.c | 9 * if consumers didn't apply their constraints yet.
26 struct regulation_constraints *constraints = rdev->constraints; in regulator_get_optimal_voltage() local
55 /* apply constraints */ in regulator_get_optimal_voltage()
68 max_spread = constraints->max_spread[0]; in regulator_get_optimal_voltage()
|
| /linux-5.10/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
|
| D | machine.rst | 37 Constraints can now be registered by defining a struct regulator_init_data
42 .constraints = {
65 .constraints = {
|
| /linux-5.10/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-5.10/drivers/staging/media/atomisp/pci/isp/kernels/ctc/ctc_1.0/ |
| D | ia_css_ctc_types.h | 82 u0.13, [0,8191], constraints: 0<x1<x2,
85 u0.13, [0,8191], constraints: x1<x2<x3,
88 u0.13, [0,8191], constraints: x2<x3<x4,
91 u0.13, [0,8191], constraints: x3<x4<8191,
|
| /linux-5.10/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-5.10/fs/jffs2/ |
| D | README.Locking | 37 Ordering constraints: See f->sem.
62 Ordering constraints:
115 Ordering constraints:
147 Ordering constraints:
168 Ordering constraints:
|
| /linux-5.10/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
147 * Internal function to update the constraints list using the PM QoS core
271 /* Flush the constraints lists for the device. */ in dev_pm_qos_constraints_destroy()
275 * Update constraints list and call the notification in dev_pm_qos_constraints_destroy()
373 * This function inserts a new entry in the device constraints list of
499 * Will remove pm qos request from the list of constraints and
523 * of per-device PM QoS constraints
[all …]
|
| /linux-5.10/include/dt-bindings/interconnect/ |
| D | qcom,icc.h | 10 * The AMC bucket denotes constraints that are applied to hardware when
11 * icc_set_bw() completes, whereas the WAKE and SLEEP constraints are applied
|