linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: [git pull] Input updates for 4.9-rc0 (part 2)
Date: Fri, 14 Oct 2016 12:36:06 -0700	[thread overview]
Message-ID: <20161014193606.GA8678@dtor-ws> (raw)

Hi Linus,

Please pull from:

	git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus

to receive updates for the input subsystem. You will gen an update to
ALPS driver to support V8 protocol with touchstick, change for i8042 to
skip selftest on many Asus laptops, which helps to keep their touchpads
working after resume, and couple other driver fixes.

Changelog:
---------

Ben Gamari (5):
      Input: ALPS - add touchstick support for SS5 hardware
      Input: ALPS - handle 0-pressure 1F events
      Input: ALPS - allow touchsticks to report pressure
      Input: ALPS - set DualPoint flag for 74 03 28 devices
      Input: ALPS - add V8 protocol documentation

Dmitry Torokhov (1):
      Input: elantech - add Fujitsu Lifebook E556 to force crc_enabled

Guenter Roeck (2):
      Input: synaptics-rmi4 - fix error handling in SPI transport driver
      Input: synaptics-rmi4 - fix error handling in I2C transport driver

Marcos Paulo de Souza (2):
      Input: elantech - fix Lenovo version typo
      Input: i8042 - skip selftest on ASUS laptops

Matti Kurkela (1):
      Input: elantech - force needed quirks on Fujitsu H760

Sangwon Jee (3):
      Input: melfas_mip4 - add devicetree binding documentations
      Input: melfas_mip4 - add maintainer information
      Input: melfas_mip4 - add ic_name sysfs attribute


Diffstat:
--------

 .../bindings/input/touchscreen/melfas_mip4.txt     | 21 +++++
 .../devicetree/bindings/vendor-prefixes.txt        |  1 +
 Documentation/input/alps.txt                       | 57 +++++++++++++
 Documentation/kernel-parameters.txt                |  9 +-
 MAINTAINERS                                        |  7 ++
 drivers/input/mouse/alps.c                         | 87 +++++++++++++++++---
 drivers/input/mouse/alps.h                         |  2 +
 drivers/input/mouse/elantech.c                     | 27 +++++-
 drivers/input/rmi4/rmi_i2c.c                       | 38 ++++++---
 drivers/input/rmi4/rmi_spi.c                       | 22 ++---
 drivers/input/serio/i8042-io.h                     |  2 +-
 drivers/input/serio/i8042-ip22io.h                 |  2 +-
 drivers/input/serio/i8042-ppcio.h                  |  2 +-
 drivers/input/serio/i8042-sparcio.h                |  2 +-
 drivers/input/serio/i8042-unicore32io.h            |  2 +-
 drivers/input/serio/i8042-x86ia64io.h              | 96 +++++++++++++++++++++-
 drivers/input/serio/i8042.c                        | 55 ++++++++++---
 drivers/input/touchscreen/melfas_mip4.c            | 38 ++++++++-
 18 files changed, 411 insertions(+), 59 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/input/touchscreen/melfas_mip4.txt

-- 
Dmitry


                 reply	other threads:[~2016-10-14 19:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161014193606.GA8678@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).