| /Linux-v5.15/drivers/iio/adc/ |
| D | qcom-vadc-common.c | 395 bool absolute, in qcom_vadc_scale_calib() argument
401 if (absolute) in qcom_vadc_scale_calib()
410 bool absolute, u16 adc_code, in qcom_vadc_scale_volt() argument
415 qcom_vadc_scale_calib(calib_graph, adc_code, absolute, &voltage); in qcom_vadc_scale_volt()
426 bool absolute, u16 adc_code, in qcom_vadc_scale_therm() argument
432 qcom_vadc_scale_calib(calib_graph, adc_code, absolute, &voltage); in qcom_vadc_scale_therm()
434 if (absolute) in qcom_vadc_scale_therm()
448 bool absolute, in qcom_vadc_scale_die_temp() argument
454 qcom_vadc_scale_calib(calib_graph, adc_code, absolute, &voltage); in qcom_vadc_scale_die_temp()
471 bool absolute, in qcom_vadc_scale_chg_temp() argument
[all …]
|
| /Linux-v5.15/fs/jfs/ |
| D | jfs_metapage.h | 52 int absolute, unsigned long new);
54 #define read_metapage(inode, lblock, size, absolute)\ argument
55 __get_metapage(inode, lblock, size, absolute, false)
57 #define get_metapage(inode, lblock, size, absolute)\ argument
58 __get_metapage(inode, lblock, size, absolute, true)
|
| /Linux-v5.15/Documentation/input/devices/ |
| D | elantech.rst | 21 4.3 Native absolute mode 4 byte packet format
24 5.2 Native absolute mode 6 byte packet format
30 6.2 Native absolute mode 6 byte packet format
35 7.2 Native absolute mode 6 byte packet format
82 in relative mode and not in absolute mode. As the Linux Elantech touchpad
83 driver always puts the hardware into absolute mode not all information
188 A: 1 = absolute mode (needs 4 byte packets, see reg_11)
297 Native absolute mode 4 byte packet format
345 x9..x0 = absolute x value (horizontal)
352 y9..y0 = absolute y value (vertical)
[all …]
|
| /Linux-v5.15/tools/scripts/ |
| D | utilities.mak | 131 # is-absolute
133 # Usage: bool-value = $(call is-absolute,path)
135 is-absolute = $(shell echo $(shell-sq) | grep -q ^/ && echo y)
139 # Usage: absolute-executable-path-or-empty = $(call lookup,path)
160 # Usage: absolute-executable-path-or-empty = $(call get-executable,path)
162 # The goal is to get an absolute path for an executable;
168 get-executable = $(if $(1),$(if $(is-absolute),$(_ge-abspath),$(lookup)))
173 # Usage: absolute-executable-path-or-empty = $(call get-executable-or-default,variable,default)
|
| /Linux-v5.15/Documentation/devicetree/bindings/input/touchscreen/ |
| D | tsc2007.txt | 15 - ti,fuzzx: specifies the absolute input fuzz x value.
18 - ti,fuzzy: specifies the absolute input fuzz y value.
19 - ti,fuzzz: specifies the absolute input fuzz z value.
|
| D | brcm,iproc-touchscreen.txt | 55 - touchscreen-fuzz-x: horizontal noise value of the absolute input
57 - touchscreen-fuzz-y: vertical noise value of the absolute input
|
| /Linux-v5.15/arch/xtensa/kernel/ |
| D | mxhead.S | 30 .begin no-absolute-literals
62 .end no-absolute-literals
|
| /Linux-v5.15/drivers/scsi/ |
| D | zorro7xx.c | 41 int absolute; /* offset is absolute address */ member
43 { .name = "PowerUP 603e+", .offset = 0xf40000, .absolute = 1 },
86 if (zdd->absolute) { in zorro7xx_init_one()
|
| D | script_asm.pl | 185 @absolute = (); # Array of absolute names
411 push (@absolute , $id);
794 @absolute = sort @absolute;
796 foreach $i (@absolute) {
918 foreach $i (@absolute) {
|
| /Linux-v5.15/arch/xtensa/boot/boot-elf/ |
| D | bootstrap.S | 29 .begin no-absolute-literals
77 .end no-absolute-literals
|
| /Linux-v5.15/Documentation/devicetree/bindings/input/ |
| D | rotary-encoder.txt | 10 encoder. Only relevant for absolute axis. Defaults to 24 which is a
13 absolute one. Relative axis will only generate +1/-1 events on the input
16 greater than the specified steps or smaller than 0. For absolute axis only.
|
| /Linux-v5.15/Documentation/devicetree/bindings/opp/ |
| D | ti-omap5-opp-supply.txt | 36 - ti,absolute-max-voltage-uv: absolute maximum voltage for the OPP supply.
62 ti,absolute-max-voltage-uv = <1500000>;
|
| /Linux-v5.15/drivers/misc/lis3lv02d/ |
| D | Kconfig | 15 This driver also provides an absolute input class device, allowing
31 This driver also provides an absolute input class device, allowing
|
| /Linux-v5.15/drivers/of/unittest-data/ |
| D | overlay_0.dts | 6 /* overlay_0 - enable using absolute target path */
|
| D | overlay_1.dts | 6 /* overlay_1 - disable using absolute target path */
|
| D | overlay_12.dts | 6 /* overlay_12 - enable using absolute target path (i2c) */
|
| D | overlay_13.dts | 6 /* overlay_13 - disable using absolute target path (i2c) */
|
| /Linux-v5.15/tools/memory-model/scripts/ |
| D | README | 34 with the absolute pathnames of the tests to run provided one
64 Run the litmus tests whose absolute pathnames are provided one
|
| /Linux-v5.15/Documentation/parisc/ |
| D | debugging.rst | 13 absolute addresses are used instead of virtual addresses as in the
14 rest of the kernel. To translate an absolute address to a virtual
|
| /Linux-v5.15/Documentation/i2c/muxes/ |
| D | i2c-mux-gpio.rst | 69 If you don't know the absolute GPIO pin numbers at registration time,
84 assign a dynamic ID to your device. If you do not know the absolute
|
| /Linux-v5.15/Documentation/vm/ |
| D | overcommit-accounting.rst | 37 or ``vm.overcommit_kbytes`` (absolute value).
45 The C language stack growth does an implicit mremap. If you want absolute
|
| /Linux-v5.15/Documentation/userspace-api/media/dvb/ |
| D | dvb-frontend-parameters.rst | 33 uint32_t frequency; /* (absolute) frequency in Hz for QAM/OFDM */
48 frontends the ``frequency`` specifies the absolute frequency and is
|
| /Linux-v5.15/Documentation/timers/ |
| D | hrtimers.rst | 38 the required readjusting of absolute CLOCK_REALTIME timers at
105 absolute timers based on a low-resolution CLOCK_REALTIME. The existing
106 implementation needed to keep an extra list of all armed absolute
111 expiry time in absolute time units removes all this complex and poorly
125 Basic data types: every time value, absolute or relative, is in a
|
| /Linux-v5.15/Documentation/sphinx/ |
| D | automarkup.py | 237 absolute = match.group(1)
239 if absolute:
|
| /Linux-v5.15/Documentation/input/ |
| D | event-codes.rst | 51 - Used to describe absolute axis value changes, e.g. describing the
184 move to the left by a certain number of units, but its absolute position in
185 space is unknown. If the absolute position is known, EV_ABS codes should be used
217 EV_ABS events describe absolute changes in a property. For example, a touchpad
329 devices require non-trivial transformation, such as absolute to relative
386 Directional axes on this device (absolute and/or relative x, y, z) represent
388 can report through the rotational axes (absolute and/or relative rx, ry, rz).
424 Trackpads that provide absolute touch position must report ABS_{X,Y} for the
|
