Searched full:step (Results 1 – 25 of 332) sorted by relevance
12345678910>>...14
| /Documentation/devicetree/bindings/mfd/ |
| D | ams,as3711.yaml | 15 two step-up DC/DC converters are defined.
26 Step-up converter configuration, to be used as a backlight source
34 description: Framebuffer phandle for the first step-up converter
38 description: Maximum current for the first step-up converter
42 description: Framebuffer phandle for the second step-up converter
46 description: Maximum current for the second step-up converter
50 description: Second step-up converter uses voltage feedback
55 Second step-up converter uses CURR1 input for current feedback
60 Second step-up converter uses CURR2 input for current feedback
65 Second step-up converter uses CURR3 input for current feedback
[all …]
|
| /Documentation/devicetree/bindings/regulator/ |
| D | tps51632-regulator.txt | 9 - ti,dvfs-step-20mV: The 20mV step voltage when PWM DVFS enabled. Missing this
10 will set 10mV step voltage in PWM DVFS mode. In normal mode, the voltage
11 step is 10mV as per datasheet.
26 ti,dvfs-step-20mV;
|
| /Documentation/devicetree/bindings/mtd/ |
| D | hisi504-nand.txt | 17 - nand-ecc-strength: Number of bits to correct per ECC step.
18 - nand-ecc-step-size: Number of data bytes covered by a single ECC step.
20 The following ECC strength and step size are currently supported:
22 - nand-ecc-strength = <16>, nand-ecc-step-size = <1024>
36 nand-ecc-step-size = <1024>;
|
| D | amlogic,meson-nand.yaml | 52 nand-ecc-step-size:
75 amlogic,boot-page-step:
86 nand-ecc-strength: [nand-ecc-step-size]
87 nand-ecc-step-size: [nand-ecc-strength]
88 amlogic,boot-pages: [nand-is-boot-medium, "amlogic,boot-page-step"]
89 amlogic,boot-page-step: [nand-is-boot-medium, "amlogic,boot-pages"]
|
| D | vf610-nfc.txt | 33 - nand-ecc-step-size: step size equals page size, currently only 2k pages are
56 nand-ecc-step-size = <2048>;
|
| D | nand-chip.yaml | 53 Maximum number of bits that can be corrected per ECC step.
57 nand-ecc-step-size:
59 Number of data bytes covered by a single ECC step.
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | ti,am3359-adc.yaml | 33 ti,chan-step-opendelay:
36 to wait after applying the step configuration registers and before sending
42 ti,chan-step-sampledelay:
50 ti,chan-step-avg:
72 ti,chan-step-opendelay = <0x098 0x3ffff 0x098 0x0>;
73 ti,chan-step-sampledelay = <0xff 0x0 0xf 0x0>;
74 ti,chan-step-avg = <16 2 4 8>;
|
| /Documentation/devicetree/bindings/leds/ |
| D | maxim,max77693.yaml | 41 Valid values: 3300 - 5500, step by 25 (rounded down)
52 Valid values: 2400 - 3400, step by 33 (rounded down)
76 15625 - 250000, step by 15625 (rounded down)
78 15625 - 500000, step by 15625 (rounded down)
84 15625 - 1000000, step by 15625 (rounded down)
86 15625 - 1250000, step by 15625 (rounded down)
88 15625 - 625000, step by 15625 (rounded down)
92 Valid values: 62500 - 1000000, step by 62500 (rounded down)
|
| /Documentation/admin-guide/media/ |
| D | si4713.rst | 79 rds_signal_deviation (int) : min=0 max=90000 step=10 default=200 value=200 flags=slider
80 rds_program_id (int) : min=0 max=65535 step=1 default=0 value=0
81 rds_program_type (int) : min=0 max=31 step=1 default=0 value=0
82 rds_ps_name (str) : min=0 max=96 step=8 value='si4713 '
83 rds_radio_text (str) : min=0 max=384 step=32 value=''
85 audio_limiter_release_time (int) : min=250 max=102390 step=50 default=5010 value=5010 flags=slider
86 audio_limiter_deviation (int) : min=0 max=90000 step=10 default=66250 value=66250 flags=slider
88 audio_compression_gain (int) : min=0 max=20 step=1 default=15 value=15 flags=slider
89 audio_compression_threshold (int) : min=-40 max=0 step=1 default=-40 value=-40 flags=slider
90 audio_compression_attack_time (int) : min=0 max=5000 step=500 default=0 value=0 flags=slider
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-fm-tx.rst | 27 step are driver-specific.
107 useconds. Step and range are driver-specific.
110 Configures audio frequency deviation level in Hz. The range and step
121 range and step are driver-specific.
125 value. The range and step are driver-specific.
129 value. The range and step are driver-specific.
133 useconds value. The range and step are driver-specific.
140 range and step are driver-specific.
144 step are driver-specific.
173 dBuV. Range and step are driver-specific.
[all …]
|
| D | ext-ctrls-rf-tuner.rst | 47 range and step are driver-specific.
64 range and step are driver-specific.
71 differs from the each others. The range and step are
78 The range and step are driver-specific.
84 ``V4L2_CID_RF_TUNER_IF_GAIN_AUTO`` is not set. The range and step
|
| D | vidioc-enum-frameintervals.rst | 53 - **Step-wise:** The function returns success if the given index value
59 - **Continuous:** This is a special case of the step-wise type above.
63 the union only the ``stepwise`` member is valid and the ``step``
114 - ``step``
115 - Frame interval step size [s].
179 - Step-wise defined frame interval.
|
| D | vidioc-queryctrl.rst | 135 - ``step``
136 - This field gives a step size for the control. See enum
137 :c:type:`v4l2_ctrl_type` how the step value is
152 0-511 and the driver reports 0-65535, step should be 128.
154 Note that although signed, the step value is supposed to be always
216 - ``step``
217 - This field gives a step size for the control. See enum
218 :c:type:`v4l2_ctrl_type` how the step value is
233 0-511 and the driver reports 0-65535, step should be 128.
326 - ``step``
[all …]
|
| D | vidioc-enum-framesizes.rst | 54 - **Step-wise:** The function returns success if the given index value
60 - **Continuous:** This is a special case of the step-wise type above.
120 - Frame width step size [pixel].
129 - Frame height step size [pixel].
187 - Step-wise defined frame size.
|
| /Documentation/admin-guide/ |
| D | quickly-build-trimmed-linux.rst | 15 section below: it contains a step-by-step guide, which is more detailed, but
54 Step-by-step guide
117 section for the step that explains adjusting your kernels build
360 Reference section for the step-by-step guide
379 [:ref:`back to step-by-step guide <backup_sbs>`]
416 [:ref:`back to step-by-step guide <secureboot_sbs>`]
462 [:ref:`back to step-by-step guide <buildrequires_sbs>`]
480 [:ref:`back to step-by-step guide <diskspace_sbs>`]
491 The step-by-step guide outlines how to retrieve Linux' sources using a shallow
504 [:ref:`back to step-by-step guide <sources_sbs>`]
[all …]
|
| D | verify-bugs-and-bisect-regressions.rst | 32 over to the* ':ref:`step-by-step guide <introguide_bissbs>`' *below. It utilizes
101 # job. See the step-by-step guide for further details.
160 this step (e.g. build, install, boot, and test a kernel to then tell Git
222 Step-by-step guide on how to verify bugs and bisect regressions
254 pitfalls, as well as problems that might occur at the particular step -- and how
408 step told you to boot; if you are unsure, check the current kernelrelease
446 previous step was already tailored to your and your hardware needs, in which
447 case you should skip this step.
456 There is a catch to this, as the 'apparently' in initial sentence of this step
793 In case you skipped the 'test latest codebase' step in the guide, check its
[all …]
|
| /Documentation/admin-guide/pm/ |
| D | suspend-flows.rst | 60 it and to prevent user space from entering the kernel while the next step
129 leaves the idle state entered in the last step of the preceding suspend
152 Tasks frozen in step 2 of the preceding `suspend <s2idle_suspend_>`_
159 This is analogous to step 1 of the `suspend <s2idle_suspend_>`_ transition
172 This step is the same as step 1 of the suspend-to-idle suspend transition
177 This step is the same as step 2 of the suspend-to-idle suspend transition
182 This step is analogous to step 3 of the suspend-to-idle suspend transition
254 The CPUs disabled in step 4 of the preceding suspend transition are taken
259 This step is the same as step 2 of the suspend-to-idle suspend transition
264 This step is the same as step 3 of the suspend-to-idle suspend transition
[all …]
|
| /Documentation/translations/zh_CN/core-api/ |
| D | cpu_hotplug.rst | 586 bash-394 [001] 22.976: cpuhp_enter: cpu: 0004 target: 140 step: 169 (cpuhp_kick_ap_work)
587 cpuhp/4-31 [004] 22.977: cpuhp_enter: cpu: 0004 target: 140 step: 168 (sched_cpu_deactivate)
588 cpuhp/4-31 [004] 22.990: cpuhp_exit: cpu: 0004 state: 168 step: 168 ret: 0
589 cpuhp/4-31 [004] 22.991: cpuhp_enter: cpu: 0004 target: 140 step: 144 (mce_cpu_pre_down)
590 cpuhp/4-31 [004] 22.992: cpuhp_exit: cpu: 0004 state: 144 step: 144 ret: 0
591 …cpuhp/4-31 [004] 22.993: cpuhp_multi_enter: cpu: 0004 target: 140 step: 143 (virtnet_cpu_down_p…
592 cpuhp/4-31 [004] 22.994: cpuhp_exit: cpu: 0004 state: 143 step: 143 ret: 0
593 cpuhp/4-31 [004] 22.995: cpuhp_enter: cpu: 0004 target: 140 step: 142 (cacheinfo_cpu_pre_down)
594 cpuhp/4-31 [004] 22.996: cpuhp_exit: cpu: 0004 state: 142 step: 142 ret: 0
595 bash-394 [001] 22.997: cpuhp_exit: cpu: 0004 state: 140 step: 169 ret: 0
[all …]
|
| /Documentation/PCI/ |
| D | pci-error-recovery.rst | 119 STEP 0: Error Event
126 STEP 1: Notification
155 The next step taken will depend on the result codes returned by the
161 proceeds to STEP 2 (MMIO Enable).
164 then recovery proceeds to STEP 4 (Slot Reset).
166 If the platform is unable to recover the slot, the next step
167 is STEP 6 (Permanent Failure).
188 STEP 2: MMIO Enabled
202 instead will have gone directly to STEP 3 (Link Reset) or STEP 4 (Slot Reset)
235 The next step taken depends on the results returned by the drivers.
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | statistics.rst | 10 Each user-defined region specifies a starting sector, length and step.
11 Individual statistics will be collected for each step-sized area within
14 The I/O statistics counters for each step-sized area of a region are
43 …@stats_create <range> <step> [<number_of_optional_arguments> <optional_arguments>...] [<program_id…
53 <step>
126 <region_id>: <start_sector>+<length> <step> <program_id> <aux_data>
133 Print counters for each step-sized area of a region.
146 Output format for each step-sized area of a region:
|
| /Documentation/devicetree/bindings/iio/health/ |
| D | maxim,max30102.yaml | 30 description: RED LED current. Each step is approximately 200 microamps.
35 description: IR LED current. Each step is approximately 200 microamps.
40 description: Green LED current. Each step is approximately 200 microamps.
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | bq25980.yaml | 43 switch cap mode. 100000 micro volt step.
50 Maximum input current limit in micro amps with a 100000 micro amp step.
57 switch cap mode. 50000 micro volt step.
63 Maximum input current limit in micro amps with a 100000 micro amp step.
|
| /Documentation/networking/ |
| D | net_dim.rst | 48 supplied to the previous iteration. The comparison step checks the difference
49 between the new and previous data and decides on the result of the last step.
50 A step would result as "better" if bandwidth increases and as "worse" if
56 considered "better". Step #2 has an optimization for avoiding false results: it
61 Step #3 decides on the suggested configuration based on the result from step #2
68 decide to verify this decision by taking a step in the other direction. This is
73 The last step is to notify the registered driver that it should apply the
100 step. The sample should include bytes, packets and interrupts, measured by
|
| /Documentation/devicetree/bindings/sound/ |
| D | cs35l33.txt | 23 a value of 1 and will increase at a step size of 100mV until a maximum of
36 with a step size of 15625uA. The default is 2500000uA.
63 of 1 and increases with a step size of 50mV to a maximum of 750mV (value of
81 by 100mV per step to a maximum of 5500mV.
91 1800mV with a step size of 50mV up to a maximum value of 1750mV.
|
| /Documentation/filesystems/ |
| D | befs.rst | 53 step 1. Install the BeFS patch into the source code tree of linux.
62 if the patching step fails (i.e. there are rejected hunks), you can try to
66 step 2. Configuration & make kernel
86 step 3. Install
89 instructions on this critical step.
|
12345678910>>...14