[lkml]   [2011]   [Dec]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Subject[RFC PATCH 00/11] input: Synaptics RMI4 Touchscreen Driver
    This patch implements a driver supporting Synaptics ClearPad and other
    touchscreen sensors that use the RMI4 protocol, as defined here:

    as well as successor documents that haven't made their way through to
    publication yet.

    This code represents a complete refactoring and rewrite of the previously
    submitted patches, and supersedes all those patches. We believe that all
    outstanding issues arising from the previous submissions have been addressed.
    However, because of the quantity of new code, we are submitting this patch
    as an RFC and requesting feedback from the kernel community.

    This patch is against the v2.6.38 tag of Linus' kernel tree, commit

    Included in this patch are:
    - full support for an RMI virtual bus as a standard kernel bus

    - physical layer implementations for I2C and SPI

    - function implementations for the following RMI4 functions:
    * F01 device control
    * F09 self test (aka BIST)
    * F11 multifinger pointing
    * F19 capacitive buttons
    * F34 device reflash
    * F54 analog data reporting

    - character device access to the RMI4 register map via rmidev

    - deletion of more legacy code and behavior

    The driver supports a system having one or more RMI sensors attached to it.
    Most devices have just a single touch sensor, but some have more than one.
    An example is the Fuse concept phone, which has 4 RMI sensors in it.

    Each sensor is presented as a device on the RMI logical bus (/sys/bus/rmi).
    Devices are named/numbered in the order they are discovered on the bus,
    starting with /sys/bus/rmi/devices/sensor00 for the first once, .../sensor01
    for the second one, and so on.

    Individual RMI functions are presented as child devices of the sensor device.
    For example, sensor00/fn01, sensor00/fn11, and so on. Control of an RMI
    function's operating parameters is implemented via sysfs.

    For diagnostic purposes, the rmidev interface is provided. This implements
    a character device (/dev/rmi0, and so on) that provides flat file access to
    the RMI4 register map. For more information, see the file

    Due to the large amount of code, we've broken this patch into 11 parts, as
    01 - header files and documenation
    02 - core sensor and bus implementation
    03 - physical layer drivers
    04 - Kconfigs and Makefiles
    05 - rmidev
    06..11 - drivers for individual RMI functions

    Comments and other feedback on this driver are welcomed.

    Christopher Heiny and the Synaptics RMI4 driver team

    Signed-off-by: Christopher Heiny <>

    Cc: Jean Delvare <>
    Cc: Linus Walleij <>
    Cc: Naveen Kumar Gaddipati <>
    Cc: Joeri de Gram <>


     \ /
      Last update: 2011-12-22 03:23    [W:0.029 / U:12.492 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site