| /linux-6.12.1/drivers/regulator/ |
| D | of_regulator.c | 36 struct regulation_constraints *constraints) in of_get_regulator_prot_limits() argument
47 &constraints->over_curr_limits, in of_get_regulator_prot_limits()
48 &constraints->over_voltage_limits, in of_get_regulator_prot_limits()
49 &constraints->temp_limits, in of_get_regulator_prot_limits()
50 &constraints->under_voltage_limits, in of_get_regulator_prot_limits()
74 constraints->over_current_detection = set[0]; in of_get_regulator_prot_limits()
75 constraints->over_voltage_detection = set[1]; in of_get_regulator_prot_limits()
76 constraints->over_temp_detection = set[2]; in of_get_regulator_prot_limits()
77 constraints->under_voltage_detection = set[3]; in of_get_regulator_prot_limits()
85 struct regulation_constraints *constraints = &(*init_data)->constraints; in of_get_regulation_constraints() local
[all …]
|
| D | core.c | 105 if (rdev->constraints && rdev->constraints->name) in rdev_get_name()
106 return rdev->constraints->name; in rdev_get_name()
121 if (!rdev->constraints) { in regulator_ops_is_valid()
122 rdev_err(rdev, "no constraints\n"); in regulator_ops_is_valid()
126 if (rdev->constraints->valid_ops_mask & ops) in regulator_ops_is_valid()
435 if (*max_uV > rdev->constraints->max_uV) in regulator_check_voltage()
436 *max_uV = rdev->constraints->max_uV; in regulator_check_voltage()
437 if (*min_uV < rdev->constraints->min_uV) in regulator_check_voltage()
438 *min_uV = rdev->constraints->min_uV; in regulator_check_voltage()
500 if (*max_uA > rdev->constraints->max_uA) in regulator_check_current_limit()
[all …]
|
| 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()
198 int min_uV = rdev->constraints->min_uV; in pwm_regulator_set_voltage()
199 int max_uV = rdev->constraints->max_uV; in pwm_regulator_set_voltage()
330 if (!init_data->constraints.boot_on || drvdata->enb_gpio) in pwm_regulator_init_boot_on()
392 if (init_data->constraints.boot_on || init_data->constraints.always_on) in pwm_regulator_probe()
|
| D | vexpress-regulator.c | 67 init_data->constraints.apply_uV = 0; in vexpress_regulator_probe()
68 if (init_data->constraints.min_uV && init_data->constraints.max_uV) in vexpress_regulator_probe()
|
| D | fixed.c | 184 init_data->constraints.apply_uV = 0; in of_get_fixed_voltage_config()
186 config->supply_name = init_data->constraints.name; in of_get_fixed_voltage_config()
187 if (init_data->constraints.min_uV == init_data->constraints.max_uV) { in of_get_fixed_voltage_config()
188 config->microvolts = init_data->constraints.min_uV; in of_get_fixed_voltage_config()
195 if (init_data->constraints.boot_on) in of_get_fixed_voltage_config()
|
| D | ab8500-ext.c | 50 .constraints = {
61 .constraints = {
69 .constraints = {
289 struct regulation_constraints *regu_constraints = rdev->constraints; in ab8500_ext_set_voltage()
292 dev_err(rdev_get_dev(rdev), "No regulator constraints\n"); in ab8500_ext_set_voltage()
311 struct regulation_constraints *regu_constraints = rdev->constraints; in ab8500_ext_list_voltage()
314 dev_err(rdev_get_dev(rdev), "regulator constraints null pointer\n"); in ab8500_ext_list_voltage()
|
| /linux-6.12.1/drivers/platform/x86/intel/int3472/ |
| D | tps68470_board_data.c | 45 .constraints = {
56 .constraints = {
67 .constraints = {
79 .constraints = {
88 .constraints = {
99 .constraints = {
110 .constraints = {
|
| /linux-6.12.1/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-6.12.1/tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/ |
| D | stall.json | 8 …the backend of the pipeline because of backend resource constraints. Backend resource constraints …
16 …ch no operations are sent from the rename unit to the backend due to backend resource constraints."
20 … no operations are sent to the rename unit from the frontend due to frontend resource constraints."
|
| /linux-6.12.1/tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/ |
| D | stall.json | 8 …the backend of the pipeline because of backend resource constraints. Backend resource constraints …
16 …ch no operations are sent from the rename unit to the backend due to backend resource constraints."
20 … no operations are sent to the rename unit from the frontend due to frontend resource constraints."
|
| /linux-6.12.1/include/linux/regulator/ |
| D | machine.h | 102 * struct regulation_constraints - regulator operating constraints.
104 * This struct describes regulator and board/machine specific constraints.
106 * @name: Descriptive name for the constraints, used for display purposes.
131 * bootloader then it will be enabled when the constraints are
266 * Initialisation constraints, our supply and consumers supplies.
270 * be explicitly set using the constraints field 'name'.
272 * @constraints: Constraints. These must be specified for the regulator to
283 struct regulation_constraints constraints; member
|
| /linux-6.12.1/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-6.12.1/arch/arm/mach-s3c/ |
| D | mach-crag6410.c | 340 .constraints = {
404 .constraints = {
422 .constraints = {
435 .constraints = {
442 .constraints = {
455 .constraints = {
465 .constraints = {
473 .constraints = {
481 .constraints = {
489 .constraints = {
[all …]
|
| /linux-6.12.1/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-6.12.1/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-6.12.1/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-6.12.1/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-6.12.1/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-6.12.1/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-6.12.1/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-6.12.1/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-6.12.1/fs/jffs2/ |
| D | README.Locking | 37 Ordering constraints: See f->sem.
62 Ordering constraints:
115 Ordering constraints:
147 Ordering constraints:
168 Ordering constraints:
|
| /linux-6.12.1/arch/x86/include/asm/ |
| D | irq_stack.h | 42 * Note, that (tos) is both in input and output constraints to ensure
52 * - Constraints:
54 * The constraints have to be done very carefully because the compiler
59 * the output constraints to make the compiler aware that R11 cannot be
74 * The constraints are handed in via the 'argconstr' argument list. They
|
| /linux-6.12.1/Documentation/arch/riscv/ |
| D | boot.rst | 4 RISC-V Kernel Boot Requirements and Constraints
11 firmware, and also the constraints that any developer must have in mind when
16 Pre-kernel Requirements and Constraints
105 Early Boot Requirements and Constraints
108 The RISC-V kernel's early boot process operates under the following constraints:
|