Home
last modified time | relevance | path

Searched full:int2 (Results 1 – 20 of 20) sorted by relevance

/Documentation/devicetree/bindings/iio/imu/
Dbosch,bmi160.yaml34 - INT2
37 to "INT2" if INT2 pin should be used instead
96 interrupt-names = "INT2";
Dnxp,fxos8700.yaml34 - INT2
79 interrupt-names = "INT2";
Dbosch,bmi323.yaml38 - INT2
Dst,lsm6dsx.yaml62 Supports up to 2 interrupt lines via the INT1 and INT2 pins.
/Documentation/devicetree/bindings/iio/accel/
Dbosch,bma255.yaml51 the one connected to the INT2 pin (if available). The type should be
55 always treated as INT2.
63 - INT2
106 interrupt-names = "INT2";
Dfsl,mma7455.yaml34 to INT1 and second (where present) to INT2.
40 - INT2
64 interrupt-names = "INT2", "INT1";
Dfsl,mma8452.yaml38 - INT2
62 interrupt-names = "INT2";
Dbosch,bmi088.yaml43 - INT2
68 interrupt-names = "INT2";
Dkionix,kx022a.yaml35 - enum: [INT1, INT2]
36 - const: INT2
Dnxp,fxls8962af.yaml36 - INT2
Dadi,adxl355.yaml39 - INT2
Dadi,adxl313.yaml47 - INT2
/Documentation/devicetree/bindings/iio/gyroscope/
Dnxp,fxas21002c.yaml44 - INT2
96 interrupt-names = "INT2";
Dbosch,bmg160.yaml33 If two interrupts are provided, expected order is INT1 and INT2.
/Documentation/devicetree/bindings/interrupt-controller/
Dloongson,liointc.yaml120 <0x00000000>, /* int2 */
/Documentation/devicetree/bindings/net/
Dfsl,fec.yaml89 - const: int2
93 - const: int2
/Documentation/
Ddontdiff147 int2.c
/Documentation/arch/m68k/
Dbuddha-driver.rst103 The IDE ports issue an INT2. You can read the level of the
107 determine what driver has to serve the INT2. Buddha and
/Documentation/devicetree/bindings/iio/
Dst,st-sensors.yaml101 Inertial interrupt lines INT1 and INT2 if these exist. This means up to
/Documentation/devicetree/bindings/pinctrl/
Dmarvell,armada-xp-pinctrl.txt52 mpp31 31 gpio, tdm(int2), sd0(cmd)