From: Joonyoung Shim <jy0922.shim@samsung.com>
To: Dan Murphy <murpdj72@gmail.com>
Cc: Joonyoung Shim <dofmind@gmail.com>,
Henrik Rydberg <rydberg@euromail.se>,
dmitry.torokhov@gmail.com, linux-input@vger.kernel.org,
kyungmin.park@samsung.com
Subject: Re: [PATCH v2] input: qt602240 - Add ATMEL QT602240 touchscreen driver
Date: Tue, 29 Jun 2010 12:33:35 +0900 [thread overview]
Message-ID: <4C29698F.9010409@samsung.com> (raw)
In-Reply-To: <AANLkTikNh-LTClIgXGAIEkegLCmWNnN2Zk05XhZWOumb@mail.gmail.com>
Hi,
On 6/28/2010 11:26 PM, Dan Murphy wrote:
> I don't see any error handling from the IC here.
>
> Generally this IC should give a few error messages if a X/Y line is broken,
> the chip goes into reset, or the chip is missed configured.
>
The configuration error can occur and if the chip detect it, we get
messages from message object in interrupt handler and can see it. If
needs, i can add error print.
> This is a bad situation here
> + /* Read dummy message to make high CHG pin */
> + do {
> + ret = qt602240_read_object(data, QT602240_GEN_MESSAGE, 0);
> + if (ret < 0)
> + return ret;
> + } while (ret != 0xff);
>
> The chip may have an error and constantly send you the message which means
> you will never get out of this loop. This can be bad as your probe or
> load_fw may never return.
>
Hmm, this chip reports always 0xff value if the message is nothing, but
i will add count to prevent unlikely loop.
Thanks.
prev parent reply other threads:[~2010-06-29 3:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 1:54 [PATCH v2] input: qt602240 - Add ATMEL QT602240 touchscreen driver Joonyoung Shim
2010-06-25 14:08 ` Henrik Rydberg
2010-06-28 5:16 ` Joonyoung Shim
2010-06-28 7:37 ` Henrik Rydberg
2010-06-28 8:17 ` Joonyoung Shim
2010-06-28 8:34 ` Henrik Rydberg
2010-06-28 8:42 ` Dmitry Torokhov
2010-06-28 8:46 ` Henrik Rydberg
2010-06-28 9:01 ` Dmitry Torokhov
2010-06-28 9:10 ` Henrik Rydberg
2010-06-28 9:05 ` Joonyoung Shim
2010-06-28 9:17 ` Henrik Rydberg
2010-06-28 10:00 ` Joonyoung Shim
2010-06-28 10:22 ` Henrik Rydberg
2010-06-28 11:12 ` Joonyoung Shim
2010-06-28 12:23 ` Henrik Rydberg
2010-06-28 12:58 ` Joonyoung Shim
2010-06-28 13:24 ` Henrik Rydberg
2010-06-28 13:41 ` Joonyoung Shim
[not found] ` <AANLkTikNh-LTClIgXGAIEkegLCmWNnN2Zk05XhZWOumb@mail.gmail.com>
2010-06-28 14:33 ` Dan Murphy
2010-06-29 3:33 ` Joonyoung Shim [this message]
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=4C29698F.9010409@samsung.com \
--to=jy0922.shim@samsung.com \
--cc=dmitry.torokhov@gmail.com \
--cc=dofmind@gmail.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-input@vger.kernel.org \
--cc=murpdj72@gmail.com \
--cc=rydberg@euromail.se \
/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.