| /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 …]
|
| /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
|
| D | i2c.rst | 30 systems are also I2C conformant. The electrical constraints are tighter
|
| /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``
|
| D | selection-api-vs-crop-api.rst | 38 the selection API the concepts of the padded target and constraints
|
| /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
|
| /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 = {
|
| /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
|
| /Documentation/devicetree/bindings/ |
| D | writing-bindings.txt | 46 constraints specific to the device.
51 - DO define properties in terms of constraints. How many entries? What are
|
| D | example-schema.yaml | 120 # constraints on the possible values.
133 # type schema is referenced and then additional constraints on the values
|
| /Documentation/RCU/ |
| D | lockdep.txt | 54 and compiler constraints. This is useful when the data
59 but retain the compiler constraints that prevent duplicating
94 barriers and compiler constraints, it generates better code than do the
|
| /Documentation/userspace-api/ |
| D | no_new_privs.rst | 29 add to the permitted set, and LSMs will not relax constraints after
36 Be careful, though: LSMs might also not tighten constraints on exec
|
| /Documentation/leds/ |
| D | leds-class-flash.rst | 68 constraints for the LED in TORCH mode
71 constraints for the indicator LED
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-zoned.rst | 7 pattern constraints. In effect, it implements a drive-managed zoned
9 doing raw block device accesses) the sequential write constraints of
15 their constraints see (for SCSI devices):
|
| /Documentation/core-api/ |
| D | packing.rst | 35 constraints/quirks)
36 - Unpacking a memory buffer (which has hardware constraints/quirks)
39 The API offers an abstraction over said hardware constraints and quirks,
|
| /Documentation/i2c/ |
| D | summary.rst | 21 meet both SMBus and I2C electrical constraints; and others which can't
|
| /Documentation/devicetree/bindings/interconnect/ |
| D | interconnect.txt | 14 etc. The consumer drivers set constraints on interconnect path (or endpoints)
|
| /Documentation/devicetree/ |
| D | writing-schema.rst | 81 binding. Each property contains a set of constraints using json-schema
85 For common properties, only additional constraints not covered by the common
|
| /Documentation/devicetree/bindings/regulator/ |
| D | max77686.txt | 17 standard regulator constraints....
|
| D | lm363x-regulator.txt | 28 Each sub-node should contain the constraints and initialization.
|
| /Documentation/sound/designs/ |
| D | tracepoints.rst | 116 :c:type:`struct snd_pcm_hardware` and rules of constraints in the runtime. The
130 of constraints into the runtime when several parameters have dependencies
|
| /Documentation/arm/omap/ |
| D | omap_pm.rst | 7 throughput constraints to the kernel power management code.
24 DaVinci) to add these constraints in a way which won't affect non-OMAP
|
| /Documentation/devicetree/bindings/arm/ |
| D | pmu.yaml | 46 # Don't know how many CPUs, so no constraints to specify
|
| /Documentation/ |
| D | unaligned-memory-access.txt | 100 Fortunately, the compiler understands the alignment constraints, so in the
128 to satisfy alignment constraints for arrays of these structures.
138 of the alignment constraints and will generate extra instructions to perform
|