Home
last modified time | relevance | path

Searched full:rmi4 (Results 1 – 25 of 48) sorted by relevance

12

/linux/drivers/input/rmi4/
H A DKconfig3 # RMI4 configuration
6 tristate "Synaptics RMI4 bus support"
9 Say Y here if you want to support the Synaptics RMI4 bus. This is
10 required for all RMI4 device support.
17 tristate "RMI4 I2C Support"
20 Say Y here if you want to support RMI4 devices connected to an I2C
26 tristate "RMI4 SPI Support"
29 Say Y here if you want to support RMI4 devices connected to a SPI
35 tristate "RMI4 SMB Support"
38 Say Y here if you want to support RMI4 devices connected to an SMB
[all …]
H A Drmi_bus.h21 * struct rmi_function - represents the implementation of an RMI4
22 * function for a particular device (basically, a driver for that RMI4 function)
113 * rmi_reset - reset a RMI4 device
/linux/Documentation/devicetree/bindings/input/
H A Dsyna,rmi4.yaml4 $id: http://devicetree.org/schemas/input/syna,rmi4.yaml#
7 title: Synaptics RMI4 compliant devices
15 The Synaptics RMI4 (Register Mapped Interface 4) core is able to support RMI4
22 - syna,rmi4-i2c
23 - syna,rmi4-spi
55 rmi4-f01@1:
92 rmi4-f1a@1a:
97 RMI4 Function 1A is for capacitive keys.
111 "^rmi4-f1[12]@1[12]$":
116 RMI4 Function 11 and Function 12 are for 2D touch position sensing.
[all …]
/linux/arch/arm/boot/dts/qcom/
H A Dqcom-msm8926-microsoft-superman-lte.dts27 compatible = "syna,rmi4-i2c";
40 rmi4-f01@1 {
45 rmi4-f11@11 {
H A Dqcom-msm8926-microsoft-tesla.dts30 compatible = "syna,rmi4-i2c";
43 rmi4-f01@1 {
48 rmi4-f12@12 {
H A Dqcom-msm8974pro-oneplus-bacon.dts97 rmi4-i2c-dev@20 {
98 compatible = "syna,rmi4-i2c";
113 rmi4-f01@1 {
118 rmi4-f12@12 {
H A Dqcom-msm8226-microsoft-common.dtsi121 compatible = "syna,rmi4-i2c";
134 rmi4-f01@1 {
139 rmi4-f11@11 {
H A Dqcom-msm8926-htc-memul.dts167 compatible = "syna,rmi4-i2c";
178 rmi4-f01@1 {
183 rmi4-f12@12 {
H A Dqcom-apq8026-huawei-sturgeon.dts98 compatible = "syna,rmi4-i2c";
113 rmi4-f01@1 {
118 rmi4-f12@12 {
H A Dqcom-apq8026-lg-lenok.dts103 compatible = "syna,rmi4-i2c";
116 rmi4-f01@1 {
121 rmi4-f12@12 {
H A Dqcom-msm8974pro-sony-xperia-shinano-common.dtsi107 compatible = "syna,rmi4-i2c";
124 rmi4-f01@1 {
129 rmi4-f11@11 {
H A Dqcom-msm8974-sony-xperia-rhine.dtsi90 compatible = "syna,rmi4-i2c";
106 rmi4-f01@1 {
111 rmi4-f11@11 {
/linux/arch/arm64/boot/dts/freescale/
H A Dimx8mq-zii-ultra-rmb3.dts110 compatible = "syna,rmi4-i2c";
120 rmi4-f01@1 {
125 rmi4-f11@11 {
134 rmi4-f12@12 {
/linux/arch/arm64/boot/dts/qcom/
H A Dmsm8916-motorola-common.dtsi50 compatible = "syna,rmi4-i2c";
59 rmi4-f01@1 {
64 rmi4-f11@11 {
H A Dmsm8916-huawei-g7.dts168 rmi4@70 {
169 compatible = "syna,rmi4-i2c";
185 rmi4-f01@1 {
190 rmi4-f11@11 {
H A Dmsm8916-longcheer-l8150.dts226 rmi4@20 {
227 compatible = "syna,rmi4-i2c";
243 rmi4-f01@1 {
248 rmi4-f12@12 {
H A Dmsm8994-sony-xperia-kitakami.dtsi113 touchscreen: rmi4-i2c-dev@2c {
114 compatible = "syna,rmi4-i2c";
131 rmi4-f01@1 {
136 rmi4-f11@11 {
H A Dmsm8953-xiaomi-vince.dts135 compatible = "syna,rmi4-i2c";
150 rmi4-f01@1 {
155 rmi4-f12@12 {
H A Dmsm8998-xiaomi-sagit.dts183 compatible = "syna,rmi4-i2c";
201 rmi4-f01@1 {
206 rmi4-f12@12 {
214 rmi4-f1a@1a {
H A Dsdm630-sony-xperia-nile.dtsi166 touchscreen: synaptics-rmi4-i2c@70 {
167 compatible = "syna,rmi4-i2c";
179 rmi4-f01@1 {
184 rmi4-f11@11 {
H A Dmsm8998-oneplus-common.dtsi172 compatible = "syna,rmi4-i2c";
189 rmi4-f01@1 {
194 rmi4_f12: rmi4-f12@12 {
/linux/arch/arm/boot/dts/st/
H A Dste-href-tvk1281618-r2.dtsi189 /* Synaptics RMI4 TM1217 touchscreen */
190 compatible = "syna,rmi4-i2c";
201 rmi4-f01@1 {
205 rmi4-f11@11 {
/linux/include/linux/
H A Drmi.h137 * documention in the RMI4 specification.
290 * struct rmi_driver - driver for an RMI4 sensor on the RMI bus.
313 * struct rmi_device - represents an RMI4 sensor device on the RMI bus.
/linux/drivers/input/
H A DMakefile32 obj-$(CONFIG_RMI4_CORE) += rmi4/
/linux/arch/arm/boot/dts/samsung/
H A Dexynos5422-samsung-k3g.dts575 compatible = "syna,rmi4-i2c";
589 rmi4-f01@1 {
594 rmi4-f12@12 {

12