From: 廖崇榮 <kt.liao@emc.com.tw>
To: "'Daniel Drake'" <drake@endlessm.com>
Cc: "'Dmitry Torokhov'" <dmitry.torokhov@gmail.com>,
"'Chris Chiu'" <chiu@endlessm.com>,
"'Charlie Mooney'" <charliemooney@chromium.org>,
"'Michele Curti'" <michele.curti@gmail.com>,
"'Krzysztof Kozlowski'" <k.kozlowski@samsung.com>,
"'Benson Leung'" <bleung@chromium.org>,
linux-input@vger.kernel.org,
"'Linux Kernel'" <linux-kernel@vger.kernel.org>,
"'Linux Upstreaming Team'" <linux@endlessm.com>,
"'黃世鵬 經理'" <phoenix@emc.com.tw>,
'jimmy_yang' <jimmy_yang@emc.com.tw>,
'Miller_Wang' <miller_wang@emc.com.tw>
Subject: RE: [PATCH] Input: elan_i2c - +200 ms delay before setting to ABS mode
Date: Tue, 28 Jun 2016 09:41:13 +0800 [thread overview]
Message-ID: <003401d1d0de$27b8e1c0$772aa540$@emc.com.tw> (raw)
In-Reply-To: <CAD8Lp44NHiSfPjzYkPCm1jX1Jb2E071WY4_OdCpJv0H7ivEoSg@mail.gmail.com>
Hi Daniel, Chris
-----Original Message-----
From: Daniel Drake [mailto:drake@endlessm.com]
Sent: Tuesday, June 21, 2016 10:42 PM
To: 廖崇榮
Cc: Dmitry Torokhov; Chris Chiu; Charlie Mooney; Michele Curti; Krzysztof Kozlowski; Benson Leung; linux-input@vger.kernel.org; Linux Kernel; Linux Upstreaming Team; 黃世鵬 經理
Subject: Re: [PATCH] Input: elan_i2c - +200 ms delay before setting to ABS mode
On Tue, Jun 21, 2016 at 6:40 AM, 廖崇榮 <kt.liao@emc.com.tw> wrote:
> KT, is this feasible?
> [KT] After internal discussion, we don't agree this patch.
> It's a work-around to fix firmware bug for specific touchpad and
> not tested by other device.
For better or worse, Linux often takes on the responsibility of working around firmware bugs. This is a real issue that affects multiple Asus laptops; you'll have no touchpad input upon reboot from any OS that drives the touchpad in "generic hid" mode (e.g. older version of Linux, some embedded OS, etc).
If the sleep is really that controversial, we could make it specific to the ELAN1000 model that is the one in question here?
[KT] : I list all ASUS models with firmware issue which cause TP no function in Endless OOB , please focuses on below types only
Ic_type : 14
Product_id : 0x14, 0x15, 0x16, 0x25, 0x18, 0x29, 0x2c, 0x31, 0x32, 0x35
You can add if branch in "__elan_initialize", something like that
if(data->ic_ytpe == 14 &&
(data->product_id == 0x14 || data->product_id == 0x15 || data->product_id == 0x16 ||
data->product_id == 0x25 || data->product_id == 0x18 || data->product_id == 0x29 ||
data->product_id == 0x2c || data->product_id == 0x31 || data->product_id == 0x32 || data->product_id == 0x35))
{ //flow for Endless}
Else {//original flow}
prev parent reply other threads:[~2016-06-28 1:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 13:34 [PATCH] Input: elan_i2c - +200 ms delay before setting to ABS mode Chris Chiu
2016-06-20 17:42 ` Dmitry Torokhov
2016-06-21 1:31 ` 廖崇榮
2016-06-21 12:40 ` 廖崇榮
2016-06-21 14:42 ` Daniel Drake
2016-06-22 12:00 ` 廖崇榮
2016-06-28 1:41 ` 廖崇榮 [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='003401d1d0de$27b8e1c0$772aa540$@emc.com.tw' \
--to=kt.liao@emc.com.tw \
--cc=bleung@chromium.org \
--cc=charliemooney@chromium.org \
--cc=chiu@endlessm.com \
--cc=dmitry.torokhov@gmail.com \
--cc=drake@endlessm.com \
--cc=jimmy_yang@emc.com.tw \
--cc=k.kozlowski@samsung.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@endlessm.com \
--cc=michele.curti@gmail.com \
--cc=miller_wang@emc.com.tw \
--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