From: Dan Murphy <murpdj72@gmail.com>
To: Joonyoung Shim <dofmind@gmail.com>
Cc: Henrik Rydberg <rydberg@euromail.se>,
Joonyoung Shim <jy0922.shim@samsung.com>,
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: Mon, 28 Jun 2010 09:33:41 -0500 [thread overview]
Message-ID: <AANLkTikJrtCEEdbtXjFA5PjZo8TvOXqFC872LHJQhfBQ@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikNh-LTClIgXGAIEkegLCmWNnN2Zk05XhZWOumb@mail.gmail.com>
On Mon, Jun 28, 2010 at 9:26 AM, Dan Murphy <murpdj72@gmail.com> 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.
>
> 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.
>
>
>
> Dan
>
> On Mon, Jun 28, 2010 at 8:41 AM, Joonyoung Shim <dofmind@gmail.com> wrote:
>>
>> 2010/6/28 Henrik Rydberg <rydberg@euromail.se>:
>> > Joonyoung Shim wrote:
>> > [...]
>> >> What is the full set of anonymous contacts? It needs the description of
>> >> case sending event for a finger going away.
>> >
>> > I disagree. Protocol A deals with devices that do not necessarily know what
>> > going away means. There is a whole new protocol devoted to your kind of
>> > hardware, type B, and using protocol A is simply not encouraged.
>> >
>>
>> If so, i'm fine.
>>
>> Thanks.
>>
>>
>> --
>> - Joonyoung Shim
>> --
>> 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
>
--
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
next prev parent reply other threads:[~2010-06-28 14:34 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 [this message]
2010-06-29 3:33 ` Joonyoung Shim
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=AANLkTikJrtCEEdbtXjFA5PjZo8TvOXqFC872LHJQhfBQ@mail.gmail.com \
--to=murpdj72@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=dofmind@gmail.com \
--cc=jy0922.shim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-input@vger.kernel.org \
--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 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).