linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: linux-input@vger.kernel.org,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	Jiri Kosina <jkosina@suse.cz>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Subject: [PATCH v4 0/5] add support for high res wheel found on some Logitech devices
Date: Tue, 11 Apr 2017 10:29:37 -0300	[thread overview]
Message-ID: <cover.1491917052.git.mchehab@s-opensource.com> (raw)

Some Logitech mouses (MX Anyware 2, MX Master) have a wheel with two
resolutions. It initializes in low resolution mode, but can be changed to high
resolution. It also supports free wheel mode, where there's no tactile
feedback at the wheel, nor it offers resistence to movements. Such mode is
enabled/disabled by clicking at the wheel (on this wheel, the middle button
is a separate button).

Add support for it.

Tested on with MX Anywhere 2 device.

PS.:
       Patches 2 and 3 will have trivial conflicts with -next version of the
       input tree, due to the documentation patches that got merged there.

v4:
 - rebased on the top of HID tree, branch 'for-next'
 - added a patch reserving some REL_MISC_n events
 - fixed CMD_MOUSE_SET_WHEEL_MODE params logic;
 - don't send 16 bytes on FAP command sync - send just what's needed;
 - HIDPP_QUIRK_CONNECT_EVENTS is now applied by default.

v3: addressed Peter's comments for EV_SW SW_RATCHET documentation

Mauro Carvalho Chehab (5):
  input: event-codes: reserve some space for REL_MISC events
  input: add an EV_REL event for high-res vertical wheel
  input: add a EV_SW event for ratchet switch
  hid-logitech-hidpp: add support for high res wheel
  hid-logitech-hidpp: add support for ratchet switch

 Documentation/input/event-codes.txt    |  29 ++++-
 drivers/hid/hid-logitech-hidpp.c       | 216 +++++++++++++++++++++++++++++++++
 include/linux/mod_devicetable.h        |   4 +-
 include/uapi/linux/input-event-codes.h |  13 +-
 4 files changed, 255 insertions(+), 7 deletions(-)

-- 
2.9.3



             reply	other threads:[~2017-04-11 13:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11 13:29 Mauro Carvalho Chehab [this message]
2017-04-11 13:29 ` [PATCH v4 1/5] input: event-codes: reserve some space for REL_MISC events Mauro Carvalho Chehab
2017-04-11 13:29   ` [PATCH v4 2/5] input: add an EV_REL event for high-res vertical wheel Mauro Carvalho Chehab
2017-04-11 13:29     ` [PATCH v4 3/5] input: add a EV_SW event for ratchet switch Mauro Carvalho Chehab
2017-04-11 13:29       ` [PATCH v4 4/5] hid-logitech-hidpp: add support for high res wheel Mauro Carvalho Chehab
2017-04-11 13:29         ` [PATCH v4 5/5] hid-logitech-hidpp: add support for ratchet switch Mauro Carvalho Chehab
2017-04-14 12:56           ` Benjamin Tissoires
2017-04-14 12:54       ` [PATCH v4 3/5] input: add a EV_SW event " Benjamin Tissoires
2017-04-15 18:04       ` Dmitry Torokhov
2017-04-15 22:50         ` Mauro Carvalho Chehab
2017-04-15 17:55   ` [PATCH v4 1/5] input: event-codes: reserve some space for REL_MISC events Dmitry Torokhov
2017-06-21 12:05     ` Benjamin Tissoires

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=cover.1491917052.git.mchehab@s-opensource.com \
    --to=mchehab@s-opensource.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.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).