From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Scott Liu <scott.liu@emc.com.tw>
Cc: linux-input@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org,
Benjamin Tissoires <benjamin.tissoires@gmail.com>,
Jesse <jesse@emc.com.tw>, Vincent Wang <vincent.wang@emc.com.tw>,
Paul <paul.liang@emc.com.tw>
Subject: Re: [PATCH v2] Support Elan Touchscreen eKTF product.
Date: Wed, 24 Oct 2012 11:13:23 -0700 [thread overview]
Message-ID: <20121024181323.GA18122@core.coreip.homeip.net> (raw)
In-Reply-To: <1351042903-27538-1-git-send-email-scott.liu@emc.com.tw>
Hi Scott,
On Wed, Oct 24, 2012 at 09:41:43AM +0800, Scott Liu wrote:
> This patch is for Elan eKTF Touchscreen product, I2C adpater module.
>
> Signed-off-by: Scott Liu <scott.liu@emc.com.tw>
> ---
>
> Hi,
> v2 revision I have fixed some bug as your advise.
> 1. To target the mainline
> 2. No Android dependency
> 3. reuse those duplication code from Henrik's patchset.
> (input_mt_sync_frame() / input_mt_get_slot_by_key())
Just a quick run through the code, so:
- please remove polling support, it is not useful in production;
- why do you need a separate probe work instead of doing what you
need in elants_probe()
- it is not a good idea to register input device first and then
allocating memory for MT handling.
- I do not understand why kfifo is needed
- please remove the rest of the custom threads
- you do not need to call input_mt_destroy_slots() explicitly
- use request_firmware() instead of special character device to upload
firmware.
- please use standard kernel-doc markup.
- consider what attributes are there only for debugging and move them to
debugfs.
- I find the use of enums in this driver quite unconventional, just
standard #defines would probably be more straightforward.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2012-10-24 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 1:41 Scott Liu
2012-10-24 18:13 ` Dmitry Torokhov [this message]
2012-10-25 4:32 ` 劉嘉駿
2012-10-25 7:10 ` 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=20121024181323.GA18122@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=benjamin.tissoires@gmail.com \
--cc=jesse@emc.com.tw \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.liang@emc.com.tw \
--cc=scott.liu@emc.com.tw \
--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
Powered by JetHome