From: "ELAN 劉嘉駿" <scott.liu@emc.com.tw>
To: 'Oliver Neukum' <oneukum@suse.de>,
'Dmitry Torokhov' <dmitry.torokhov@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
'Vincent Wang' <vincent.wang@emc.com.tw>,
'Jeff Chuang' <jeff.chuang@emc.com.tw>,
'Benson Leung' <bleung@chromium.org>,
'Benjamin Tissoires' <benjamin.tissoires@gmail.com>,
'Henrik Rydberg' <rydberg@euromail.se>,
'David Herrmann' <dh.herrmann@gmail.com>
Subject: RE: [PATCH v1] Input: elants_i2c: Add Elan touchscreen support
Date: Thu, 20 Nov 2014 20:25:15 +0800 [thread overview]
Message-ID: <000001d004bd$0ad90830$208b1890$@emc.com.tw> (raw)
In-Reply-To: <1416479490.28599.13.camel@linux-0dmf.site>
Hi Oliver:
-----Original Message-----
From: Oliver Neukum [mailto:oneukum@suse.de]
Sent: Thursday, November 20, 2014 6:32 PM
To: Dmitry Torokhov
Cc: scott; linux-kernel@vger.kernel.org; linux-input@vger.kernel.org; Vincent Wang; Jeff Chuang; Benson Leung; Benjamin Tissoires; Henrik Rydberg; David Herrmann
Subject: Re: [PATCH v1] Input: elants_i2c: Add Elan touchscreen support
> +static int elants_i2c_sw_reset(struct i2c_client *client) {
> + const u8 soft_rst_cmd[] = { 0x77, 0x77, 0x77, 0x77 };
> + int error;
> +
> + error = elants_i2c_send(client, soft_rst_cmd,
> + sizeof(soft_rst_cmd));
> + if (error) {
> + dev_err(&client->dev, "software reset failed: %d\n",
> error);
> + return error;
> + }
> +
> + /*
> + * We should wait at least 10 msec (but no more than 40)
> before
> + * sending fastboot or IAP command to the device.
> + */
> + msleep(30);
If timing is critical in both ways, you should take our guarantee if sufficient sleep. I suggest you sleep 11msecs.
Sorry, this is our firmware tricky but it should be sleep longer than 30ms. Actually 70ms.
(Dmitry, I need to modify this delay time to 70ms. Sorry for the changed over and over again;
because we consider big sensor solution which need to use more ICs and need more longer delay)
thanks,
Scott
> +static int elants_i2c_initialize(struct elants_data *ts) {
> + struct i2c_client *client = ts->client;
> + int error, retry_cnt;
> + const u8 hello_packet[] = { 0x55, 0x55, 0x55, 0x55 };
> + const u8 recov_packet[] = { 0x55, 0x55, 0x80, 0x80 };
> + u8 buf[HEADER_SIZE];
> +
Strictly speaking you should disable preemption here.
> + for (retry_cnt = 0; retry_cnt < MAX_RETRIES; retry_cnt++) {
> + error = elants_i2c_sw_reset(client);
> + if (error) {
> + /* Continue initializing if it's the last try
> */
> + if (retry_cnt < MAX_RETRIES - 1)
> + continue;
> + }
Regards
Oliver
--
Oliver Neukum <oneukum@suse.de>
next prev parent reply other threads:[~2014-11-20 12:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-27 12:15 [PATCH v1] Input: elants_i2c: Add Elan touchscreen support scott
2014-11-20 8:11 ` Dmitry Torokhov
2014-11-20 8:55 ` ELAN 劉嘉駿
2014-11-20 10:31 ` Oliver Neukum
2014-11-20 12:25 ` ELAN 劉嘉駿 [this message]
2014-11-20 17:51 ` 'Dmitry Torokhov'
2014-11-21 1:16 ` ELAN 劉嘉駿
2014-11-20 17:47 ` Dmitry Torokhov
2014-11-20 20:27 ` Oliver Neukum
2014-11-20 20:35 ` Dmitry Torokhov
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='000001d004bd$0ad90830$208b1890$@emc.com.tw' \
--to=scott.liu@emc.com.tw \
--cc=benjamin.tissoires@gmail.com \
--cc=bleung@chromium.org \
--cc=dh.herrmann@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jeff.chuang@emc.com.tw \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oneukum@suse.de \
--cc=rydberg@euromail.se \
--cc=vincent.wang@emc.com.tw \
/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).