Searched full:resolution (Results 1 – 25 of 262) sorted by relevance
1234567891011
| /Documentation/timers/ |
| D | hrtimers.rst | 2 hrtimers - subsystem for high-resolution kernel timers
5 This patch introduces a new subsystem for high-resolution kernel timers.
9 back and forth trying to integrate high-resolution and high-precision
11 such high-resolution timer implementations in practice, we came to the
18 - the forced handling of low-resolution and high-resolution timers in
30 necessitate a more complex handling of high resolution timers, which
62 high-resolution timer subsystem as well.
64 While this subsystem does not offer high-resolution clock sources just
65 yet, the hrtimer subsystem can be easily extended with high-resolution
73 resolution and low precision use cases - once the precision-sensitive
[all …]
|
| D | highres.rst | 2 High resolution timers and dynamic ticks design notes
26 - high resolution timer functionality
82 functionality like high resolution timers or dynamic ticks.
102 accounting, profiling, and high resolution timers.
132 utilize the high resolution and dynamic tick functionalities without any change
134 enabling of high resolution timers and dynamic ticks is simply provided by
142 high resolution timer functionality
145 During system boot it is not possible to use the high resolution timer
150 the high resolution functionality can work. Up to the point where hrtimers are
151 initialized, the system works in the usual low resolution periodic mode. The
[all …]
|
| /Documentation/devicetree/bindings/iio/resolver/ |
| D | adi,ad2s1210.yaml | 13 The AD2S1210 is a complete 10-bit to 16-bit resolution tracking
34 In normal mode, the resolution of the digital output is selected using
35 the RES0 and RES1 input pins. In configuration mode, the resolution is
38 RES1 RES0 Resolution (Bits)
101 resolution-gpios:
104 resolution of the digital output. If omitted, it is assumed that the
105 RES0 and RES1 pins are hard-wired to match the assigned-resolution-bits
125 assigned-resolution-bits:
127 Resolution of the digital output required by the application. This
129 be measured. If resolution-gpios is omitted, it is assumed that RES0 and
[all …]
|
| /Documentation/fb/ |
| D | viafb.rst | 67 - 0 : Resolution: 640x480, Channel: single, Dithering: Enable
68 - 1 : Resolution: 800x600, Channel: single, Dithering: Enable
69 - 2 : Resolution: 1024x768, Channel: single, Dithering: Enable (default)
70 - 3 : Resolution: 1280x768, Channel: single, Dithering: Enable
71 - 4 : Resolution: 1280x1024, Channel: dual, Dithering: Enable
72 - 5 : Resolution: 1400x1050, Channel: dual, Dithering: Enable
73 - 6 : Resolution: 1600x1200, Channel: dual, Dithering: Enable
75 - 8 : Resolution: 800x480, Channel: single, Dithering: Enable
76 - 9 : Resolution: 1024x768, Channel: dual, Dithering: Enable
77 - 10: Resolution: 1024x768, Channel: single, Dithering: Disable
[all …]
|
| D | viafb.modes | 13 # Resolution 640 480
38 # Resolution 640 480
59 # Resolution 640 480
80 # Resolution 640 480
101 # Resolution 640 480
122 # Resolution 720 480
143 # Resolution 800 480
164 # Resolution 720 576
185 # Resolution 800 600
207 # Resolution 800 600
[all …]
|
| D | efifb.rst | 36 For GOP displays, efifb can autodetect the display's resolution and framebuffer
55 horizontal and vertical resolution, and optionally bit depth, and set
61 The EFI stub will choose the mode with the highest resolution (product
62 of horizontal and vertical resolution). If there are multiple modes
63 with the highest resolution, it will choose one with the highest color
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-w1_therm | 47 What: /sys/bus/w1/devices/.../resolution
51 (RW) get or set the device resolution (on supported devices,
52 if not, this entry is not present). Note that the resolution
57 * '9..14': device resolution in bit
58 or resolution to set in bit
59 * '-xx': xx is kernel error when reading the resolution
62 Some DS18B20 clones are fixed in 12-bit resolution, so the
63 actual resolution is read back from the chip and verified. Error
82 conversion duration depend on the resolution (if
84 resolution, 750ms for 12bits.
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | dev-decoder.rst | 65 height for given coded resolution.
67 coded resolution
68 stream resolution in pixels aligned to codec and hardware requirements;
69 typically visible resolution rounded up to full macroblocks;
70 see also: visible resolution.
73 width for given coded resolution.
139 height in pixels for given source resolution; relevant to encoders only.
141 source resolution
142 resolution in pixels of source frames being source to the encoder and
143 subject to further cropping to the bounds of visible resolution; relevant to
[all …]
|
| D | dev-stateless-decoder.rst | 92 ``OUTPUT`` format being set, including resolution, colorimetry
110 frame buffer resolution for the decoded frames.
142 to hardware limitations). After setting a resolution of 1920x1088 or lower
144 YUV and RGB pixel formats, but after setting a resolution higher than
146 unsupported for this resolution.
162 frame buffer resolution of the decoded stream; typically unchanged from
373 resolution may have changed and follow the dynamic resolution change sequence in
388 Dynamic resolution change
391 If the client detects a resolution change in the stream, it will need to perform
392 the initialization sequence again with the new resolution:
[all …]
|
| /Documentation/hwmon/ |
| D | lm73.rst | 28 Measurement Resolution Support
32 LSB: 0.25, 0.125, 0.0625, and 0.3125. Changing the resolution mode
34 From userspace, the desired resolution can be specified as a function of
37 maximum times defined for the resolution in the datasheet.
40 Resolution Conv. Time Input Range
81 Mathematically, the resolution can be derived from the conversion time
87 resolution in degrees C per LSB.
|
| D | ds1621.rst | 102 also pin compatible with the DS1621 and provide multi-resolution support.
114 - DS1631 - 93ms..750ms for 9..12 bits resolution, respectively.
115 - DS1721 - 93ms..750ms for 9..12 bits resolution, respectively.
116 - DS1731 - 93ms..750ms for 9..12 bits resolution, respectively.
135 Temperature Resolution:
137 As mentioned above, the DS1631, DS1721, and DS1731 provide multi-resolution
154 At initial device power-on, the default resolution is set to 12-bits.
156 The resolution mode for the DS1631, DS1721, or DS1731 can be changed from
158 will normalize the range of input values to the device maximum resolution
162 Resolution Conversion Time Input Range
[all …]
|
| D | lm90.rst | 474 * 8 bit sensor resolution
477 * 8 bit sensor resolution
481 * 11 bit sensor resolution for remote temperature sensor
486 * 11 bit resolution for remote temperature sensor
490 * 11 bit resolution for remote temperature sensor
514 * Lower resolution for remote temperature
516 * 10 bit temperature resolution
521 * 10 bit temperature resolution for external sensors
528 * Better local resolution (10 bit)
529 * 10 bit external sensor resolution
[all …]
|
| D | tmp513.rst | 35 -40 to + 125 degrees with a resolution of 0.0625 degree C.
40 0 to 127.5 degrees with a resolution of 0.5 degree.
54 shunt resistor value. The value resolution will be equal to 10uV/Rshunt.
68 The bus voltage range is read from the chip with a resolution of 4mV. The chip
84 The bus power and bus currents range and resolution depends on the calibration
|
| D | adc128d818.rst | 28 measurement has a resolution of 0.5 degrees; the limits have a resolution
35 inputs can measure voltages between 0 and 2.55 volts, with a resolution
|
| D | lm70.rst | 56 13-bit temperature data (0.0625 degrees celsius resolution).
61 with 0.25 degrees Celsius resolution.
64 data (0.03125 degrees celsius resolution).
|
| D | tmp401.rst | 59 Celsius. Resolution of the remote sensor is 0.0625 degree. Local
60 sensor resolution can be set to 0.5, 0.25, 0.125 or 0.0625 degree (not
61 supported by the driver so far, so using the default resolution of 0.5
|
| D | tmp103.rst | 23 temperatures to a resolution of 1°C. The TMP103 is specified for
26 Resolution: 8 Bits
|
| /Documentation/userspace-api/media/rc/ |
| D | lirc-get-rec-resolution.rst | 13 LIRC_GET_REC_RESOLUTION - Obtain the value of receive resolution, in microseconds.
29 Resolution, in microseconds.
34 Some receivers have maximum resolution which is defined by internal
38 This ioctl returns the integer value with such resolution, with can be
|
| /Documentation/w1/slaves/ |
| D | w1_therm.rst | 61 its current resolution. Default conversion time is set by the driver according
70 Writing a resolution value (in bits) to ``w1_slave`` will change the
72 the sensor. Resolution is reset when the sensor gets power-cycled.
74 To store the current resolution in EEPROM, write ``0`` to ``w1_slave``.
78 Alternatively, resolution can be read or written using the dedicated
79 ``resolution`` entry on each device, if supported by the sensor.
82 resolution is read back from the chip and verified.
84 Note: Changing the resolution reverts the conversion time to default.
138 resolutions. The device is powered up in 14-bit resolution mode. The conversion
144 indicating 15, but the device is always operating in 14-bit resolution mode.
|
| /Documentation/devicetree/bindings/iio/proximity/ |
| D | semtech,sx9324.yaml | 82 semtech,ph01-resolution:
86 Capacitance measurement resolution. For phase 0 and 1.
87 Higher the number, higher the resolution.
90 semtech,ph23-resolution:
94 Capacitance measurement resolution. For phase 2 and 3
193 semtech,ph01-resolution = <256>;
194 semtech,ph23-resolution = <256>;
|
| D | semtech,sx9360.yaml | 38 semtech,resolution:
42 Capacitance measurement resolution. For both phases, "reference" and
43 "measurement". Higher the number, higher the resolution.
93 semtech,resolution = <256>;
|
| /Documentation/sound/ |
| D | utimers.rst | 39 __u64 resolution;
45 The ``resolution`` field sets the desired resolution in nanoseconds for
46 the virtual timer. ``resolution`` field simply provides an information
67 .resolution = 1000000ULL,
120 ``resolution`` for the userspace-driven ALSA timer used with snd-aloop
|
| /Documentation/iio/ |
| D | ad7380.rst | 61 Oversampling and resolution boost
70 exceed the default resolution. To accommodate the performance boost achievable,
71 it is possible to enable an additional two bits of resolution. Because the
72 resolution boost feature can only be enabled when oversampling is enabled and
73 oversampling is not as useful without the resolution boost, the driver
74 automatically enables the resolution boost if and only if oversampling is
77 Since the resolution boost feature causes 16-bit chips to now have 18-bit data
|
| /Documentation/devicetree/bindings/input/touchscreen/ |
| D | auo_pixcir_ts.txt | 9 - x-size: horizontal resolution of touchscreen
10 - y-size: vertical resolution of touchscreen
|
| /Documentation/input/ |
| D | event-codes.rst | 198 physical size of which varies by device. For high-resolution wheels
199 this may be an approximation based on the high-resolution scroll events,
206 - High-resolution scroll wheel data. The accumulated value 120 represents
207 movement by one detent. For devices that do not provide high-resolution
209 high-resolution scrolling, the value may be a fraction of 120.
211 If a vertical scroll wheel supports high-resolution scrolling, this code
213 and REL_HWHEEL may be an approximation based on the high-resolution
214 scroll events. There is no guarantee that the high-resolution data
257 A device should set the resolution of the axis to indicate whether the
258 pressure is in measurable units. If the resolution is zero, the
[all …]
|
1234567891011