Home
last modified time | relevance | path

Searched full:matrix (Results 1 – 25 of 223) sorted by relevance

123456789

/Documentation/devicetree/bindings/mfd/
Datmel-matrix.txt1 * Device tree bindings for Atmel Bus Matrix
3 The Bus Matrix registers are used to configure Atmel SoCs internal bus
8 "atmel,at91sam9260-matrix", "syscon"
9 "atmel,at91sam9261-matrix", "syscon"
10 "atmel,at91sam9263-matrix", "syscon"
11 "atmel,at91sam9rl-matrix", "syscon"
12 "atmel,at91sam9g45-matrix", "syscon"
13 "atmel,at91sam9n12-matrix", "syscon"
14 "atmel,at91sam9x5-matrix", "syscon"
15 "atmel,sama5d3-matrix", "syscon"
[all …]
Dtc3589x.txt50 - keypad,num-rows : number of rows in the matrix, see
51 bindings/input/matrix-keymap.txt
52 - keypad,num-columns : number of columns in the matrix, see
53 bindings/input/matrix-keymap.txt
55 bindings/input/matrix-keymap.txt
/Documentation/devicetree/bindings/input/
Dgpio-matrix-keypad.txt1 * GPIO driven matrix keypad device tree bindings
3 GPIO driven matrix keypad is used to interface a SoC with a matrix keypad.
4 The matrix keypad supports multiple row and column lines, a key can be
5 placed at each intersection of a unique row and a unique column. The matrix
10 - compatible: Should be "gpio-matrix-keypad"
18 bindings/input/matrix-keymap.txt
31 matrix-keypad {
32 compatible = "gpio-matrix-keypad";
Dnvidia,tegra20-kbc.txt2 The key controller has maximum 24 pins to make matrix keypad. Any pin
15 devicetree/bindings/input/matrix-keymap.txt.
24 matrix-keyboard bindings:
27 matrix-keyboard-controller spec but to be used when the KEY_FN modifier
Dtca8418_keypad.txt1 This binding is based on the matrix-keymap binding with the following
10 - linux,keymap: Keys definitions, see keypad-matrix.
Dmatrix-keymap.yaml4 $id: http://devicetree.org/schemas/input/matrix-keymap.yaml#
7 title: Common Key Matrices on Matrix-connected Key Boards
13 A simple common binding for matrix-connected key boards. Currently targeted at
Dclps711x-keypad.txt1 * Cirrus Logic CLPS711X matrix keypad device tree bindings
8 bindings/input/matrix-keymap.txt.
Dcirrus,ep9307-keypad.yaml13 - $ref: /schemas/input/matrix-keymap.yaml#
16 The KPP is designed to interface with a keypad matrix with 2-point contact
18 of scanning a keypad matrix. The KPP is capable of detecting, debouncing,
Dimx-keypad.yaml13 - $ref: /schemas/input/matrix-keymap.yaml#
16 The KPP is designed to interface with a keypad matrix with 2-point contact
18 of scanning a keypad matrix. The KPP is capable of detecting, debouncing,
Dqcom,pm8921-keypad.yaml14 - $ref: matrix-keymap.yaml#
48 matrix array
53 matrix array.
Domap-keypad.txt3 TI's Keypad controller is used to interface a SoC with a matrix-type
9 This binding is based on the matrix-keymap binding with the following
Dtwl4030-keypad.txt3 TWL4030's Keypad controller is used to interface a SoC with a matrix-type
9 This binding is based on the matrix-keymap binding with the following
Dgoogle,cros-ec-keyb.yaml15 Google's ChromeOS EC Keyboard is a simple matrix keyboard
31 Enable a ghost filter for the matrix keyboard. This is recommended
40 An ordered u32 array describing the rows/columns (in the scan matrix)
60 $ref: /schemas/input/matrix-keymap.yaml#
136 /* No matrix keyboard, just buttons/switches */
Dpxa27x-keypad.txt10 interval for matrix key. The value is in binary number of 2ms
12 Optional Properties For Matrix Keyes
13 Please refer to matrix-keymap.txt
/Documentation/ABI/testing/
Dsysfs-bus-iio-mpu60507 This is mounting matrix for motion sensors. Mounting matrix
8 is a 3x3 unitary matrix. A typical mounting matrix would look like
11 positions relative to the board that holds these sensors. Identity matrix
/Documentation/userspace-api/media/v4l/
Dext-ctrls-detect.rst39 ``V4L2_CID_DETECT_MD_THRESHOLD_GRID`` matrix control.
46 ``V4L2_CID_DETECT_MD_REGION_GRID`` matrix control.
54 ``V4L2_CID_DETECT_MD_THRESHOLD_GRID (__u16 matrix)``
57 detection mode. Matrix element (0, 0) represents the cell at the
60 ``V4L2_CID_DETECT_MD_REGION_GRID (__u8 matrix)``
63 detection mode. Matrix element (0, 0) represents the cell at the
/Documentation/devicetree/bindings/iio/
Dmount-matrix.txt5 * should we have HOWTO engineer a correct matrix for a new device (without comparing to a different…
10 Mounting matrix
12 The mounting matrix is a device tree property used to orient any device
16 The purpose of the mounting matrix is to translate the sensor frame of
17 reference into the device frame of reference using a translation matrix as
43 to this world. When using the mounting matrix, the sensor and device orientation
154 To achieve this, use the device tree property "mount-matrix" for the sensor.
156 This supplies a 3x3 rotation matrix in the strict linear algebraic sense,
159 multiplied by this matrix to give the proper vectors values in three-dimensional
165 The mounting matrix has the layout:
[all …]
/Documentation/devicetree/bindings/iio/accel/
Dkionix,kxcjk1013.yaml31 mount-matrix:
32 description: an optional 3x3 mounting rotation matrix.
49 mount-matrix = "0", "1", "0",
Dkionix,kxsd9.yaml29 mount-matrix:
30 description: an optional 3x3 mounting rotation matrix.
54 mount-matrix = "-0.984807753012208", "0", "-0.173648177666930",
/Documentation/arch/s390/
Dvfio-ap.rst150 be received (DQAP instruction). The validity of an APQN is defined by the matrix
190 1. AP matrix device
202 domains, and control domains comprising the matrix for a KVM guest.
205 by a KVM guest's SIE state description to grant the guest access to a matrix
222 | +----------------> Device core +----------> matrix device |
240 | admin | | VFIO device core |---------> matrix |
252 2. The vfio-ap driver during its initialization will register a single 'matrix'
254 all vfio_ap mediated devices used to configure an AP matrix for a guest.
255 3. The /sys/devices/vfio_ap/matrix device is created by the device core
302 | | device | | | vfio_ap.ko |<-> matrix
[all …]
/Documentation/RCU/Design/Memory-Ordering/
DTreeRCU-dyntick.svg48 transform="matrix(-0.2,0,0,-0.2,-1.2,0)"
104 transform="matrix(-1.1,0,0,-1.1,-1.1,0)"
118 transform="matrix(-0.4,0,0,-0.4,-4,0)"
147 transform="matrix(-0.2,0,0,-0.2,-1.2,0)" />
161 transform="matrix(-0.2,0,0,-0.2,-1.2,0)" />
175 transform="matrix(-0.2,0,0,-0.2,-1.2,0)" />
188 transform="matrix(-1.1,0,0,-1.1,-1.1,0)"
202 transform="matrix(-1.1,0,0,-1.1,-1.1,0)"
216 transform="matrix(-1.1,0,0,-1.1,-1.1,0)"
230 transform="matrix(-1.1,0,0,-1.1,-1.1,0)"
[all …]
DTreeRCU-hotplug.svg48 transform="matrix(-0.2,0,0,-0.2,-1.2,0)"
104 transform="matrix(-1.1,0,0,-1.1,-1.1,0)"
118 transform="matrix(-0.4,0,0,-0.4,-4,0)"
147 transform="matrix(-0.2,0,0,-0.2,-1.2,0)" />
161 transform="matrix(-0.2,0,0,-0.2,-1.2,0)" />
175 transform="matrix(-0.2,0,0,-0.2,-1.2,0)" />
188 transform="matrix(-1.1,0,0,-1.1,-1.1,0)"
202 transform="matrix(-1.1,0,0,-1.1,-1.1,0)"
216 transform="matrix(-1.1,0,0,-1.1,-1.1,0)"
230 transform="matrix(-1.1,0,0,-1.1,-1.1,0)"
[all …]
/Documentation/devicetree/bindings/perf/
Driscv,pmu.yaml38 $ref: /schemas/types.yaml#/definitions/uint32-matrix
43 The mapping is encoded in an matrix format where each element represents
55 $ref: /schemas/types.yaml#/definitions/uint32-matrix
59 of events. The information is encoded in an matrix format where each
69 $ref: /schemas/types.yaml#/definitions/uint32-matrix
75 encoded in a matrix format where each element represents the specific raw
/Documentation/devicetree/bindings/iio/imu/
Dbosch,bmi160.yaml50 mount-matrix:
51 description: an optional 3x3 mounting rotation matrix
78 mount-matrix = "0", "1", "0",
/Documentation/devicetree/bindings/iio/magnetometer/
Dasahi-kasei,ak8975.yaml56 mount-matrix:
57 description: an optional 3x3 mounting rotation matrix.
86 mount-matrix = "-0.984807753012208", /* x0 */

123456789