From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Wang Yafei <wangyafei@goodix.com>
Cc: Henrik Rydberg <rydberg@bitmath.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
andrew@goodix.com, mouse@goodix.com
Subject: Re: [PATCH] Add driver for GOODiX GTx5 series touchsereen
Date: Tue, 6 Jun 2017 23:33:11 -0700 [thread overview]
Message-ID: <20170607063311.GB23434@dtor-ws> (raw)
In-Reply-To: <82be2a70-2fe7-93c3-ddeb-e9f9d9243d53@goodix.com>
Hi Wang,
On Wed, Jun 07, 2017 at 12:05:51PM +0800, Wang Yafei wrote:
> This driver is for GOODiX GTx5 series touchscreen controllers
> such as GT8589, GT7589. This driver designed with hierarchial structure,
> for that can be modified to support subsequent controllers easily.
> Some zones of the touchscreen can be set to buttons(according to the
> hardware). That is why it handles button and multitouch events.
>
> A brief description of driver structure
> - Core Layer: This layer responsible for basic input events report,
> GPIO pinctrl, Interrupt, Power resources manager and submodules
> manager.
> - Hardware Layer: This layer responsible for controllers initialization,
> irq handle as well as bus read/write.
> - External Module Layer: This layer used for support more features
> such as firmware update, debug tools and gesture wakeup.
What is the difference between this version and the version you posted a
couple of days ago?
A few high level comments/questions:
- is this for a different chip that what is handled by the Goodix driver
that we already have in the kernel?
- you should be using standard touchscreen bindings described in
Documentation/devicetree/bindings/input/touchscreen/touchscreen.txt
- please use gpiod API without gpio fallbacks: you are submitting the
driver for inclusion into mainline that does have gpiod API and for
mainline it does not make sense to use fallbacks.
- similarly drop other compat stuff for older kernels
- please drop Android stiff (EARLY_SUSPEND, ets).
- use generic device properties (device_property_read_*()) instead of
OF-specific variants.
- use get_unaligned_*() API to convert data on wire to CPU format
instead of doing the same by hand.
- use dev_err(), dev_dbg(), etc for logging.
Thanks.
--
Dmitry
prev parent reply other threads:[~2017-06-07 6:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 4:05 [PATCH] Add driver for GOODiX GTx5 series touchsereen Wang Yafei
2017-06-07 6:33 ` 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=20170607063311.GB23434@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=andrew@goodix.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mouse@goodix.com \
--cc=rydberg@bitmath.org \
--cc=wangyafei@goodix.com \
/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