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: <alpine.DEB.2.01.1401081344451.1454@pmeerw.net>
References: <52CD04F1.8090100@gmail.com>
 <alpine.DEB.2.01.1401081228580.1454@pmeerw.net> <52CD4376.50305@gmail.com>
 <alpine.DEB.2.01.1401081344451.1454@pmeerw.net>
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