From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Iiro Valkonen <iiro.valkonen@atmel.com>
Cc: Joonyoung Shim <jy0922.shim@samsung.com>, linux-input@vger.kernel.org
Subject: Re: [PATCH 1/3] Input: atmel_mxt_ts - Make wait-after-reset period compatible with all chips
Date: Mon, 4 Jul 2011 03:04:36 -0700 [thread overview]
Message-ID: <20110704100435.GA3723@core.coreip.homeip.net> (raw)
In-Reply-To: <4E11825B.3000409@atmel.com>
On Mon, Jul 04, 2011 at 12:05:31PM +0300, Iiro Valkonen wrote:
> The delay before the chip can be accessed after reset varies between different
> chips in maXTouch family. Waiting for 200ms and then monitoring the CHG (chip
> is ready when the line is low) is guaranteed to work with all chips.
>
> Signed-off-by: Iiro Valkonen <iiro.valkonen@atmel.com>
> ---
> drivers/input/touchscreen/atmel_mxt_ts.c | 4 +++-
> include/linux/i2c/atmel_mxt_ts.h | 1 +
> 2 files changed, 4 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c b/drivers/input/touchscreen/atmel_mxt_ts.c
> index 1e61387..8870e7b 100644
> --- a/drivers/input/touchscreen/atmel_mxt_ts.c
> +++ b/drivers/input/touchscreen/atmel_mxt_ts.c
> @@ -170,7 +170,7 @@
> #define MXT_BOOT_VALUE 0xa5
> #define MXT_BACKUP_VALUE 0x55
> #define MXT_BACKUP_TIME 25 /* msec */
> -#define MXT_RESET_TIME 65 /* msec */
> +#define MXT_RESET_TIME 200 /* msec */
>
> #define MXT_FWRESET_TIME 175 /* msec */
>
> @@ -828,6 +828,8 @@ static int mxt_initialize(struct mxt_data *data)
> mxt_write_object(data, MXT_GEN_COMMAND,
> MXT_COMMAND_RESET, 1);
> msleep(MXT_RESET_TIME);
> + while (data->pdata->read_chg())
> + msleep(2);
I would prefer if we did not wait indefinitely but timed out after
certain number of retries.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2011-07-04 10:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 9:05 [PATCH 1/3] Input: atmel_mxt_ts - Make wait-after-reset period compatible with all chips Iiro Valkonen
2011-07-04 10:04 ` Dmitry Torokhov [this message]
2011-07-04 12:42 ` Iiro Valkonen
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=20110704100435.GA3723@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=iiro.valkonen@atmel.com \
--cc=jy0922.shim@samsung.com \
--cc=linux-input@vger.kernel.org \
/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).