linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: JJ Ding <jj_ding@emc.com.tw>
To: linux-input@vger.kernel.org
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	JJ Ding <jj_ding@emc.com.tw>
Subject: [RFC PATCH 0/2] Input: psmouse - new mechanism for bad packet handling
Date: Wed,  7 Dec 2011 19:38:42 +0800	[thread overview]
Message-ID: <1323257924-12773-1-git-send-email-jj_ding@emc.com.tw> (raw)

Hi list,

The first patch adds a new way to deal with bad packets. This mechanism is
used in our original driver. When I first sent the patches to support elan's
v3 and v4 hardware, Dmitry suggested this should be done in psmouse core, so
here is another try.

I am not sure if this is the prefered way to handle bad packets, so I introduce
PSMOUSE_SHIFT_PACKET for psmouse_ret_t, and convert elan driver to use this.

These patches are sent to gather feedback and comments, please take a look, and
let me know if this new mechanism is OK. Thank you very much.

P.S. patches are against Dmitry's -next tree.

Best regards,
-JJ

JJ Ding (2):
  Input: psmouse - work around EC buffer
  Input: elantech - convert v1 ~ v3 hardware to use
    PSMOUSE_SHIFT_PACKET

 drivers/input/mouse/elantech.c     |    6 +++---
 drivers/input/mouse/psmouse-base.c |    5 +++++
 drivers/input/mouse/psmouse.h      |    3 ++-
 3 files changed, 10 insertions(+), 4 deletions(-)

-- 
1.7.8


             reply	other threads:[~2011-12-07 11:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-07 11:38 JJ Ding [this message]
2011-12-07 11:38 ` [RFC PATCH 1/2] Input: psmouse - work around EC buffer JJ Ding
2011-12-07 11:38 ` [RFC PATCH 2/2] Input: elantech - convert v1 ~ v3 hardware to use PSMOUSE_SHIFT_PACKET JJ Ding
2012-01-29 11:11 ` [RFC PATCH 0/2] Input: psmouse - new mechanism for bad packet handling Marc Dietrich

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=1323257924-12773-1-git-send-email-jj_ding@emc.com.tw \
    --to=jj_ding@emc.com.tw \
    --cc=dmitry.torokhov@gmail.com \
    --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).