From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "james.chen" <james.chen@emc.com.tw>
Cc: Herman Lin <herman.lin@emc.com.tw>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
Charlie Mooney <charliemooney@chromium.org>
Subject: Re: [PATCH] MAINLINE: Input: elants_i2c: Extend the calibration timeout to 12 second.
Date: Thu, 3 Sep 2015 22:19:13 -0700 [thread overview]
Message-ID: <20150904051913.GA22340@dtor-ws> (raw)
In-Reply-To: <1441337217-1351-1-git-send-email-james.chen@emc.com.tw>
Hi James,
On Fri, Sep 04, 2015 at 11:26:57AM +0800, james.chen wrote:
> From: "james.chen" <james.chen@emc.com.tw>
>
> As the test result of chrome project buddy(23 inch),
> the calibration time is about 9.2~10.5 second.
> So, this patch extend the calibration timeout to 12 second.
>
> BUG= none
> TEST= Build and test on buddy project.
When submitting patches for mainline you do not need to follow ChromeOS
format (i.e have MAINLINE/CHROMIUM prefix and have BUG/TEST tags).
I dropped them from the commit description and applied the patch.
Thanks!
>
> Signed-off-by: James Chen <james.chen@emc.com.tw>
> ---
> drivers/input/touchscreen/elants_i2c.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/input/touchscreen/elants_i2c.c b/drivers/input/touchscreen/elants_i2c.c
> index ddac134..17cc20e 100644
> --- a/drivers/input/touchscreen/elants_i2c.c
> +++ b/drivers/input/touchscreen/elants_i2c.c
> @@ -102,7 +102,7 @@
> #define ELAN_FW_PAGESIZE 132
>
> /* calibration timeout definition */
> -#define ELAN_CALI_TIMEOUT_MSEC 10000
> +#define ELAN_CALI_TIMEOUT_MSEC 12000
>
> #define ELAN_POWERON_DELAY_USEC 500
> #define ELAN_RESET_DELAY_MSEC 20
> --
> 1.8.3.2
>
--
Dmitry
prev parent reply other threads:[~2015-09-04 5:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 3:26 [PATCH] MAINLINE: Input: elants_i2c: Extend the calibration timeout to 12 second james.chen
2015-09-04 5:19 ` Dmitry Torokhov [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=20150904051913.GA22340@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=charliemooney@chromium.org \
--cc=herman.lin@emc.com.tw \
--cc=james.chen@emc.com.tw \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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).