11 Oct, 2011

1 commit


10 Oct, 2011

3 commits


07 Oct, 2011

5 commits

  • CONFIG_PM is defined when CONFIG_PM_SLEEP or CONFIG_PM_RUNTIME is defined,
    however suspend and resume methods are only valid in the context of
    CONFIG_PM_SLEEP. If only CONFIG_PM_RUNTIME is defined we get the following
    warning (courtesy of Geerts randconfig builds):

    lm8323.c: warning: 'lm8323_resume' defined but not used

    Signed-off-by: Dmitry Torokhov

    Dmitry Torokhov
     
  • CONFIG_PM is defined when CONFIG_PM_SLEEP or CONFIG_PM_RUNTIME is defined,
    however suspend and resume methods are only valid in the context of
    CONFIG_PM_SLEEP. If only CONFIG_PM_RUNTIME is defined we get the following
    warning (courtesy of Geerts randconfig builds):

    ad7879-i2c.c: warning: 'ad7879_i2c_resume' defined but not used

    Signed-off-by: Dmitry Torokhov

    Dmitry Torokhov
     
  • CONFIG_PM is defined when CONFIG_PM_SLEEP or CONFIG_PM_RUNTIME is defined,
    however suspend and resume methods are only valid in context of
    CONFIG_PM_SLEEP. If only CONFIG_PM_RUNTIME is defined we get the following
    warning (courtesy of Geerts randconfig builds):

    synaptics_i2c.c: warning: 'synaptics_i2c_resume' defined but not used

    Signed-off-by: Dmitry Torokhov

    Dmitry Torokhov
     
  • Sometimes GCC is not smart enough to recognize that x, y and z are
    always used properly initialized in mma8450_poll(). Let's rearrange
    the code a bit to help GCC.

    Signed-off-by: Dmitry Torokhov

    Dmitry Torokhov
     
  • Sysfs attribute show methods are always passed a buffer of length
    PAGE_SIZE. To keep from overwriting this buffer and causing havoc, use
    snprintf() to guarantee we never write more than the buffer can hold.

    In addition, at least for my touchscreen, the number and size of objects
    was far too big to fit in a single 4K page. Therefore, this patch also
    trims some redundant framing text to leave more room for actual data.

    Signed-off-by: Daniel Kurtz
    Acked-by: Nick Dyer
    Signed-off-by: Dmitry Torokhov

    Daniel Kurtz
     

05 Oct, 2011

4 commits


29 Sep, 2011

1 commit


21 Sep, 2011

10 commits


10 Sep, 2011

11 commits

  • v4 hardware is a true multitouch capable touchpad (up to 5 fingers).
    The packet format is quite complex, please see protocol document for
    reference.

    Signed-off-by: JJ Ding
    Signed-off-by: Dmitry Torokhov

    JJ Ding
     
  • v3 hardware's packet format is almost identical to v2 (one/three finger touch),
    except when sensing two finger touch, the hardware sends 12 bytes of data.

    Signed-off-by: JJ Ding
    Acked-by: Daniel Kurtz
    Acked-by: Éric Piel
    Signed-off-by: Dmitry Torokhov

    JJ Ding
     
  • Group property setting code into elantech_set_properties.

    Signed-off-by: JJ Ding
    Acked-by: Daniel Kurtz
    Acked-by: Éric Piel
    Signed-off-by: Dmitry Torokhov

    JJ Ding
     
  • For v2 hardware, there is no real parity check, but we can still check
    some constant bits for data integrity.

    Also rename elantech_check_parity_v1 to elantech_packet_check_v1 to make
    these packet checking function names consistent.

    Signed-off-by: JJ Ding
    Acked-by: Daniel Kurtz
    Acked-by: Éric Piel
    Signed-off-by: Dmitry Torokhov

    JJ Ding
     
  • Don't try to be too clever and remove ETP_EDGE_FUZZ_V2. X, Y ranges
    should be just the raw resolution of the device. Otherwise, they can
    cause underflow on the Y axis.

    Suggested-by: Éric Piel
    Signed-off-by: JJ Ding
    Acked-by: Daniel Kurtz
    Acked-by: Éric Piel
    Signed-off-by: Dmitry Torokhov

    JJ Ding
     
  • With newer hardware, the touchpad provides range info.
    Let's use it.

    Signed-off-by: JJ Ding
    Acked-by: Daniel Kurtz
    Acked-by: Éric Piel
    Signed-off-by: Dmitry Torokhov

    JJ Ding
     
  • For two finger touches the coordinate of each finger gets reported
    separately but with reduced resolution.

    With this change, we now have the same range for ST and MT data and
    scale MT data because it has lower resolution to match ST.

    Suggested-by: Dmitry Torokhov
    Signed-off-by: JJ Ding
    Acked-by: Daniel Kurtz
    Acked-by: Éric Piel
    Signed-off-by: Dmitry Torokhov

    JJ Ding
     
  • x, y values are actually 12-bit long. Also update protocol document to
    reflect the change.

    Signed-off-by: JJ Ding
    Acked-by: Daniel Kurtz
    Acked-by: Éric Piel
    Signed-off-by: Dmitry Torokhov

    JJ Ding
     
  • Fix warning from Geert's build summary emails by changing "if" to
    "ifdef". Thsi should fix the following:

    drivers/input/misc/twl6040-vibra.c:231:5: warning: "CONFIG_PM_SLEEP" is not defined

    Builds cleanly with CONFIG_PM_SLEEP enabled or disabled.

    Signed-off-by: Randy Dunlap
    Signed-off-by: Dmitry Torokhov

    Randy Dunlap
     
  • Take spinlock when entering ISR and timer routine to ensure that we do not
    race while enabling/disabling FIFO interrupts.

    Also we do not need to take teh spinlock in tegra_kbc_startremove() since
    interrupt is completely disabled.

    Tested-by: Rakesh Iyer
    Signed-off-by: Dmitry Torokhov

    Dmitry Torokhov
     
  • For wakeup to be reliable, kbc needs to be in interrupt mode before suspend.
    Created common routine to control the FIFO interrupt.
    Added synchronization to ensure orderly suspend.

    Signed-off-by: Rakesh Iyer
    Signed-off-by: Dmitry Torokhov

    Rakesh Iyer
     

09 Sep, 2011

1 commit

  • WARNING: drivers/input/keyboard/built-in.o(.text+0xb55b): Section mismatch in reference from the function tc3589x_keypad_open() to the function .devinit.text:tc3589x_keypad_init_key_hardware()
    The function tc3589x_keypad_open() references
    the function __devinit tc3589x_keypad_init_key_hardware().
    This is often because tc3589x_keypad_open lacks a __devinit
    annotation or the annotation of tc3589x_keypad_init_key_hardware is wrong.

    Signed-off-by: Harvey Yang
    Signed-off-by: Dmitry Torokhov

    Harvey Yang
     

08 Sep, 2011

3 commits


29 Aug, 2011

1 commit