From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?R2HDq3RhbiBDYXJsaWVy?= Subject: Re: Information about Atmel MXT224 Date: Wed, 08 Jan 2014 13:58:56 +0100 Message-ID: <52CD4B90.8040509@gmail.com> References: <52CD04F1.8090100@gmail.com> <52CD4376.50305@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from mail-ee0-f45.google.com ([74.125.83.45]:35158 "EHLO mail-ee0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756218AbaAHM7N (ORCPT ); Wed, 8 Jan 2014 07:59:13 -0500 Received: by mail-ee0-f45.google.com with SMTP id d49so647302eek.18 for ; Wed, 08 Jan 2014 04:59:11 -0800 (PST) In-Reply-To: Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Peter Meerwald Cc: linux-input@vger.kernel.org, "linux-arm-kernel@lists.infradead.org" , Joonyoung Shim Hello, > just ask harder; I got it from them I am going to ask to another dealer. > you need to understand the object table and see what object leads to = the > invalid object message; there is some mismatch between the driver and= the > chip But you have to admit that without Protocol Guide, it is a little bit=20 harder ;-) > if I remember correctly, the mxt224 does periodic interrupts (200ms?) > when something is wrong with the config That's explain why I previously saw Interrupts running free (100ms or=20 200ms). Thank you, Ga=C3=ABtan Carlier -- To unsubscribe from this list: send the line "unsubscribe linux-input" = in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: gcembed@gmail.com (=?UTF-8?B?R2HDq3RhbiBDYXJsaWVy?=) Date: Wed, 08 Jan 2014 13:58:56 +0100 Subject: Information about Atmel MXT224 In-Reply-To: References: <52CD04F1.8090100@gmail.com> <52CD4376.50305@gmail.com> Message-ID: <52CD4B90.8040509@gmail.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hello, > just ask harder; I got it from them I am going to ask to another dealer. > you need to understand the object table and see what object leads to the > invalid object message; there is some mismatch between the driver and the > chip But you have to admit that without Protocol Guide, it is a little bit harder ;-) > if I remember correctly, the mxt224 does periodic interrupts (200ms?) > when something is wrong with the config That's explain why I previously saw Interrupts running free (100ms or 200ms). Thank you, Ga?tan Carlier