From: Simon Budig <simon.budig@kernelconcepts.de>
To: Giulio Benetti <giulio.benetti@micronovasrl.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: dmitry.torokhov@gmail.com, rydberg@bitmath.org,
linux@roeck-us.net, stefan.schoefegger@ginzinger.com,
luca@lucaceresoli.net, martink@posteo.de, a.mathur@samsung.com
Subject: Re: edt-ft5x06 question
Date: Wed, 15 Nov 2017 10:32:08 +0100 [thread overview]
Message-ID: <1510738328.18096.32.camel@kernelconcepts.de> (raw)
In-Reply-To: <9036109f-ae02-01de-77a7-13442e3d9e53@micronovasrl.com>
[-- Attachment #1: Type: text/plain, Size: 2120 bytes --]
Hi Giulio
On Tue, 2017-11-14 at 22:42 +0100, Giulio Benetti wrote:
> I'm using ft5206 with edt-ft5x06.c driver,
> but what I see is that registers with M09 or M06
> seem different from focaltech ft5206
> https://www.buydisplay.com/download/ic/FT5206.pdf
>
> For example, except address 0x80 for threshold register(thgroup),
> all the others don't appear:
> GAIN 0x30 or 0x92 should be 0x82(thcal maybe?)
>
> Can someone clarify this?
The Registers depend heavily on the actual firmware flashed into the
ft5x06. M06 and M09 refers to the resp. touch glasses from EDT (hence
the name of the driver), who have a custom firmware installed. Despite
being based on the same focaltec chips, their i2c interface is totally
different...
Most non-EDT ft5x06 touches do use a communication protocol similiar to
the M09 series. Unfortunately I've witnessed a lot that it is not
possible to rely on the registers that are supposed to provide
vendor/model information (according to the Focaltec datasheet). It
always takes a little bit of tweaking to figure out what resolution
they actually provide (which is possible with the custom EDT-M09
firmware).
There is a patch series I've sent to this mailinglist (and need to
resend, because the first part of the patch series is bogus) that might
improve the model detection a little bit, but it by no means is
bulletproof.
(see https://patchwork.kernel.org/patch/9987467/ and
https://patchwork.kernel.org/patch/9987471/)
For non-EDT touches that are bonded together with a display it is a
reasonable assumption that the touch resolution matches the screen
resolution (Which I consider unfortunate: Why throw away more
resolution?).
Anyway if you have suggestions for improving this driver I am
interested in feedback.
Bye,
Simon
--
kernel concepts GmbH Simon Budig
Sieghuetter Hauptweg 48 simon.budig@kernelconcepts.de
D-57072 Siegen +49-271-771091-17
http://www.kernelconcepts.de/
HR Siegen, HR B 9613; Geschäftsführer: Ole Reinhardt
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2017-11-15 9:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 21:42 edt-ft5x06 question Giulio Benetti
2017-11-15 8:50 ` Luca Ceresoli
2017-11-15 9:32 ` Simon Budig [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-15 16:30 Giulio Benetti
2017-11-15 22:29 ` Giulio Benetti
2017-11-17 17:16 ` Luca Ceresoli
2017-11-17 18:47 ` Giulio Benetti
2017-11-17 19:13 ` Simon Budig
2017-11-18 21:16 ` Giulio Benetti
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=1510738328.18096.32.camel@kernelconcepts.de \
--to=simon.budig@kernelconcepts.de \
--cc=a.mathur@samsung.com \
--cc=dmitry.torokhov@gmail.com \
--cc=giulio.benetti@micronovasrl.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=luca@lucaceresoli.net \
--cc=martink@posteo.de \
--cc=rydberg@bitmath.org \
--cc=stefan.schoefegger@ginzinger.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).