Received: by 10.223.164.202 with SMTP id h10csp317638wrb; Fri, 17 Nov 2017 00:51:39 -0800 (PST) X-Google-Smtp-Source: AGs4zMZ4jCMheTQ5NlDZhUn1cnz2kLEGX9fcCO2k9hUuzKY/m6b7lBJG7h11NDDej135Z7QUNZlY X-Received: by 10.159.246.20 with SMTP id b20mr4438326pls.95.1510908699849; Fri, 17 Nov 2017 00:51:39 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1510908699; cv=none; d=google.com; s=arc-20160816; b=vmtDri+RTzc3h9UHvUEdg3In7PiJb0uCjKBfivVEeoYKP8wPxaR3ql8C2S9/f/IMk/ Zzy5p3F1k7X6c09yLlrqh12smNsvsvNkR+RGd8rmOrmguY2Sxi0Fwu22+ejIJ/yNxuhx ANwzjrGiUENrcSY+cgC5rwxcT0MnXaglQDpRdgPAHoLQDA1FrWHKWRwuwdfG7wD68OSF ke0C1DL/TdG21SWbhS1aDNFebbqMgRPDlaKwFVnPKvUDlF3oLdlAsX5vi02TgUskjWNG 2n8cVZ/2X5xh4z1vW1hs4ZS20X7pgtBhvcGZD5obUMsezfh5vu53V11ZIZXJkXNG7LId bsKg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:mime-version:user-agent:date:message-id:subject:cc :to:from:dkim-signature:arc-authentication-results; bh=+0mq+kNA0Ru5vJ0etGbgeJHH9r6JFe1P0LASVYUXgOc=; b=tdeZ8tFTHFJUnCwR5L6sQhaVlV9qTHshQKqo1I029VnwLr2apBRRhjnb+Uv4tqVdhC r4Uap+sct4wzfsLbSNoA6I96eyvGh/E27yFQaap+eRE08AoloD2ZUPtaXuZoHXkskkaG Ox3aa92izezyFwEs8LUdcH9oh7um/Xi0XpUzvxuiw88P4BQAWsvJSZAeABeAL7gPXeKK DvmAM0XlaG7x0ao8B5lDcvM5SkNrluqjUTDdwsNHKdTIRsWRPU1mkWLCeBHECkOi0iib j153GV8wO23JHLvOf+KBw0Eknz1QzWszZI2u2Xio3iFgQbf7wvEVVS0JvmmXkvv/fcIe 9mlQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=temperror (no key for signature) header.i=@micronovasrl.com header.s=dkim header.b=UJ8VVV1j; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s14si2648338pfa.333.2017.11.17.00.51.27; Fri, 17 Nov 2017 00:51:39 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=temperror (no key for signature) header.i=@micronovasrl.com header.s=dkim header.b=UJ8VVV1j; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936484AbdKPXKh (ORCPT + 92 others); Thu, 16 Nov 2017 18:10:37 -0500 Received: from mail.micronovasrl.com ([212.103.203.10]:41428 "EHLO mail.micronovasrl.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S936386AbdKPXKc (ORCPT ); Thu, 16 Nov 2017 18:10:32 -0500 Received: from mail.micronovasrl.com (mail.micronovasrl.com [127.0.0.1]) by mail.micronovasrl.com (Postfix) with ESMTP id 9FA00B015EE for ; Fri, 17 Nov 2017 00:10:30 +0100 (CET) Authentication-Results: mail.micronovasrl.com (amavisd-new); dkim=pass reason="pass (just generated, assumed good)" header.d=micronovasrl.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=micronovasrl.com; h=content-transfer-encoding:content-language:content-type :content-type:mime-version:user-agent:date:date:message-id :subject:subject:to:from:from; s=dkim; t=1510873830; x= 1511737831; bh=sWGyp/z66gPcdVn1v79q/GV4KW+06DpXpUwDuSnmY8E=; b=U J8VVV1jN+PtFy7JPmLatwSMqSO9YGKMKNq6I3ihiWbPKtiF7//bi9BNQX/68f/a3 4QLPAXdQing8v5OAQ311Ug6jydgy5ZyNS3pyuGp381HJ/ONyIYIDeOGAyUbeOn7y cMRWllyJr5vqv3CvVJwIhX3J1sX3ZNrgh0eXiniPuc= X-Virus-Scanned: Debian amavisd-new at mail.micronovasrl.com Received: from mail.micronovasrl.com ([127.0.0.1]) by mail.micronovasrl.com (mail.micronovasrl.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id l-YZVmPATia2 for ; Fri, 17 Nov 2017 00:10:30 +0100 (CET) Received: from [192.168.123.48] (unknown [192.168.123.48]) by mail.micronovasrl.com (Postfix) with ESMTPSA id 43A4EB002F1; Fri, 17 Nov 2017 00:10:29 +0100 (CET) From: Giulio Benetti To: 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, simon.budig@kernelconcepts.de, martink@posteo.de, a.mathur@samsung.com Subject: Re: Re: edt-ft5x06 question Message-ID: <98c15a70-1756-0037-3803-3b782ede2545@micronovasrl.com> Date: Fri, 17 Nov 2017 00:10:30 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15; format=flowed Content-Language: it Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Simon, sorry for the mess with mailing list. My mail filter gave me problems and removed e-mails from linux-input mailing list. > 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. I only have an idea, since we can't know for sure what's the Vendor, and we can't know for sure max_x and max_y, I would like to add a field in dt to select which vendor to use. For example, if you choose "Edt" as vendor, than driver behaves like it does now, otherwise there could be "Focaltech" as vendor, and in that case I could find a way to get max_x and max_y. If I can't find a way, we put the need to be inserted in dts both max_x and max_y. Also I would like to export more registers as attributes and dt. And last. In my company, on previous projects, we experienced problems with temperature and mechanical drifts. So the only solution was to send an autocalibrate every n seconds, when ts is untouched. I did this adding a timed tasklet inside driver, so I would like to do the same. Now what comes in my mind is, do we need to keep everything in the same driver edt-ft5x.c? Or does it make sense to write new one(focaltech-ft5x.c) based on edt-ft5x.c? Best regards > > Bye, > Simon > > -- > kernel concepts GmbH Simon Budig > Sieghuetter Hauptweg 48 simon.budig@xxxxxxxxxxxxxxxxx > D-57072 Siegen +49-271-771091-17 > http://www.kernelconcepts.de/ > HR Siegen, HR B 9613; Gesch�ftsf�hrer: Ole Reinhardt -- Giulio Benetti R&D Manager & Advanced Research MICRONOVA SRL Sede: Via A. Niedda 3 - 35010 Vigonza (PD) Tel. 049/8931563 - Fax 049/8931346 Cod.Fiscale - P.IVA 02663420285 Capitale Sociale � 26.000 i.v. Iscritta al Reg. Imprese di Padova N. 02663420285 Numero R.E.A. 258642 From 1584186291369816083@xxx Thu Nov 16 02:02:58 +0000 2017 X-GM-THRID: 1584085398794430736 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread