Home
last modified time | relevance | path

Searched +full:high +full:- +full:resolution (Results 1 – 25 of 845) sorted by relevance

12345678910>>...34

/kernel/linux/linux-6.6/Documentation/timers/
Dhrtimers.rst2 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
21 32-bitness assumptions, and has been honed and micro-optimized for a
23 for many years - and thus even small extensions to it easily break
26 current usage - but it is simply not suitable to be extended for
27 high-res timers.
29 - the unpredictable [O(N)] overhead of cascading leads to delays which
[all …]
Dhighres.rst2 High resolution timers and dynamic ticks design notes
8 https://www.kernel.org/doc/ols/2006/ols2006v1-pages-333-346.pdf
11 http://www.cs.columbia.edu/~nahum/w6998/papers/ols2006-hrtimers-slides.pdf
23 - hrtimer base infrastructure
24 - timeofday and clock source management
25 - clock event management
26 - high resolution timer functionality
27 - dynamic ticks
31 ---------------------------
40 - time ordered enqueueing into a rb-tree
[all …]
/kernel/linux/linux-5.10/Documentation/timers/
Dhrtimers.rst2 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
21 32-bitness assumptions, and has been honed and micro-optimized for a
23 for many years - and thus even small extensions to it easily break
26 current usage - but it is simply not suitable to be extended for
27 high-res timers.
29 - the unpredictable [O(N)] overhead of cascading leads to delays which
[all …]
Dhighres.rst2 High resolution timers and dynamic ticks design notes
8 https://www.kernel.org/doc/ols/2006/ols2006v1-pages-333-346.pdf
11 http://www.cs.columbia.edu/~nahum/w6998/papers/ols2006-hrtimers-slides.pdf
23 - hrtimer base infrastructure
24 - timeofday and clock source management
25 - clock event management
26 - high resolution timer functionality
27 - dynamic ticks
31 ---------------------------
40 - time ordered enqueueing into a rb-tree
[all …]
/kernel/linux/linux-5.10/Documentation/fb/
Dviafb.modes10 # 640x480, 60 Hz, Non-Interlaced (25.175 MHz dotclock)
13 # Resolution 640 480
28 mode "640x480-60"
31 timings 39722 48 16 33 10 96 2 endmode mode "480x640-60"
35 # 640x480, 75 Hz, Non-Interlaced (31.50 MHz dotclock)
38 # Resolution 640 480
52 mode "640x480-75"
56 # 640x480, 85 Hz, Non-Interlaced (36.000 MHz dotclock)
59 # Resolution 640 480
73 mode "640x480-85"
[all …]
/kernel/linux/linux-6.6/Documentation/fb/
Dviafb.modes10 # 640x480, 60 Hz, Non-Interlaced (25.175 MHz dotclock)
13 # Resolution 640 480
28 mode "640x480-60"
31 timings 39722 48 16 33 10 96 2 endmode mode "480x640-60"
35 # 640x480, 75 Hz, Non-Interlaced (31.50 MHz dotclock)
38 # Resolution 640 480
52 mode "640x480-75"
56 # 640x480, 85 Hz, Non-Interlaced (36.000 MHz dotclock)
59 # Resolution 640 480
73 mode "640x480-85"
[all …]
/kernel/linux/linux-5.10/lib/fonts/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
12 bool "Select compiled-in fonts"
29 This is the "high resolution" font for the VGA frame buffer (the one
35 Given the resolution provided by the frame buffer device, answer N
42 This is the "high resolution" font for the VGA frame buffer (the one
52 Small console font with Macintosh-style high-half glyphs. Some Mac
68 Small console font with PC-style control-character and high-half
76 Small console font with PC-style control characters and high-half
84 bool "Medium-size 6x10 font"
87 Medium-size console font. Suitable for framebuffer consoles on
[all …]
/kernel/linux/linux-6.6/lib/fonts/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
12 bool "Select compiled-in fonts"
29 This is the "high resolution" font for the VGA frame buffer (the one
35 Given the resolution provided by the frame buffer device, answer N
42 This is the "high resolution" font for the VGA frame buffer (the one
52 Small console font with Macintosh-style high-half glyphs. Some Mac
68 Small console font with PC-style control-character and high-half
76 Small console font with PC-style control characters and high-half
84 bool "Medium-size 6x10 font"
87 Medium-size console font. Suitable for framebuffer consoles on
[all …]
/kernel/linux/linux-5.10/Documentation/hwmon/
Dds1621.rst47 - Christian W. Zuckschwerdt <zany@triq.net>
48 - valuable contributions by Jan M. Sendler <sendler@sendler.de>
49 - ported to 2.6 by Aurelien Jarno <aurelien@aurel32.net>
53 ------------------
58 * 0 = active high,
62 -----------
65 both high and low temperature limits which can be user defined (i.e.
66 programmed into non-volatile on-chip registers). Temperature range is -55
68 Fahrenheit range of -67 to +257 degrees with 0.9 steps. If polarity
74 stays high until the high limit is met or exceeded. On the other hand
[all …]
Dadm9240.rst10 Addresses scanned: I2C 0x2c - 0x2f
20 Addresses scanned: I2C 0x2c - 0x2f
24 http://pdfserv.maxim-ic.com/en/ds/DS1780.pdf
30 Addresses scanned: I2C 0x2c - 0x2f
37 - Frodo Looijaard <frodol@dds.nl>,
38 - Philip Edelbrock <phil@netroedge.com>,
39 - Michiel Rook <michiel@grendelproject.nl>,
40 - Grant Coady <gcoady.lk@gmail.com> with guidance
44 ---------
46 chip MSB 5-bit address. Each chip reports a unique manufacturer
[all …]
Dw83793.rst10 Addresses scanned: I2C 0x2c - 0x2f
15 - Yuan Mu (Winbond Electronics)
16 - Rudolf Marek <r.marek@assembler.cz>
20 -----------------
36 -----------
44 sets of 6-pin CPU VID input.
47 If your motherboard maker used the reference design, the resolution of
48 voltage0-2 is 2mV, resolution of voltage3/4/5 is 16mV, 8mV for voltage6,
49 24mV for voltage7/8. Temp1-4 have a 0.25 degree Celsius resolution,
50 temp5-6 have a 1 degree Celsiis resolution.
[all …]
/kernel/linux/linux-6.6/Documentation/hwmon/
Dds1621.rst47 - Christian W. Zuckschwerdt <zany@triq.net>
48 - valuable contributions by Jan M. Sendler <sendler@sendler.de>
49 - ported to 2.6 by Aurelien Jarno <aurelien@aurel32.net>
53 ------------------
58 * 0 = active high,
62 -----------
65 both high and low temperature limits which can be user defined (i.e.
66 programmed into non-volatile on-chip registers). Temperature range is -55
68 Fahrenheit range of -67 to +257 degrees with 0.9 steps. If polarity
74 stays high until the high limit is met or exceeded. On the other hand
[all …]
Dadm9240.rst10 Addresses scanned: I2C 0x2c - 0x2f
20 Addresses scanned: I2C 0x2c - 0x2f
24 http://pdfserv.maxim-ic.com/en/ds/DS1780.pdf
30 Addresses scanned: I2C 0x2c - 0x2f
37 - Frodo Looijaard <frodol@dds.nl>,
38 - Philip Edelbrock <phil@netroedge.com>,
39 - Michiel Rook <michiel@grendelproject.nl>,
40 - Grant Coady <gcoady.lk@gmail.com> with guidance
44 ---------
46 chip MSB 5-bit address. Each chip reports a unique manufacturer
[all …]
Dw83793.rst10 Addresses scanned: I2C 0x2c - 0x2f
15 - Yuan Mu (Winbond Electronics)
16 - Rudolf Marek <r.marek@assembler.cz>
20 -----------------
36 -----------
44 sets of 6-pin CPU VID input.
47 If your motherboard maker used the reference design, the resolution of
48 voltage0-2 is 2mV, resolution of voltage3/4/5 is 16mV, 8mV for voltage6,
49 24mV for voltage7/8. Temp1-4 have a 0.25 degree Celsius resolution,
50 temp5-6 have a 1 degree Celsiis resolution.
[all …]
/kernel/linux/linux-6.6/Documentation/input/
Devent-codes.rst1 .. _input-event-codes:
36 - Used as markers to separate events. Events may be separated in time or in
41 - Used to describe state changes of keyboards, buttons, or other key-like
46 - Used to describe relative axis value changes, e.g. moving the mouse 5 units
51 - Used to describe absolute axis value changes, e.g. describing the
56 - Used to describe miscellaneous input data that do not fit into other types.
60 - Used to describe binary state input switches.
64 - Used to turn LEDs on devices on and off.
68 - Used to output sound to devices.
72 - Used for autorepeating devices.
[all …]
/kernel/linux/linux-5.10/Documentation/input/
Devent-codes.rst1 .. _input-event-codes:
36 - Used as markers to separate events. Events may be separated in time or in
41 - Used to describe state changes of keyboards, buttons, or other key-like
46 - Used to describe relative axis value changes, e.g. moving the mouse 5 units
51 - Used to describe absolute axis value changes, e.g. describing the
56 - Used to describe miscellaneous input data that do not fit into other types.
60 - Used to describe binary state input switches.
64 - Used to turn LEDs on devices on and off.
68 - Used to output sound to devices.
72 - Used for autorepeating devices.
[all …]
/kernel/linux/linux-6.6/Documentation/w1/slaves/
Dw1_therm.rst16 -----------
46 in the module), it will drive the line high during the longer conversion
49 -1 if at least one sensor still in conversion, 1 if conversion is complete
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.
81 Some non-genuine DS18B20 chips are fixed in 12-bit mode only, so the actual
[all …]
/kernel/linux/linux-5.10/Documentation/w1/slaves/
Dw1_therm.rst15 -----------
45 in the module), it will drive the line high during the longer conversion
48 -1 if at least one sensor still in conversion, 1 if conversion is complete
60 it's current resolution. Default conversion time is set by the driver according
69 Writing a resolution value (in bits) to ``w1_slave`` will change the
71 the sensor. Resolution is reset when the sensor gets power-cycled.
73 To store the current resolution in EEPROM, write ``0`` to ``w1_slave``.
77 Alternatively, resolution can be read or written using the dedicated
78 ``resolution`` entry on each device, if supported by the sensor.
80 Some non-genuine DS18B20 chips are fixed in 12-bit mode only, so the actual
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/iio/proximity/
Dsemtech,sx9324.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Gwendal Grignou <gwendal@chromium.org>
11 - Daniel Campello <campello@chromium.org>
17 - $ref: /schemas/iio/iio.yaml#
32 vdd-supply:
35 svdd-supply:
38 "#io-channel-cells":
41 semtech,ph0-pin:
[all …]
/kernel/linux/linux-5.10/include/sound/ac97/
Dregs.h1 /* SPDX-License-Identifier: GPL-2.0+
33 /* range 0x28-0x3a - AUDIO AC'97 2.0 extensions */
44 /* range 0x3c-0x58 - MODEM */
54 #define AC97_GPIO_POLARITY 0x4e /* GPIO Pin Polarity/Type, 0=low, 1=high active */
59 /* range 0x5a-0x7b - Vendor Specific */
62 /* range 0x60-0x6f (page 1) - extended codec registers */
108 #define AC97_BC_16BIT_DAC 0x0000 /* 16-bit DAC resolution */
109 #define AC97_BC_18BIT_DAC 0x0040 /* 18-bit DAC resolution */
110 #define AC97_BC_20BIT_DAC 0x0080 /* 20-bit DAC resolution */
112 #define AC97_BC_16BIT_ADC 0x0000 /* 16-bit ADC resolution */
[all …]
/kernel/linux/linux-6.6/include/sound/ac97/
Dregs.h1 /* SPDX-License-Identifier: GPL-2.0+
33 /* range 0x28-0x3a - AUDIO AC'97 2.0 extensions */
44 /* range 0x3c-0x58 - MODEM */
54 #define AC97_GPIO_POLARITY 0x4e /* GPIO Pin Polarity/Type, 0=low, 1=high active */
59 /* range 0x5a-0x7b - Vendor Specific */
62 /* range 0x60-0x6f (page 1) - extended codec registers */
108 #define AC97_BC_16BIT_DAC 0x0000 /* 16-bit DAC resolution */
109 #define AC97_BC_18BIT_DAC 0x0040 /* 18-bit DAC resolution */
110 #define AC97_BC_20BIT_DAC 0x0080 /* 20-bit DAC resolution */
112 #define AC97_BC_16BIT_ADC 0x0000 /* 16-bit ADC resolution */
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/
Dxilinx.txt10 Each IP-core has a set of parameters which the FPGA designer can use to
20 properties of the device node. In general, device nodes for IP-cores
23 (name): (generic-name)@(base-address) {
24 compatible = "xlnx,(ip-core-name)-(HW_VER)"
27 interrupt-parent = <&interrupt-controller-phandle>;
29 xlnx,(parameter1) = "(string-value)";
30 xlnx,(parameter2) = <(int-value)>;
33 (generic-name): an open firmware-style name that describes the
36 (ip-core-name): the name of the ip block (given after the BEGIN
38 and all underscores '_' converted to dashes '-'.
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/
Dxilinx.txt10 Each IP-core has a set of parameters which the FPGA designer can use to
20 properties of the device node. In general, device nodes for IP-cores
23 (name): (generic-name)@(base-address) {
24 compatible = "xlnx,(ip-core-name)-(HW_VER)"
27 interrupt-parent = <&interrupt-controller-phandle>;
29 xlnx,(parameter1) = "(string-value)";
30 xlnx,(parameter2) = <(int-value)>;
33 (generic-name): an open firmware-style name that describes the
36 (ip-core-name): the name of the ip block (given after the BEGIN
38 and all underscores '_' converted to dashes '-'.
[all …]
/kernel/linux/linux-6.6/drivers/iio/trigger/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
7 menu "Triggers - standalone"
10 tristate "High resolution timer trigger"
13 Provides a frequency based IIO trigger using high resolution
17 module will be called iio-trig-hrtimer.
26 module will be called iio-trig-interrupt.
29 tristate "STM32 Low-Power Timer Trigger"
32 Select this option to enable STM32 Low-Power Timer Trigger.
37 module will be called stm32-lptimer-trigger.
46 module will be called stm32-timer-trigger.
[all …]
/kernel/linux/linux-5.10/drivers/iio/trigger/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
7 menu "Triggers - standalone"
10 tristate "High resolution timer trigger"
13 Provides a frequency based IIO trigger using high resolution
17 module will be called iio-trig-hrtimer.
26 module will be called iio-trig-interrupt.
29 tristate "STM32 Low-Power Timer Trigger"
32 Select this option to enable STM32 Low-Power Timer Trigger.
37 module will be called stm32-lptimer-trigger.
46 module will be called stm32-timer-trigger.
[all …]

12345678910>>...34