From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756991AbbLBUxB (ORCPT ); Wed, 2 Dec 2015 15:53:01 -0500 Received: from kdh-gw.itdev.co.uk ([89.21.227.133]:52856 "EHLO hermes.kdh.itdev.co.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1756119AbbLBUvT (ORCPT ); Wed, 2 Dec 2015 15:51:19 -0500 From: Nick Dyer To: Dmitry Torokhov Cc: Yufeng Shen , Benson Leung , linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, Alan Bowens , Javier Martinez Canillas , Chris Healy Subject: [PATCH RFC 0/8] Input: atmel_mxt_ts - raw data via debugfs Date: Wed, 2 Dec 2015 20:42:23 +0000 Message-Id: <1449088951-7069-1-git-send-email-nick.dyer@itdev.co.uk> X-Mailer: git-send-email 2.5.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello- This is a series of patches to add diagnostic data support to the Atmel maXTouch driver. There's an existing implementation in the open-source mxt-app tool, however there are performance advantages to moving this code into the driver. The algorithm for retrieving the data has been fairly consistent across a range of chips, with the exception of the mXT1386 series (see patch). The intention is to open-source a utility which can read/display this data, this should be available very shortly. It would be good if we could agree a single debugfs interface which could be supported by all touchscreen chips that have this kind of feature, so I've attempted to keep that part of this vendor neutral. This patch sequence is also available from https://github.com/ndyer/linux/commits/diagnostic-debug Any feedback appreciated. Best regards Nick Dyer