From: Kamal Mostafa <kamal@canonical.com>
To: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Henrik Rydberg <rydberg@euromail.se>
Cc: Dudley Du <dudl@cypress.com>, David Solda <dso@cypress.com>,
Troy Abercrombia <ta@cypress.com>,
Kamal Mostafa <kamal@canonical.com>,
Kyle Fazzari <git@status.e4ward.com>,
Mario Limonciello <mario_limonciello@dell.com>,
Tim Gardner <tim.gardner@canonical.com>,
Herton Krzesinski <herton.krzesinski@canonical.com>
Subject: [PATCH v5 0/3] Cypress PS/2 Trackpad driver
Date: Wed, 5 Dec 2012 16:16:13 -0800 [thread overview]
Message-ID: <1354752976-27257-1-git-send-email-kamal@canonical.com> (raw)
This driver, submitted on behalf of Cypress Semiconductor Corporation and
additional contributors, provides support for the Cypress PS/2 Trackpad.
This [PATCH v5] version differs from my previous submitted version[3]:
Patch #1 (cmdbuf to 8 bytes) and #3 (link in driver) are unchanged.
Patch #4 (simulated multitouch) has been dropped.
Patch #2 (main driver) changes:
- fixed cypress_reconnect/suspend/resume (don't let pkt_size get clobbered)
as recommended by Henrik Rydberg:
- removed all the CYTP_RELATIVE_SUPPORT code.
- removed debug-only vscroll/hscroll code.
- renamed "vital_stat{ist}ics" to "tp_metrics".
- fixed cypress_set_input_params x/y sanity check.
- clarified cypress_parse_packet contact_cnt palm-detection check.
- clarified cypress_ps2_ext_cmd comment.
- dropped separate #define CTYP_MAX_CONTACTS.
Known problems: None.
-Kamal Mostafa <kamal@canonical.com>
[0] PATCH v1: http://www.spinics.net/lists/linux-input/msg23690.html
[1] PATCH v2: http://www.spinics.net/lists/linux-input/msg23718.html
[2] PATCH v3: http://www.spinics.net/lists/linux-input/msg23943.html
[3] PATCH v4: http://www.spinics.net/lists/linux-input/msg24047.html
Dudley Du (2):
input: Cypress PS/2 Trackpad psmouse driver
input: Cypress PS/2 Trackpad link into psmouse-base
Kamal Mostafa (1):
input: increase struct ps2dev cmdbuf[] to 8 bytes
drivers/input/mouse/Kconfig | 10 +
drivers/input/mouse/Makefile | 1 +
drivers/input/mouse/cypress_ps2.c | 740 ++++++++++++++++++++++++++++++++++++
drivers/input/mouse/cypress_ps2.h | 216 +++++++++++
drivers/input/mouse/psmouse-base.c | 32 ++
drivers/input/mouse/psmouse.h | 1 +
include/linux/libps2.h | 2 +-
7 files changed, 1001 insertions(+), 1 deletion(-)
create mode 100644 drivers/input/mouse/cypress_ps2.c
create mode 100644 drivers/input/mouse/cypress_ps2.h
--
1.7.10.4
next reply other threads:[~2012-12-06 0:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 0:16 Kamal Mostafa [this message]
2012-12-06 0:16 ` [PATCH v5 1/3] input: increase struct ps2dev cmdbuf[] to 8 bytes Kamal Mostafa
2012-12-06 7:51 ` Dmitry Torokhov
2012-12-06 0:16 ` [PATCH v5 2/3] input: Cypress PS/2 Trackpad psmouse driver Kamal Mostafa
2012-12-06 8:08 ` Dmitry Torokhov
2012-12-07 2:09 ` Kamal Mostafa
2012-12-06 0:16 ` [PATCH v5 3/3] input: Cypress PS/2 Trackpad link into psmouse-base Kamal Mostafa
2012-12-06 7:52 ` Dmitry Torokhov
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=1354752976-27257-1-git-send-email-kamal@canonical.com \
--to=kamal@canonical.com \
--cc=dmitry.torokhov@gmail.com \
--cc=dso@cypress.com \
--cc=dudl@cypress.com \
--cc=git@status.e4ward.com \
--cc=herton.krzesinski@canonical.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario_limonciello@dell.com \
--cc=rydberg@euromail.se \
--cc=ta@cypress.com \
--cc=tim.gardner@canonical.com \
/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).