linux/include/linux/rmi.h
<<
>>
Prefs
   1/* SPDX-License-Identifier: GPL-2.0-only */
   2/*
   3 * Copyright (c) 2011-2016 Synaptics Incorporated
   4 * Copyright (c) 2011 Unixphere
   5 */
   6
   7#ifndef _RMI_H
   8#define _RMI_H
   9#include <linux/kernel.h>
  10#include <linux/device.h>
  11#include <linux/interrupt.h>
  12#include <linux/input.h>
  13#include <linux/kfifo.h>
  14#include <linux/list.h>
  15#include <linux/module.h>
  16#include <linux/types.h>
  17
  18#define NAME_BUFFER_SIZE 256
  19
  20/**
  21 * struct rmi_2d_axis_alignment - target axis alignment
  22 * @swap_axes: set to TRUE if desired to swap x- and y-axis
  23 * @flip_x: set to TRUE if desired to flip direction on x-axis
  24 * @flip_y: set to TRUE if desired to flip direction on y-axis
  25 * @clip_x_low - reported X coordinates below this setting will be clipped to
  26 *               the specified value
  27 * @clip_x_high - reported X coordinates above this setting will be clipped to
  28 *               the specified value
  29 * @clip_y_low - reported Y coordinates below this setting will be clipped to
  30 *               the specified value
  31 * @clip_y_high - reported Y coordinates above this setting will be clipped to
  32 *               the specified value
  33 * @offset_x - this value will be added to all reported X coordinates
  34 * @offset_y - this value will be added to all reported Y coordinates
  35 * @rel_report_enabled - if set to true, the relative reporting will be
  36 *               automatically enabled for this sensor.
  37 */
  38struct rmi_2d_axis_alignment {
  39        bool swap_axes;
  40        bool flip_x;
  41        bool flip_y;
  42        u16 clip_x_low;
  43        u16 clip_y_low;
  44        u16 clip_x_high;
  45        u16 clip_y_high;
  46        u16 offset_x;
  47        u16 offset_y;
  48        u8 delta_x_threshold;
  49        u8 delta_y_threshold;
  50};
  51
  52/** This is used to override any hints an F11 2D sensor might have provided
  53 * as to what type of sensor it is.
  54 *
  55 * @rmi_f11_sensor_default - do not override, determine from F11_2D_QUERY14 if
  56 * available.
  57 * @rmi_f11_sensor_touchscreen - treat the sensor as a touchscreen (direct
  58 * pointing).
  59 * @rmi_f11_sensor_touchpad - thread the sensor as a touchpad (indirect
  60 * pointing).
  61 */
  62enum rmi_sensor_type {
  63        rmi_sensor_default = 0,
  64        rmi_sensor_touchscreen,
  65        rmi_sensor_touchpad
  66};
  67
  68#define RMI_F11_DISABLE_ABS_REPORT      BIT(0)
  69
  70/**
  71 * struct rmi_2d_sensor_data - overrides defaults for a 2D sensor.
  72 * @axis_align - provides axis alignment overrides (see above).
  73 * @sensor_type - Forces the driver to treat the sensor as an indirect
  74 * pointing device (touchpad) rather than a direct pointing device
  75 * (touchscreen).  This is useful when F11_2D_QUERY14 register is not
  76 * available.
  77 * @disable_report_mask - Force data to not be reported even if it is supported
  78 * by the firware.
  79 * @topbuttonpad - Used with the "5 buttons touchpads" found on the Lenovo 40
  80 * series
  81 * @kernel_tracking - most moderns RMI f11 firmwares implement Multifinger
  82 * Type B protocol. However, there are some corner cases where the user
  83 * triggers some jumps by tapping with two fingers on the touchpad.
  84 * Use this setting and dmax to filter out these jumps.
  85 * Also, when using an old sensor using MF Type A behavior, set to true to
  86 * report an actual MT protocol B.
  87 * @dmax - the maximum distance (in sensor units) the kernel tracking allows two
  88 * distincts fingers to be considered the same.
  89 */
  90struct rmi_2d_sensor_platform_data {
  91        struct rmi_2d_axis_alignment axis_align;
  92        enum rmi_sensor_type sensor_type;
  93        int x_mm;
  94        int y_mm;
  95        int disable_report_mask;
  96        u16 rezero_wait;
  97        bool topbuttonpad;
  98        bool kernel_tracking;
  99        int dmax;
 100        int dribble;
 101        int palm_detect;
 102};
 103
 104/**
 105 * struct rmi_f30_data - overrides defaults for a single F30 GPIOs/LED chip.
 106 * @buttonpad - the touchpad is a buttonpad, so enable only the first actual
 107 * button that is found.
 108 * @trackstick_buttons - Set when the function 30 is handling the physical
 109 * buttons of the trackstick (as a PS/2 passthrough device).
 110 * @disable - the touchpad incorrectly reports F30 and it should be ignored.
 111 * This is a special case which is due to misconfigured firmware.
 112 */
 113struct rmi_f30_data {
 114        bool buttonpad;
 115        bool trackstick_buttons;
 116        bool disable;
 117};
 118
 119
 120/*
 121 * Set the state of a register
 122 *      DEFAULT - use the default value set by the firmware config
 123 *      OFF - explicitly disable the register
 124 *      ON - explicitly enable the register
 125 */
 126enum rmi_reg_state {
 127        RMI_REG_STATE_DEFAULT = 0,
 128        RMI_REG_STATE_OFF = 1,
 129        RMI_REG_STATE_ON = 2
 130};
 131
 132/**
 133 * struct rmi_f01_power_management -When non-zero, these values will be written
 134 * to the touch sensor to override the default firmware settigns.  For a
 135 * detailed explanation of what each field does, see the corresponding
 136 * documention in the RMI4 specification.
 137 *
 138 * @nosleep - specifies whether the device is permitted to sleep or doze (that
 139 * is, enter a temporary low power state) when no fingers are touching the
 140 * sensor.
 141 * @wakeup_threshold - controls the capacitance threshold at which the touch
 142 * sensor will decide to wake up from that low power state.
 143 * @doze_holdoff - controls how long the touch sensor waits after the last
 144 * finger lifts before entering the doze state, in units of 100ms.
 145 * @doze_interval - controls the interval between checks for finger presence
 146 * when the touch sensor is in doze mode, in units of 10ms.
 147 */
 148struct rmi_f01_power_management {
 149        enum rmi_reg_state nosleep;
 150        u8 wakeup_threshold;
 151        u8 doze_holdoff;
 152        u8 doze_interval;
 153};
 154
 155/**
 156 * struct rmi_device_platform_data_spi - provides parameters used in SPI
 157 * communications.  All Synaptics SPI products support a standard SPI
 158 * interface; some also support what is called SPI V2 mode, depending on
 159 * firmware and/or ASIC limitations.  In V2 mode, the touch sensor can
 160 * support shorter delays during certain operations, and these are specified
 161 * separately from the standard mode delays.
 162 *
 163 * @block_delay - for standard SPI transactions consisting of both a read and
 164 * write operation, the delay (in microseconds) between the read and write
 165 * operations.
 166 * @split_read_block_delay_us - for V2 SPI transactions consisting of both a
 167 * read and write operation, the delay (in microseconds) between the read and
 168 * write operations.
 169 * @read_delay_us - the delay between each byte of a read operation in normal
 170 * SPI mode.
 171 * @write_delay_us - the delay between each byte of a write operation in normal
 172 * SPI mode.
 173 * @split_read_byte_delay_us - the delay between each byte of a read operation
 174 * in V2 mode.
 175 * @pre_delay_us - the delay before the start of a SPI transaction.  This is
 176 * typically useful in conjunction with custom chip select assertions (see
 177 * below).
 178 * @post_delay_us - the delay after the completion of an SPI transaction.  This
 179 * is typically useful in conjunction with custom chip select assertions (see
 180 * below).
 181 * @cs_assert - For systems where the SPI subsystem does not control the CS/SSB
 182 * line, or where such control is broken, you can provide a custom routine to
 183 * handle a GPIO as CS/SSB.  This routine will be called at the beginning and
 184 * end of each SPI transaction.  The RMI SPI implementation will wait
 185 * pre_delay_us after this routine returns before starting the SPI transfer;
 186 * and post_delay_us after completion of the SPI transfer(s) before calling it
 187 * with assert==FALSE.
 188 */
 189struct rmi_device_platform_data_spi {
 190        u32 block_delay_us;
 191        u32 split_read_block_delay_us;
 192        u32 read_delay_us;
 193        u32 write_delay_us;
 194        u32 split_read_byte_delay_us;
 195        u32 pre_delay_us;
 196        u32 post_delay_us;
 197        u8 bits_per_word;
 198        u16 mode;
 199
 200        void *cs_assert_data;
 201        int (*cs_assert)(const void *cs_assert_data, const bool assert);
 202};
 203
 204/**
 205 * struct rmi_device_platform_data - system specific configuration info.
 206 *
 207 * @reset_delay_ms - after issuing a reset command to the touch sensor, the
 208 * driver waits a few milliseconds to give the firmware a chance to
 209 * to re-initialize.  You can override the default wait period here.
 210 * @irq: irq associated with the attn gpio line, or negative
 211 */
 212struct rmi_device_platform_data {
 213        int reset_delay_ms;
 214        int irq;
 215
 216        struct rmi_device_platform_data_spi spi_data;
 217
 218        /* function handler pdata */
 219        struct rmi_2d_sensor_platform_data sensor_pdata;
 220        struct rmi_f01_power_management power_management;
 221        struct rmi_f30_data f30_data;
 222};
 223
 224/**
 225 * struct rmi_function_descriptor - RMI function base addresses
 226 *
 227 * @query_base_addr: The RMI Query base address
 228 * @command_base_addr: The RMI Command base address
 229 * @control_base_addr: The RMI Control base address
 230 * @data_base_addr: The RMI Data base address
 231 * @interrupt_source_count: The number of irqs this RMI function needs
 232 * @function_number: The RMI function number
 233 *
 234 * This struct is used when iterating the Page Description Table. The addresses
 235 * are 16-bit values to include the current page address.
 236 *
 237 */
 238struct rmi_function_descriptor {
 239        u16 query_base_addr;
 240        u16 command_base_addr;
 241        u16 control_base_addr;
 242        u16 data_base_addr;
 243        u8 interrupt_source_count;
 244        u8 function_number;
 245        u8 function_version;
 246};
 247
 248struct rmi_device;
 249
 250/**
 251 * struct rmi_transport_dev - represent an RMI transport device
 252 *
 253 * @dev: Pointer to the communication device, e.g. i2c or spi
 254 * @rmi_dev: Pointer to the RMI device
 255 * @proto_name: name of the transport protocol (SPI, i2c, etc)
 256 * @ops: pointer to transport operations implementation
 257 *
 258 * The RMI transport device implements the glue between different communication
 259 * buses such as I2C and SPI.
 260 *
 261 */
 262struct rmi_transport_dev {
 263        struct device *dev;
 264        struct rmi_device *rmi_dev;
 265
 266        const char *proto_name;
 267        const struct rmi_transport_ops *ops;
 268
 269        struct rmi_device_platform_data pdata;
 270
 271        struct input_dev *input;
 272};
 273
 274/**
 275 * struct rmi_transport_ops - defines transport protocol operations.
 276 *
 277 * @write_block: Writing a block of data to the specified address
 278 * @read_block: Read a block of data from the specified address.
 279 */
 280struct rmi_transport_ops {
 281        int (*write_block)(struct rmi_transport_dev *xport, u16 addr,
 282                           const void *buf, size_t len);
 283        int (*read_block)(struct rmi_transport_dev *xport, u16 addr,
 284                          void *buf, size_t len);
 285        int (*reset)(struct rmi_transport_dev *xport, u16 reset_addr);
 286};
 287
 288/**
 289 * struct rmi_driver - driver for an RMI4 sensor on the RMI bus.
 290 *
 291 * @driver: Device driver model driver
 292 * @reset_handler: Called when a reset is detected.
 293 * @clear_irq_bits: Clear the specified bits in the current interrupt mask.
 294 * @set_irq_bist: Set the specified bits in the current interrupt mask.
 295 * @store_productid: Callback for cache product id from function 01
 296 * @data: Private data pointer
 297 *
 298 */
 299struct rmi_driver {
 300        struct device_driver driver;
 301
 302        int (*reset_handler)(struct rmi_device *rmi_dev);
 303        int (*clear_irq_bits)(struct rmi_device *rmi_dev, unsigned long *mask);
 304        int (*set_irq_bits)(struct rmi_device *rmi_dev, unsigned long *mask);
 305        int (*store_productid)(struct rmi_device *rmi_dev);
 306        int (*set_input_params)(struct rmi_device *rmi_dev,
 307                        struct input_dev *input);
 308        void *data;
 309};
 310
 311/**
 312 * struct rmi_device - represents an RMI4 sensor device on the RMI bus.
 313 *
 314 * @dev: The device created for the RMI bus
 315 * @number: Unique number for the device on the bus.
 316 * @driver: Pointer to associated driver
 317 * @xport: Pointer to the transport interface
 318 *
 319 */
 320struct rmi_device {
 321        struct device dev;
 322        int number;
 323
 324        struct rmi_driver *driver;
 325        struct rmi_transport_dev *xport;
 326
 327};
 328
 329struct rmi4_attn_data {
 330        unsigned long irq_status;
 331        size_t size;
 332        void *data;
 333};
 334
 335struct rmi_driver_data {
 336        struct list_head function_list;
 337
 338        struct rmi_device *rmi_dev;
 339
 340        struct rmi_function *f01_container;
 341        struct rmi_function *f34_container;
 342        bool bootloader_mode;
 343
 344        int num_of_irq_regs;
 345        int irq_count;
 346        void *irq_memory;
 347        unsigned long *irq_status;
 348        unsigned long *fn_irq_bits;
 349        unsigned long *current_irq_mask;
 350        unsigned long *new_irq_mask;
 351        struct mutex irq_mutex;
 352        struct input_dev *input;
 353
 354        struct irq_domain *irqdomain;
 355
 356        u8 pdt_props;
 357
 358        u8 num_rx_electrodes;
 359        u8 num_tx_electrodes;
 360
 361        bool enabled;
 362        struct mutex enabled_mutex;
 363
 364        struct rmi4_attn_data attn_data;
 365        DECLARE_KFIFO(attn_fifo, struct rmi4_attn_data, 16);
 366};
 367
 368int rmi_register_transport_device(struct rmi_transport_dev *xport);
 369void rmi_unregister_transport_device(struct rmi_transport_dev *xport);
 370
 371void rmi_set_attn_data(struct rmi_device *rmi_dev, unsigned long irq_status,
 372                       void *data, size_t size);
 373
 374int rmi_driver_suspend(struct rmi_device *rmi_dev, bool enable_wake);
 375int rmi_driver_resume(struct rmi_device *rmi_dev, bool clear_wake);
 376#endif
 377