From: 'Dmitry Torokhov' <dmitry.torokhov@gmail.com>
To: jingle <jingle.wu@emc.com.tw>
Cc: 'linux-kernel' <linux-kernel@vger.kernel.org>,
'linux-input' <linux-input@vger.kernel.org>,
'phoenix' <phoenix@emc.com.tw>,
"'dave.wang'" <dave.wang@emc.com.tw>,
"'josh.chen'" <josh.chen@emc.com.tw>
Subject: Re: [PATCH] Input: elan_i2c - Reduce the resume time for new dev ices
Date: Mon, 8 Mar 2021 17:37:47 -0800 [thread overview]
Message-ID: <YEbRazfF0iTreYYz@google.com> (raw)
In-Reply-To: <005d01d713f8$e4b715a0$ae2540e0$@emc.com.tw>
Hi Jingle,
On Mon, Mar 08, 2021 at 04:56:14PM +0800, jingle wrote:
> Hi Dmitry:
>
> 1. missing "i<"
> + u32 quirks = 0;
> + int i;
> +
> + for (i = 0; ARRAY_SIZE(elan_i2c_quirks); i++) {
>
> -> for (i = 0; i<ARRAY_SIZE(elan_i2c_quirks); i++) {
Yes, you are right of course. Was this the only issue with the updated
patch? Did it work for you otherwise?
>
> 2. elan_resume () funtion are different with at Chromeos driver.
> @@ -1384,7 +1422,7 @@ static int __maybe_unused elan_resume(struct device
> *dev)
> goto err;
> }
>
> - error = elan_initialize(data);
> + error = elan_initialize(data, data->quirks &
> ETP_QUIRK_QUICK_WAKEUP);
> if (error)
> dev_err(dev, "initialize when resuming failed: %d\n",
> error);
>
> -> https://chromium.googlesource.com/chromiumos/third_party/kernel/+/ref
> -> s/heads/chromeos-5.4/drivers/input/mouse/elan_i2c_core.c#1434
> -> error = elan_initialize(data); this code is in elan_reactivate()
> function at Chromeos driver.
> -> Will this change affect cherrypick from linux kernel to chromeos?
Yes, we would need to adjust the patch for Chrome OS and have
elan_reactivate() to call elan_initialize() with appropriate argument.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2021-03-09 1:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 7:35 [PATCH] Input: elan_i2c - Reduce the resume time for new devices jingle.wu
2021-03-01 5:31 ` Dmitry Torokhov
2021-03-02 1:04 ` [PATCH] Input: elan_i2c - Reduce the resume time for new dev ices jingle.wu
2021-03-05 0:55 ` Dmitry Torokhov
2021-03-05 1:24 ` jingle
2021-03-05 1:31 ` 'Dmitry Torokhov'
2021-03-05 1:50 ` jingle
2021-03-08 3:18 ` 'Dmitry Torokhov'
2021-03-08 8:56 ` jingle
2021-03-09 1:37 ` 'Dmitry Torokhov' [this message]
[not found] ` <00ce01d714ef$2598f740$70cae5c0$@emc.com.tw>
2021-03-09 14:53 ` jingle.wu
2021-03-10 5:46 ` 'Dmitry Torokhov'
2021-03-09 6:29 ` Dan Carpenter
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=YEbRazfF0iTreYYz@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=dave.wang@emc.com.tw \
--cc=jingle.wu@emc.com.tw \
--cc=josh.chen@emc.com.tw \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phoenix@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).