Home
last modified time | relevance | path

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

12

/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 …]
/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 …]
Dhideep.txt4 - compatible : must be "hideep,hideep-ts"
5 - reg : I2C slave address, (e.g. 0x6C).
6 - interrupts : Interrupt to which the chip is connected.
9 - vdd-supply : It is the controller supply for controlling
11 - vid-supply : It is the controller supply for controlling
13 - reset-gpios : Define for reset gpio pin.
15 - touchscreen-size-x : X axis size of touchscreen
16 - touchscreen-size-y : Y axis size of touchscreen
17 - linux,keycodes : Specifies an array of numeric keycode values to
23 #include "dt-bindings/input/input.h"
[all …]
Dimx6ul_tsc.txt4 - compatible: must be "fsl,imx6ul-tsc".
5 - reg: this touch controller address and the ADC2 address.
6 - interrupts: the interrupt of this touch controller and ADC2.
7 - clocks: the root clock of touch controller and ADC2.
8 - clock-names; must be "tsc" and "adc".
9 - xnur-gpio: the X- gpio this controller connect to.
10 This xnur-gpio returns to low once the finger leave the touch screen (The
14 - measure-delay-time: the value of measure delay time.
15 Before X-axis or Y-axis measurement, the screen need some time before
18 - pre-charge-time: the touch screen need some time to precharge.
[all …]
Dbrcm,iproc-touchscreen.txt4 - compatible: must be "brcm,iproc-touchscreen"
5 - ts_syscon: handler of syscon node defining physical base
9 - clocks: The clock provided by the SOC to driver the tsc
10 - clock-names: name for the clock
11 - interrupts: The touchscreen controller's interrupt
12 - address-cells: Specify the number of u32 entries needed in child nodes.
14 - size-cells: Specify number of u32 entries needed to specify child nodes size
18 - scanning_period: Time between scans. Each step is 1024 us. Valid 1-256.
19 - debounce_timeout: Each step is 512 us. Valid 0-255
20 - settling_timeout: The settling duration (in ms) is the amount of time
[all …]
Dad7879.txt1 * Analog Devices AD7879(-1)/AD7889(-1) touchscreen interface (SPI/I2C)
4 - compatible : for SPI slave, use "adi,ad7879"
5 for I2C slave, use "adi,ad7879-1"
6 - reg : SPI chipselect/I2C slave address
7 See spi-bus.txt for more SPI slave properties
8 - interrupts : touch controller interrupt
9 - touchscreen-max-pressure : maximum reported pressure
10 - adi,resistance-plate-x : total resistance of X-plate (for pressure
13 - touchscreen-swapped-x-y : X and Y axis are swapped (boolean)
14 - adi,first-conversion-delay : 0-12: In 128us steps (starting with 128us)
[all …]
/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 …]
Datarikbd.rst12 provides a convenient connection point for a mouse and switch-type joysticks.
13 The ikbd processor also maintains a time-of-day clock with one second
18 The ikbd communicates with the main processor over a high speed bi-directional
41 0xF8-0xFB relative mouse position records (lsbs determined by
43 0xFC time-of-day
67 ---------------------------
71 button being pressed or released, or motion in either axis exceeding a
75 significantly more than the threshold delta x or y. This may happen since no
85 ; and x is the left button state
86 X ; delta x as twos complement integer
[all …]
/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 …]
/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 …]
Dinput-programming.rst34 return -EBUSY;
40 error = -ENOMEM;
44 button_dev->evbit[0] = BIT_MASK(EV_KEY);
45 button_dev->keybit[BIT_WORD(BTN_0)] = BIT_MASK(BTN_0);
83 parts of the input systems what it is - what events can be generated or
123 for for example mouse movement, where you don't want the X and Y values
126 dev->open() and dev->close()
140 return -EBUSY;
154 button_dev->open = button_open;
155 button_dev->close = button_close;
[all …]
/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 …]
/Documentation/devicetree/bindings/input/rmi4/
Drmi_2d_sensor.txt12 http://www.synaptics.com/sites/default/files/511-000136-01-Rev-E-RMI4-Interfacing-Guide.pdf
16 - touchscreen-inverted-x
17 - touchscreen-inverted-y
18 - touchscreen-swapped-x-y
19 - touchscreen-x-mm
20 - touchscreen-y-mm
23 - syna,clip-x-low: Sets a minimum value for X.
24 - syna,clip-y-low: Sets a minimum value for Y.
25 - syna,clip-x-high: Sets a maximum value for X.
26 - syna,clip-y-high: Sets a maximum value for Y.
[all …]
/Documentation/devicetree/bindings/input/
Delan_i2c.txt4 - compatible: must be "elan,ekth3000".
5 - reg: I2C address of the chip.
6 - interrupts: interrupt to which the chip is connected (see interrupt
10 - wakeup-source: touchpad can be used as a wakeup source.
11 - pinctrl-names: should be "default" (see pinctrl binding [1]).
12 - pinctrl-0: a phandle pointing to the pin settings for the device (see
14 - vcc-supply: a phandle for the regulator supplying 3.3V power.
15 - elan,trackpoint: touchpad can support a trackpoint (boolean)
16 - elan,clickpad: touchpad is a clickpad (the entire surface is a button)
17 - elan,middle-button: touchpad has a physical middle button
[all …]
/Documentation/driver-api/iio/
Dbuffers.rst13 :file:`/dev/iio:device{X}` character device node, thus reducing the CPU load.
18 :file:`/sys/bus/iio/iio:device{X}/buffer/*`. Here are some of the existing
31 :file:`/sys/bus/iio/iio:device{X}/scan_elements/*` directory. This file contains
50 For example, a driver for a 3-axis accelerometer with 12 bit resolution where
51 data is stored in two 8-bits registers as follows::
54 +---+---+---+---+---+---+---+---+
55 |D3 |D2 |D1 |D0 | X | X | X | X | (LOW byte, address 0x06)
56 +---+---+---+---+---+---+---+---+
59 +---+---+---+---+---+---+---+---+
61 +---+---+---+---+---+---+---+---+
[all …]
/Documentation/devicetree/bindings/media/
Dvideo-interfaces.txt4 ---------------
21 #address-cells = <1>;
22 #size-cells = <0>;
37 a common scheme using '#address-cells', '#size-cells' and 'reg' properties is
41 specify #address-cells, #size-cells properties independently for the 'port'
44 Two 'endpoint' nodes are linked with each other through their 'remote-endpoint'
53 a device is partitioned into multiple data busses, e.g. 16-bit input port
54 divided into two separate ITU-R BT.656 8-bit busses. In such case bus-width
55 and data-shift properties can be used to assign physical data lines to each
59 --------------------------------
[all …]
/Documentation/misc-devices/
Dlis3lv02d.rst12 - Yan Burman <burman.yan@gmail.com>
13 - Eric Piel <eric.piel@tremplin-utc.net>
17 -----------
23 their axis automatically oriented on standard way (eg: you can directly play
31 - 3D position that the accelerometer reports. Format: "(x,y,z)"
33 - read reports the sampling rate of the accelerometer device in HZ.
37 - performs selftest for the chip as specified by chip manufacturer.
40 the laptop to act as a pinball machine-esque joystick. Joystick device can be
42 By default output values are scaled between -32768 .. 32767. In joystick raw
54 Seltest returns either "OK x y z" or "FAIL x y z" where x, y and z are
[all …]
/Documentation/fb/
Dmodedb.rst9 - one routine to probe for video modes, which can be used by all frame buffer
11 - one generic video mode database with a fair amount of standard videomodes
13 - the possibility to supply your own mode database for graphics hardware that
14 needs non-standard modes, like amifb and Mac frame buffer drivers (which
23 <xres>x<yres>[M][R][-<bpp>][@<refresh>][i][m][eDd]
24 <name>[-<bpp>][@<refresh>]
37 Sample usage: 1024x768M@60m - CVT timing with margins
44 signals (e.g. HDMI and DVI-I). For other outputs it behaves like 'e'. If 'd'
50 video=VGA-1:1280x1024@60me
54 video=LVDS-1:d video=HDMI-1:D
[all …]
/Documentation/hid/
Dhid-sensor.rst26 Logical Minimum(-32767)
35 The report is indicating "sensor page (0x20)" contains an accelerometer-3D (0x73).
36 This accelerometer-3D has some fields. Here for example field 2 is motion intensity
37 (0x045f) with a logical minimum value of -32767 and logical maximum of 32767. The
47 for different sensors. For example an accelerometer can send X,Y and Z data, whereas
51 - Core hid driver
52 - Individual sensor processing part (sensor drivers)
55 -----------
56 The core driver registers (hid-sensor-hub) registers as a HID driver. It parses
58 with name HID-SENSOR-xxxx (where xxxx is usage id from the specification).
[all …]
/Documentation/ABI/testing/
Dsysfs-bus-iio3 Contact: linux-iio@vger.kernel.org
6 Corresponds to a grouping of sensor channels. X is the IIO
11 Contact: linux-iio@vger.kernel.org
21 X is the IIO index of the trigger.
25 Contact: linux-iio@vger.kernel.org
31 Contact: linux-iio@vger.kernel.org
33 Description of the physical chip / device for device X.
38 Contact: linux-iio@vger.kernel.org
41 buffered samples and events for device X.
48 Contact: linux-iio@vger.kernel.org
[all …]

12