From: "Gaëtan Carlier" <gcembed@gmail.com>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: linux-input@vger.kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Joonyoung Shim <jy0922.shim@samsung.com>
Subject: Re: Information about Atmel MXT224
Date: Wed, 08 Jan 2014 13:58:56 +0100 [thread overview]
Message-ID: <52CD4B90.8040509@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.01.1401081344451.1454@pmeerw.net>
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
--
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
WARNING: multiple messages have this Message-ID (diff)
From: gcembed@gmail.com (Gaëtan Carlier)
To: linux-arm-kernel@lists.infradead.org
Subject: Information about Atmel MXT224
Date: Wed, 08 Jan 2014 13:58:56 +0100 [thread overview]
Message-ID: <52CD4B90.8040509@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.01.1401081344451.1454@pmeerw.net>
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
next prev parent reply other threads:[~2014-01-08 12:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 7:57 Information about Atmel MXT224 Gaëtan Carlier
2014-01-08 7:57 ` Gaëtan Carlier
2014-01-08 9:04 ` Alexander Shiyan
2014-01-08 9:04 ` Alexander Shiyan
2014-01-08 11:24 ` Gaëtan Carlier
2014-01-08 11:24 ` Gaëtan Carlier
2014-01-08 11:42 ` Peter Meerwald
2014-01-08 11:42 ` Peter Meerwald
2014-01-08 12:24 ` Gaëtan Carlier
2014-01-08 12:24 ` Gaëtan Carlier
2014-01-08 12:50 ` Peter Meerwald
2014-01-08 12:50 ` Peter Meerwald
2014-01-08 12:58 ` Gaëtan Carlier [this message]
2014-01-08 12:58 ` Gaëtan Carlier
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=52CD4B90.8040509@gmail.com \
--to=gcembed@gmail.com \
--cc=jy0922.shim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.