From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Matteo Delfino <kendatsuba@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH] Input: elantech - fix packet check for v3 and v4 hardware
Date: Thu, 15 Aug 2013 00:12:51 -0700 [thread overview]
Message-ID: <20130815071251.GC15691@core.coreip.homeip.net> (raw)
In-Reply-To: <1376473037-11211-1-git-send-email-kendatsuba@gmail.com>
Hi Matteo,
On Wed, Aug 14, 2013 at 11:37:17AM +0200, Matteo Delfino wrote:
> The signatures of v3 and v4 packets change depending on the value of a
> hardware flag called 'crc_enabled'. The packet type detection must change
> accordingly.
>
> This patch also restores a consistency check for v4 packets inadvertently
> removed by commit:
>
> 9eebed7de660c0b5ab129a9de4f89d20b60de68c
> Input: elantech - fix for newer hardware versions (v7)
>
> A note about the naming convention: v3 hardware is associated with IC body
> v5 while v4 hardware is associated with IC body v6 and v7. The above commit
> refers to IC body v7, not to v7 hardware.
>
> Tested on Samsung NP730U3E (fw = 0x675f05, ICv7, crc_enabled = 1)
>
> Tested-by: Giovanni Frigione <gio.frigione@gmail.com>
> Signed-off-by: Matteo Delfino <kendatsuba@gmail.com>
> ---
>
> Hello Dmitry,
> this patch is based on some information provided by elantech. It has
> been successfully tested on the above v4 hardware so the information
> seems to be reliable. More testing is needed on v3 hardware with
> crc_enabled=1 (if there's such hardware out there..). The behaviour
> should be unchanged for v3 and v4 hardware with crc_enabled=0 (the
> vast majority).
>
> I was asked to CC stable kernels too since this patch restores a
> consistency check on v4 packets removed by a previous commit already
> queued in linux-3.5.y-queue but, considering the above, I think it's
> best to leave this decision to you.
Once again, I think it should bake a bit in the trees before heading for
next, so I won't mark it for stable. Feel free to forward it later, once
it survives a few -rcs.
Thanks!
--
Dmitry
prev parent reply other threads:[~2013-08-15 7:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 9:37 [PATCH] Input: elantech - fix packet check for v3 and v4 hardware Matteo Delfino
2013-08-15 7:12 ` Dmitry Torokhov [this message]
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=20130815071251.GC15691@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=kendatsuba@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).