Andrew Scull | b4b6d4a | 2019-01-02 15:54:55 +0000 | [diff] [blame^] | 1 | # |
| 2 | # RMI4 configuration |
| 3 | # |
| 4 | config RMI4_CORE |
| 5 | tristate "Synaptics RMI4 bus support" |
| 6 | select IRQ_DOMAIN |
| 7 | help |
| 8 | Say Y here if you want to support the Synaptics RMI4 bus. This is |
| 9 | required for all RMI4 device support. |
| 10 | |
| 11 | If unsure, say Y. |
| 12 | |
| 13 | if RMI4_CORE |
| 14 | |
| 15 | config RMI4_I2C |
| 16 | tristate "RMI4 I2C Support" |
| 17 | depends on I2C |
| 18 | help |
| 19 | Say Y here if you want to support RMI4 devices connected to an I2C |
| 20 | bus. |
| 21 | |
| 22 | If unsure, say Y. |
| 23 | |
| 24 | config RMI4_SPI |
| 25 | tristate "RMI4 SPI Support" |
| 26 | depends on SPI |
| 27 | help |
| 28 | Say Y here if you want to support RMI4 devices connected to a SPI |
| 29 | bus. |
| 30 | |
| 31 | If unsure, say N. |
| 32 | |
| 33 | config RMI4_SMB |
| 34 | tristate "RMI4 SMB Support" |
| 35 | depends on I2C |
| 36 | help |
| 37 | Say Y here if you want to support RMI4 devices connected to an SMB |
| 38 | bus. |
| 39 | |
| 40 | If unsure, say N. |
| 41 | |
| 42 | To compile this driver as a module, choose M here: the module will be |
| 43 | called rmi_smbus. |
| 44 | |
| 45 | config RMI4_F03 |
| 46 | bool "RMI4 Function 03 (PS2 Guest)" |
| 47 | depends on RMI4_CORE |
| 48 | help |
| 49 | Say Y here if you want to add support for RMI4 function 03. |
| 50 | |
| 51 | Function 03 provides PS2 guest support for RMI4 devices. This |
| 52 | includes support for TrackPoints on TouchPads. |
| 53 | |
| 54 | config RMI4_F03_SERIO |
| 55 | tristate |
| 56 | depends on RMI4_CORE |
| 57 | depends on RMI4_F03 |
| 58 | default RMI4_CORE |
| 59 | select SERIO |
| 60 | |
| 61 | config RMI4_2D_SENSOR |
| 62 | bool |
| 63 | |
| 64 | config RMI4_F11 |
| 65 | bool "RMI4 Function 11 (2D pointing)" |
| 66 | select RMI4_2D_SENSOR |
| 67 | help |
| 68 | Say Y here if you want to add support for RMI4 function 11. |
| 69 | |
| 70 | Function 11 provides 2D multifinger pointing for touchscreens and |
| 71 | touchpads. For sensors that support relative pointing, F11 also |
| 72 | provides mouse input. |
| 73 | |
| 74 | config RMI4_F12 |
| 75 | bool "RMI4 Function 12 (2D pointing)" |
| 76 | select RMI4_2D_SENSOR |
| 77 | help |
| 78 | Say Y here if you want to add support for RMI4 function 12. |
| 79 | |
| 80 | Function 12 provides 2D multifinger pointing for touchscreens and |
| 81 | touchpads. For sensors that support relative pointing, F12 also |
| 82 | provides mouse input. |
| 83 | |
| 84 | config RMI4_F30 |
| 85 | bool "RMI4 Function 30 (GPIO LED)" |
| 86 | help |
| 87 | Say Y here if you want to add support for RMI4 function 30. |
| 88 | |
| 89 | Function 30 provides GPIO and LED support for RMI4 devices. This |
| 90 | includes support for buttons on TouchPads and ClickPads. |
| 91 | |
| 92 | config RMI4_F34 |
| 93 | bool "RMI4 Function 34 (Device reflash)" |
| 94 | select FW_LOADER |
| 95 | help |
| 96 | Say Y here if you want to add support for RMI4 function 34. |
| 97 | |
| 98 | Function 34 provides support for upgrading the firmware on the RMI4 |
| 99 | device via the firmware loader interface. This is triggered using a |
| 100 | sysfs attribute. |
| 101 | |
| 102 | config RMI4_F54 |
| 103 | bool "RMI4 Function 54 (Analog diagnostics)" |
| 104 | depends on VIDEO_V4L2=y || (RMI4_CORE=m && VIDEO_V4L2=m) |
| 105 | select VIDEOBUF2_VMALLOC |
| 106 | select RMI4_F55 |
| 107 | help |
| 108 | Say Y here if you want to add support for RMI4 function 54 |
| 109 | |
| 110 | Function 54 provides access to various diagnostic features in certain |
| 111 | RMI4 touch sensors. |
| 112 | |
| 113 | config RMI4_F55 |
| 114 | bool "RMI4 Function 55 (Sensor tuning)" |
| 115 | help |
| 116 | Say Y here if you want to add support for RMI4 function 55 |
| 117 | |
| 118 | Function 55 provides access to the RMI4 touch sensor tuning |
| 119 | mechanism. |
| 120 | |
| 121 | endif # RMI_CORE |