| /openbmc/linux/Documentation/timers/ |
| H A 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
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 …]
|
| H A D | highres.rst | 2 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 …]
|
| /openbmc/linux/Documentation/fb/ |
| H A D | viafb.modes | 10 # 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 …]
|
| /openbmc/linux/lib/fonts/ |
| H A D | Kconfig | 1 # 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 …]
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | ds1621.rst | 47 - 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 …]
|
| H A D | adm9240.rst | 10 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 …]
|
| H A D | w83793.rst | 10 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 …]
|
| H A D | tmp513.rst | 1 .. SPDX-License-Identifier: GPL-2.0
22 Eric Tremblay <etremblay@distech-controls.com>
25 -----------
28 The TMP512 (dual-channel) and TMP513 (triple-channel) are system monitors
29 that include remote sensors, a local temperature sensor, and a high-side current
31 temperatures, on-chip temperatures, and system voltage/power/current
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.
44 **temp[1-4]_input**
46 **temp[1-4]_crit**
[all …]
|
| H A D | max31827.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 Addresses scanned: I2C 0x40 - 0x5f
20 Addresses scanned: I2C 0x40 - 0x5f
28 Addresses scanned: I2C 0x40 - 0x5f
34 - Daniel Matyas <daniel.matyas@analog.com>
37 -----------
40 between them is found in the default power-on behaviour of the chips. While the
42 4. Besides this, the MAX31829's alarm active state is high, while the other two
52 hysteresis value: -40 and -30 degrees for under temperature alarm and +100 and
69 The conversions can be manual with the one-shot functionality and automatic with
[all …]
|
| /openbmc/bmcweb/redfish-core/include/registries/ |
| H A D | openbmc.json | 14 "Resolution": "None.", string
18 "Description": "Indicates At-Scale Debug connection has been established",
19 "Message": "At-Scale Debug service is now connected %1",
23 "Resolution": "None.", string
27 "Description": "Indicates At-Scale Debug connection aborted/failed",
28 "Message": "At-Scale Debug connection aborted/failed",
31 "Resolution": "None.", string
35 "Description": "Indicates At-Scale Debug connection has ended",
36 "Message": "At-Scale Debug service is now disconnected",
39 "Resolution": "None.", string
[all …]
|
| /openbmc/u-boot/drivers/video/rockchip/ |
| H A D | Kconfig | 8 # Author: Eric Gao <eric.gao@rock-chips.com>
15 Rockchip SoCs provide video output capabilities for High-Definition
16 Multimedia Interface (HDMI), Low-voltage Differential Signalling
19 This driver supports the on-chip video output device, and targets the
23 int "Maximum horizontal resolution (for memory allocation purposes)"
27 The maximum horizontal resolution to support for the framebuffer.
29 framebuffer during device-model binding/probing.
32 int "Maximum vertical resolution (for memory allocation purposes)"
36 The maximum vertical resolution to support for the framebuffer.
38 framebuffer during device-model binding/probing.
[all …]
|
| /openbmc/linux/Documentation/input/ |
| H A D | event-codes.rst | 1 .. _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 …]
|
| /openbmc/linux/Documentation/w1/slaves/ |
| H A D | w1_therm.rst | 16 -----------
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 …]
|
| /openbmc/linux/Documentation/devicetree/bindings/iio/proximity/ |
| H A D | semtech,sx9324.yaml | 1 # 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 …]
|
| /openbmc/linux/include/sound/ac97/ |
| H A D | regs.h | 1 /* 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 …]
|
| /openbmc/openpower-hw-diags/test/ |
| H A D | test-resolution.cpp | 4 #include <analyzer/resolution.hpp>
24 TEST(Resolution, TestSet1) in TEST() argument
30 proc_str, callout::Priority::HIGH, false); in TEST()
46 l1->push(c1); in TEST()
47 l1->push(c2); in TEST()
48 l1->push(c5); in TEST()
52 l2->push(c4); in TEST()
53 l2->push(c3); in TEST()
54 l2->push(l1); in TEST()
65 l1->resolve(sd1); in TEST()
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/ |
| H A D | xilinx.txt | 10 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 …]
|
| /openbmc/u-boot/drivers/video/ |
| H A D | videomodes.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */
14 #define FB_SYNC_HOR_HIGH_ACT 1 /* horizontal sync high active */
15 #define FB_SYNC_VERT_HIGH_ACT 2 /* vertical sync high active */
17 #define FB_SYNC_COMP_HIGH_ACT 8 /* composite sync high active */
33 * Resolution Struct
36 int xres; /* visible resolution */
57 int resindex; /* index to resolution struct */
|
| /openbmc/linux/drivers/iio/trigger/ |
| H A D | Kconfig | 1 # 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 …]
|
| /openbmc/linux/drivers/clocksource/ |
| H A D | scx200_hrt.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
6 * high-resolution timer. The Geode SC-1100 (at least) has a buggy
8 * given as a boot-arg. In its absence, the Generic Timekeeping code
9 * will detect and de-rate the bad TSC, allowing this timer to take
12 * Based on work by John Stultz, and Ted Phelps (in a 2.6.12-rc6 patch)
29 MODULE_PARM_DESC(ppm, "+-adjust to actual XO freq (ppm)");
37 #define HR_TM27MPD (1 << 2) /* 1 turns off input clock (power-down) */
62 return -ENODEV; in init_hrt_clocksource()
64 /* Reserve the timer's ISA io-region for ourselves */ in init_hrt_clocksource()
67 "NatSemi SCx200 High-Resolution Timer")) { in init_hrt_clocksource()
[all …]
|
| /openbmc/u-boot/board/google/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0+
15 i5 Ivybridge which is a die-shrink of Sandybridge, with 4GB of
20 and it provides a 2560x1700 high resolution touch-enabled LCD
24 bool "Chromebook link 64-bit"
27 U-Boot is built as a 64-bit binary. This allows testing while this
52 Chrome OS EC connected on LPC, and it provides a 2560x1700 high
53 resolution touch-enabled LCD display.
|
| /openbmc/linux/Documentation/devicetree/bindings/display/bridge/ |
| H A D | ti,dlpc3433.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jagan Teki <jagan@amarulasolutions.com>
11 - Christopher Vollo <chris@renewoutreach.org>
15 for processing high resolution DMD based projectors.
21 It supports upto 720p resolution with 60 and 120 Hz refresh
30 - 0x1b
31 - 0x1d
33 enable-gpios:
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-driver-w1_therm | 5 (RW) read or write TH and TL (Temperature High an Low) alarms.
7 (typical -55 degC to 125 degC), if not values will be trimmed
11 master level, refer to Documentation/w1/w1-generic.rst for
41 * '-xx': xx is kernel error when reading power status
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
55 values after power-on. Read or write are :
57 * '9..14': device resolution in bit
58 or resolution to set in bit
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/leds/ |
| H A D | leds-lm3697.txt | 1 * Texas Instruments - LM3697 Highly Efficient White LED Driver
3 The LM3697 11-bit LED driver provides high-
10 - compatible:
12 - reg : I2C slave address
13 - #address-cells : 1
14 - #size-cells : 0
17 - enable-gpios : GPIO pin to enable/disable the device
18 - vled-supply : LED supply
21 - reg : 0 - LED is Controlled by bank A
22 1 - LED is Controlled by bank B
[all …]
|
| /openbmc/u-boot/doc/device-tree-bindings/video/ |
| H A D | displaymode.txt | 4 (from http://lists.freedesktop.org/archives/dri-devel/2012-July/024875.html)
7 - xres, yres: Display resolution
8 - left-margin, right-margin, hsync-len: Horizontal Display timing
10 - upper-margin, lower-margin, vsync-len: Vertical display timing
12 - clock: display clock in Hz
15 - width-mm, height-mm: Display dimensions in mm
16 - hsync-active-high (bool): Hsync pulse is active high
17 - vsync-active-high (bool): Vsync pulse is active high
18 - interlaced (bool): This is an interlaced mode
19 - doublescan (bool): This is a doublescan mode
[all …]
|