From: Nick Dyer <nick.dyer@itdev.co.uk>
To: "Poddar, Sourav" <sourav.poddar@ti.com>
Cc: Daniel Kurtz <djkurtz@chromium.org>,
Yufeng Shen <miletus@chromium.org>,
linux-input@vger.kernel.org, Felipe Balbi <balbi@ti.com>,
"Tiwari, Atul" <Atul.Tiwari@atmel.com>,
"Bowens, Alan" <Alan.Bowens@atmel.com>
Subject: Re: ATMEL MXT224 Touch Controller
Date: Tue, 05 Jun 2012 12:41:59 -0700 [thread overview]
Message-ID: <4FCE6107.8080609@itdev.co.uk> (raw)
In-Reply-To: <CAKdam54qJBkPQ7kU0pfQy_wqr1iNtioEzJunfxE3xVfdZAKdOA@mail.gmail.com>
> The issue which I am facing is that there are many interrupts that comes
> during the probe and it keeps coming after bootup even if I dont touch
> the touch panel.
It sounds like your configuration may need tuning.
> One point which I want to clarify is the use of the RESET pin in the
> controller. If I dont do a "RESET", the probe fails at the first i2c
> read/write. I am doing this reset of the touchscreen controller in my
> board file by the use of a particular gpio. Are you also doing a RESET
Try putting in a delay before the first read, eg 500ms. It may be that the
chip is not ready, it takes some time to settle after power on.
> I saw a lot of patches from you on this driver, which are not there in
> mainline yet. Are you using any local patches also?
Daniel does have some other stuff that hasn't been merged yet.
You will also find some official atmel kernel updates, and some useful
utilities here:
https://github.com/atmel-maxtouch
It would be desirable to push this work upstream, I don't know of any
manufacturer which is shipping the unchanged mainline kernel, most of them
have diverged considerably.
> Is it possible for you to share your touchscreen configuration
> parameters as there might be some parameters which I might be
> configuring wrong?
>
> Any pointer on above point will be really helpful.
I don't know what platform you are working on, but if you contact your
Atmel sales representatives they can provide you with the protocol guide
documentation on the tuning parameters. It generally requires an NDA.
cheers
--
Nick Dyer
Software Engineer, ITDev Ltd
Hardware and Software Development Consultancy
Website: http://www.itdev.co.uk
next prev parent reply other threads:[~2012-06-05 19:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 14:16 ATMEL MXT224 Touch Controller Poddar, Sourav
[not found] ` <CAGS+omAn5_hGbbD1A=vpEOJRaaFc8v0BaDK10E+dt=ZgT4h-Bw@mail.gmail.com>
2012-06-01 10:36 ` Poddar, Sourav
2012-06-05 19:41 ` Nick Dyer [this message]
2012-06-05 20:47 ` Yufeng Shen
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=4FCE6107.8080609@itdev.co.uk \
--to=nick.dyer@itdev.co.uk \
--cc=Alan.Bowens@atmel.com \
--cc=Atul.Tiwari@atmel.com \
--cc=balbi@ti.com \
--cc=djkurtz@chromium.org \
--cc=linux-input@vger.kernel.org \
--cc=miletus@chromium.org \
--cc=sourav.poddar@ti.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).