lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 17 May 2020 21:05:32 -0700 From: Dmitry Torokhov <dmitry.torokhov@...il.com> To: Michał Mirosław <mirq-linux@...e.qmqm.pl> Cc: David Heidelberg <david@...t.cz>, Dmitry Osipenko <digetx@...il.com>, Henrik Rydberg <rydberg@...math.org>, James Chen <james.chen@....com.tw>, Johnny Chuang <johnny.chuang@....com.tw>, Rob Herring <robh+dt@...nel.org>, Scott Liu <scott.liu@....com.tw>, linux-input@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH v5 07/10] input: elants: support 0x66 reply opcode for reporting touches On Sun, Apr 26, 2020 at 07:47:52PM +0200, Michał Mirosław wrote: > From: Dmitry Osipenko <digetx@...il.com> > > eKTF3624 touchscreen firmware uses two variants of the reply opcodes for > reporting touch events: one is 0x63 (used by older firmware) and other is > 0x66 (used by newer firmware). The 0x66 variant is equal to 0x63 of > eKTH3500, while 0x63 needs small adjustment of the touch pressure value. > > Nexus 7 tablet device has eKTF3624 touchscreen and it uses 0x66 opcode for > reporting touch events, let's support it now. Other devices, eg. ASUS TF300T, > use 0x63. > > Note: CMD_HEADER_REK is used for replying to calibration requests, it has > the same 0x66 opcode number which eKTF3624 uses for reporting touches. > The calibration replies are handled separately from the the rest of the > commands in the driver by entering into ELAN_WAIT_RECALIBRATION state > and thus this change shouldn't change the old behavior. Is it possible to know what format a device will use by querying it at probe time? Thanks. -- Dmitry
Powered by blists - more mailing lists