From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Priit Laes <plaes@plaes.org>
Cc: Bastien Nocera <hadess@hadess.net>,
linux-input@vger.kernel.org, Henrik Rydberg <rydberg@bitmath.org>
Subject: Re: [PATCH] Input: goodix - preliminary support for GT801-2+1
Date: Sun, 5 Apr 2015 11:43:19 -0700 [thread overview]
Message-ID: <20150405184319.GA31564@dtor-ws> (raw)
In-Reply-To: <1428253576.29867.7.camel@plaes.org>
On Sun, Apr 05, 2015 at 08:06:16PM +0300, Priit Laes wrote:
> On Sun, 2015-04-05 at 18:04 +0200, Bastien Nocera wrote:
> > On Sun, 2015-04-05 at 00:08 +0300, Priit Laes wrote:
> > > This patch implements GT801x2 touchscreen support.
> > > Unfortunately, there is a big difference between GT801 and GT9xx
> > > series
> > > chips, therefore some advice is needed on how to proceed.
> > >
> > > Differences between GT801x2 and GT9xx series:
> > >
> > > 1. I2C registers: 1 byte (GT801x2) vs 2 bytes (GT9xx)
> > > 2. Different configuration layout and version info
> > > 3. Different touch report protocol
> >
> > That doesn't seem like an awful lot of differences. Approximately 80
> > line changes for 500 lines of driver code. You could add an enum for
> > the 8xx and 9xx types near the top, add that as driver data in the
> > match arrays (both the ACPI and OF ones). Then have if statements
> > choose the correct init, read and report functions.
>
> How should I handle the version readout?
>
> Currently the driver has following info in its registers (starting
> from 0xf0):
>
> f0: 47 54 38 30 31 4e 49 5f 33 52 31 35 5f 31 41 56 GT801NI_3R15_1AV
>
>
> And there's another issue with deactivating interrupts. When I remove
> the goodix module, I get following traceback:
>
> [snip]
> WARNING: CPU: 0 PID: 381 at fs/proc/generic.c:552 remove_proc_entry+0x138/0x16c()
> remove_proc_entry: removing non-empty directory 'irq/50', leaking at least 'gt801x2'
> Modules linked in: goodix(-) rtl8192cu rtl_usb rtl8192c_common rtlwifi
This is an issue with the i2c core and not the driver; the offending
patch has been reverted as far as I can remember.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2015-04-05 18:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-04 21:08 [PATCH] input: goodix: RFC - implementing support for GT801x2 Priit Laes
2015-04-04 21:08 ` [PATCH] Input: goodix - preliminary support for GT801-2+1 Priit Laes
2015-04-05 16:04 ` Bastien Nocera
2015-04-05 17:06 ` Priit Laes
2015-04-05 18:43 ` Dmitry Torokhov [this message]
2015-04-08 14:24 ` Bastien Nocera
2015-04-05 23:56 ` Dmitry Torokhov
2015-04-08 14:25 ` Bastien Nocera
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=20150405184319.GA31564@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=hadess@hadess.net \
--cc=linux-input@vger.kernel.org \
--cc=plaes@plaes.org \
--cc=rydberg@bitmath.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).