Home
last modified time | relevance | path

Searched +full:x +full:- +full:axis (Results 1 – 25 of 215) sorted by relevance

123456789

/kernel/linux/linux-5.10/drivers/input/touchscreen/
Dof_touchscreen.c1 // SPDX-License-Identifier: GPL-2.0-only
33 unsigned long axis, in touchscreen_set_params() argument
38 if (!test_bit(axis, dev->absbit)) { in touchscreen_set_params()
39 dev_warn(&dev->dev, in touchscreen_set_params()
40 "DT specifies parameters but the axis %lu is not set up\n", in touchscreen_set_params()
41 axis); in touchscreen_set_params()
45 absinfo = &dev->absinfo[axis]; in touchscreen_set_params()
46 absinfo->minimum = min; in touchscreen_set_params()
47 absinfo->maximum = max; in touchscreen_set_params()
48 absinfo->fuzz = fuzz; in touchscreen_set_params()
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/accel/
Dlis302.txt8 - compatible: should be set to "st,lis3lv02d-spi"
9 - reg: the chipselect index
10 - spi-max-frequency: maximal bus speed, should be set to 1000000 unless
12 - interrupts: the interrupt generated by the device
15 - compatible: should be set to "st,lis3lv02d"
16 - reg: i2c slave address
17 - Vdd-supply: The input supply for Vdd
18 - Vdd_IO-supply: The input supply for Vdd_IO
23 - st,click-single-{x,y,z}: if present, tells the device to issue an
25 x/y/z axis.
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/
Dmount-matrix.txt2 * is the definition of +/- values practical or counterintuitive?
13 that produce three-dimensional data in relation to the world where it is
21 of the (x,y,z) triplets, such as different registers to read these coordinates,
28 reference to (x,y,z) orientation, with (x,y) corresponding to these axes on the
29 screen and (z) being depth, the axis perpendicular to the screen.
31 For a screen you probably want (x) coordinates to go from negative on the left
37 reference. This means that the sensor may be flipped upside-down, left-right,
47 Device-to-world examples for some three-dimensional sensor types:
49 - Accelerometers have their world frame of reference toward the center of
50 gravity, usually to the core of the planet. A reading of the (x,y,z) values
[all …]
/kernel/linux/linux-5.10/drivers/input/misc/
Dadxl34x.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * ADXL345/346 Three-Axis Digital Accelerometers
25 #define OFSX 0x1E /* R/W X-axis offset */
26 #define OFSY 0x1F /* R/W Y-axis offset */
27 #define OFSZ 0x20 /* R/W Z-axis offset */
34 #define ACT_INACT_CTL 0x27 /* R/W Axis enable control for activity and */
36 #define THRESH_FF 0x28 /* R/W Free-fall threshold */
37 #define TIME_FF 0x29 /* R/W Free-fall time */
38 #define TAP_AXES 0x2A /* R/W Axis control for tap/double tap */
46 #define DATAX0 0x32 /* R X-Axis Data 0 */
[all …]
/kernel/linux/linux-5.10/Documentation/input/joydev/
Djoystick-api.rst1 .. _joystick-api:
7 :Author: Ragnar Hojland Espinosa <ragnar@macula.net> - 7 Aug 1998
18 driver now reports only any changes of its state. See joystick-api.txt,
23 For backward compatibility the old (v0.x) interface is still included.
57 __u8 number; /* axis/button number */
65 -------------
86 ---------------
88 The values of ``number`` correspond to the axis or button that
90 is, you have both an axis 0 and a button 0). Generally,
93 Axis number
[all …]
Djoystick.rst3 .. _joystick-doc:
14 linux-input@vger.kernel.org
16 send "subscribe linux-input" to majordomo@vger.kernel.org to subscribe to it.
25 ---------
29 usually packaged as ``joystick``, ``input-utils``, ``evtest``, and so on.
35 ------------
48 ln -s input/js0 js0
49 ln -s input/js1 js1
50 ln -s input/js2 js2
51 ln -s input/js3 js3
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/input/touchscreen/
Dchipone_icn8318.txt4 - compatible : "chipone,icn8318"
5 - reg : I2C slave address of the chip (0x40)
6 - interrupts : interrupt specification for the icn8318 interrupt
7 - wake-gpios : GPIO specification for the WAKE input
8 - touchscreen-size-x : horizontal resolution of touchscreen (in pixels)
9 - touchscreen-size-y : vertical resolution of touchscreen (in pixels)
12 - pinctrl-names : should be "default"
13 - pinctrl-0: : a phandle pointing to the pin settings for the
15 - touchscreen-fuzz-x : horizontal noise value of the absolute input
17 - touchscreen-fuzz-y : vertical noise value of the absolute input
[all …]
Dbu21013.txt4 - compatible : "rohm,bu21013_tp"
5 - reg : I2C device address
6 - reset-gpios : GPIO pin enabling (selecting) chip (CS)
7 - interrupt-parent : the phandle for the gpio controller
8 - interrupts : (gpio) interrupt to which the chip is connected
11 - touch-gpios : GPIO pin registering a touch event
12 - <supply_name>-supply : Phandle to a regulator supply
13 - touchscreen-size-x : General touchscreen binding, see [1].
14 - touchscreen-size-y : General touchscreen binding, see [1].
15 - touchscreen-inverted-x : General touchscreen binding, see [1].
[all …]
Dtouchscreen.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Dmitry Torokhov <dmitry.torokhov@gmail.com>
13 touchscreen-min-x:
14 description: minimum x coordinate reported
18 touchscreen-min-y:
23 touchscreen-size-x:
24 description: horizontal resolution of touchscreen (maximum x coordinate reported + 1)
27 touchscreen-size-y:
[all …]
Dads7846.txt7 Documentation/devicetree/bindings/spi/spi-bus.txt
23 vcc-supply A regulator node for the supply voltage.
28 ti,vref-delay-usecs vref supply delay in usecs, 0 for
30 ti,vref-mv The VREF voltage, in millivolts (u16).
33 ti,keep-vref-on set to keep vref on for differential
35 ti,settle-delay-usec Settling time of the analog signals;
37 on the X/Y drivers. If set to non-zero,
41 ti,penirq-recheck-delay-usecs If set to non-zero, after samples are
47 ti,x-plate-ohms Resistance of the X-plate,
49 ti,y-plate-ohms Resistance of the Y-plate,
[all …]
/kernel/linux/linux-5.10/Documentation/input/devices/
Dcma3000_d0x.rst1 CMA3000-D0x Accelerometer
5 * VTI CMA3000-D0x
8 CMA3000-D0X Product Family Specification 8281000A.02.pdf
15 -----------
17 CMA3000 Tri-axis accelerometer supports Motion detect, Measurement and
25 This mode is used to read the acceleration data on X,Y,Z
26 axis and supports 400, 100, 40 Hz sample frequency.
47 -------------
50 Noise on X Axis
53 Noise on Y Axis
[all …]
Diforce-protocol.rst7 Home page at `<http://web.archive.org/web/*/http://www.esil.univ-mrs.fr>`_
16 specify force effects to I-Force 2.0 devices. None of this information comes
25 send data to your I-Force device based on what you read in this document.
30 All values are hexadecimal with big-endian encoding (msb on the left). Beware,
31 values inside packets are encoded using little-endian. Bytes whose roles are
35 ------------------------
60 axis::
64 00 X-Axis lsb
65 01 X-Axis msb
66 02 Y-Axis lsb, or gas pedal for a wheel
[all …]
/kernel/linux/linux-5.10/Documentation/input/
Dmulti-touch-protocol.rst4 Multi-touch (MT) Protocol
7 :Copyright: |copy| 2009-2010 Henrik Rydberg <rydberg@euromail.se>
11 ------------
13 In order to utilize the full power of the new multi-touch and multi-user
16 document describes the multi-touch (MT) protocol which allows kernel
30 --------------
34 packet. Since these events are ignored by current single-touch (ST)
48 All drivers mark the end of a multi-touch transfer by calling the usual
67 the ABS_MT_TRACKING_ID of the associated slot. A non-negative tracking id
68 is interpreted as a contact, and the value -1 denotes an unused slot. A
[all …]
/kernel/linux/linux-5.10/drivers/iio/imu/
Dadis16400.c1 // SPDX-License-Identifier: GPL-2.0-only
38 #define ADIS16400_XGYRO_OUT 0x04 /* X-axis gyroscope output */
39 #define ADIS16400_YGYRO_OUT 0x06 /* Y-axis gyroscope output */
40 #define ADIS16400_ZGYRO_OUT 0x08 /* Z-axis gyroscope output */
41 #define ADIS16400_XACCL_OUT 0x0A /* X-axis accelerometer output */
42 #define ADIS16400_YACCL_OUT 0x0C /* Y-axis accelerometer output */
43 #define ADIS16400_ZACCL_OUT 0x0E /* Z-axis accelerometer output */
44 #define ADIS16400_XMAGN_OUT 0x10 /* X-axis magnetometer measurement */
45 #define ADIS16400_YMAGN_OUT 0x12 /* Y-axis magnetometer measurement */
46 #define ADIS16400_ZMAGN_OUT 0x14 /* Z-axis magnetometer measurement */
[all …]
/kernel/linux/linux-5.10/drivers/hid/
Dhid-lg3ff.c1 // SPDX-License-Identifier: GPL-2.0-or-later
15 #include "hid-lg.h"
21 * 0 - seems to be command field
22 * 1 - 30 deal with the x axis
23 * 31 -60 deal with the y axis
25 * Field 1 is x axis constant force
26 * Field 31 is y axis constant force
28 * other interesting fields 1,2,3,4 on x axis
29 * (same for 31,32,33,34 on y axis)
36 * -127 0 -127 -127 makes the joystick loose on the left,
[all …]
/kernel/linux/linux-5.10/include/linux/
Dlis3lv02d.h1 /* SPDX-License-Identifier: GPL-2.0 */
6 * struct lis3lv02d_platform_data - lis3 chip family platform data
8 * @click_thresh_x: Click detection unit x axis threshold
9 * @click_thresh_y: Click detection unit y axis threshold
10 * @click_thresh_z: Click detection unit z axis threshold
26 * @axis_x: Sensor orientation remapping for x-axis
27 * @axis_y: Sensor orientation remapping for y-axis
28 * @axis_z: Sensor orientation remapping for z-axis
111 #define LIS3_INV_DEV_X -1
112 #define LIS3_INV_DEV_Y -2
[all …]
Dfb.h1 /* SPDX-License-Identifier: GPL-2.0 */
72 __u32 serial; /* Serial Number - Integer */
79 __u16 input; /* display type - see FB_DISP_* */
80 __u16 dpms; /* DPMS support - see FB_DPMS_ */
81 __u16 signal; /* Signal Type - see FB_SIGNAL_* */
84 __u16 gamma; /* Gamma - in fractions of 100 */
86 __u16 misc; /* Misc flags - see FB_MISC_* */
131 /* only used by mach-pxa/am200epd.c */
145 u32 x; member
193 u32 blit_x; /* supported bit block dimensions (1-32)*/
[all …]
/kernel/linux/linux-5.10/include/linux/input/
Dmt.h1 /* SPDX-License-Identifier: GPL-2.0-only */
18 #define INPUT_MT_TRACK 0x0008 /* use in-kernel tracking */
19 #define INPUT_MT_SEMI_MT 0x0010 /* semi-mt device, finger count handled manually */
22 * struct input_mt_slot - represents the state of an input MT slot
28 int abs[ABS_MT_LAST - ABS_MT_FIRST + 1];
34 * struct input_mt - state of tracked contacts
40 * @red: reduced cost matrix for in-kernel tracking
56 slot->abs[code - ABS_MT_FIRST] = value; in input_mt_set_value()
62 return slot->abs[code - ABS_MT_FIRST]; in input_mt_get_value()
73 return slot->frame == mt->frame; in input_mt_is_used()
[all …]
Dadxl34x.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
20 * X,Y,Z Axis Offset:
30 * TAP_X/Y/Z Enable: Setting TAP_X, Y, or Z Enable enables X,
32 * selected axis from participation in Tap detection.
89 * X/Y/Z Enable: A '1' enables X, Y, or Z participation in activity
90 * or inactivity detection. A '0' excludes the selected axis from
152 * result in the function appearing un-responsive if the
162 * holds the threshold value for Free-Fall detection.
163 * The data format is unsigned. The root-sum-square(RSS) value
167 * result in undesirable behavior if Free-Fall interrupt is
[all …]
Dkxtj9.h1 /* SPDX-License-Identifier: GPL-2.0-only */
13 unsigned int min_interval; /* minimum poll interval (in milli-seconds) */
14 unsigned int init_interval; /* initial poll interval (in milli-seconds) */
17 * By default, x is axis 0, y is axis 1, z is axis 2; these can be
25 * Each axis can be negated to account for sensor orientation within
32 /* CTRL_REG1: set resolution, g-range, data ready enable */
33 /* Output resolution: 8-bit valid or 12-bit valid */
37 /* Output g-range: +/-2g, 4g, or 8g */
/kernel/linux/linux-5.10/sound/pci/
Dazt3328.h1 /* SPDX-License-Identifier: GPL-2.0 */
5 /* "PU" == "power-up value", as tested on PCI168 PCI rev. 10
85 …REQ_SUSPECTED_66200 0x06 | SOUNDFORMAT_XTAL2 /* 66200 (13240 * 5); 64000 may have been nicer :-\ */
111 #define IDX_IO_TIMER_VALUE 0x60 /* found this timer area by pure luck :-) */
122 /* some IRQ bit in here might also be used to signal a power-management timer
150 * in case playback is active? Or is this driver-induced?
175 * still lets us evaluate button states, but not axis states */
179 * --> FIFO/timing settings???) */
186 #define IDX_IO_6CH 0x6C /* unknown; fully read-writable */
209 * axis measurement bits enabled
[all …]
/kernel/linux/linux-5.10/drivers/staging/iio/accel/
Dadis16240.c1 // SPDX-License-Identifier: GPL-2.0+
32 /* Output, x-axis accelerometer */
35 /* Output, y-axis accelerometer */
38 /* Output, z-axis accelerometer */
47 /* Output, x-axis acceleration peak */
50 /* Output, y-axis acceleration peak */
53 /* Output, z-axis acceleration peak */
56 /* Output, sum-of-squares acceleration peak */
59 /* Output, Capture Buffer 1, X and Y acceleration */
74 /* Calibration, x-axis acceleration offset adjustment */
[all …]
/kernel/linux/linux-5.10/drivers/platform/x86/
Dhdaps.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * hdaps.c - driver for IBM's Hard Drive Active Protection System
9 * starting with the R40, T41, and X40. It provides a basic two-axis
31 #define HDAPS_NR_PORTS 0x30 /* number of ports: 0x1600 - 0x162f */
34 #define HDAPS_PORT_YPOS 0x1612 /* y-axis position */
35 #define HDAPS_PORT_XPOS 0x1614 /* x-axis position */
37 #define HDAPS_PORT_YVAR 0x1617 /* y-axis variance (what is this?) */
38 #define HDAPS_PORT_XVAR 0x1619 /* x-axis variance (what is this?) */
71 * __get_latch - Get the value from a given port. Callers must hold hdaps_mtx.
79 * __check_latch - Check a port latch for a given value. Returns zero if the
[all …]
/kernel/linux/linux-5.10/drivers/misc/lis3lv02d/
Dlis3lv02d.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * lis3lv02d.c - ST LIS3LV02DL accelerometer driver
5 * Copyright (C) 2007-2008 Yan Burman
7 * Copyright (C) 2008-2009 Pavel Machek
42 #define SELFTEST_FAIL -1
43 #define SELFTEST_IRQ -2
51 * to keep the interrupt for the free-fall event. The values are updated at
61 * LIS3LV02D spec says 1024 LSBs corresponds 1 G -> 1LSB is 1000/1024 mG
67 /* Sensitivity values for -2G +2G scale */
72 * LIS331DLH spec says 1LSBs corresponds 4G/4096 -> 1LSB is 1000/1024 mG.
[all …]
/kernel/linux/linux-5.10/drivers/staging/media/atomisp/pci/isp/kernels/tnr/tnr3/
Dia_css_tnr3_types.h1 /* SPDX-License-Identifier: GPL-2.0 */
4 Copyright (c) 2010 - 2015, Intel Corporation.
20 * CSS-API header file for Temporal Noise Reduction v3 (TNR3) kernel
33 * each. Each line graph has Luma values on the x axis and sigma values for
34 * each plane on the y axis. The three linear segments may have a different
37 * specified each on the Luma axis and the per plane Sigma axis. On the Luma
38 * axis two points are fixed (namely 0 and maximum luma value - depending on
41 * the per plane sigma axis are also specified at the interface.
53 unsigned int knee_y[TNR3_NUM_SEGMENTS - 1]; /** Knee points */

123456789