All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Priit Laes <plaes@plaes.org>,
	linux-input@vger.kernel.org, Henrik Rydberg <rydberg@bitmath.org>
Subject: Re: [PATCH] Input: goodix - preliminary support for GT801-2+1
Date: Wed, 08 Apr 2015 16:25:10 +0200	[thread overview]
Message-ID: <1428503110.28443.13.camel@hadess.net> (raw)
In-Reply-To: <20150405235608.GB5313@dtor-ws>

On Sun, 2015-04-05 at 16:56 -0700, Dmitry Torokhov wrote:
> On Sun, Apr 05, 2015 at 06:04:24PM +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.
> > 
> > I would think that that would grow the driver by a further 50 
> > lines, 
> > which would certainly be acceptable.
> > 
> > Don't forget to add your name to the copyright header mentioning 
> > you're the author for the 8xx support :)
> > 
> > > Signed-off-by: Priit Laes <plaes@plaes.org>
> > 
> > There's really no need to sign it off if you know it's not going 
> > to be 
> > accepted upstream ;)
> 
> Actually I think it is still useful: that means that somebody else 
> can
> use the patch as a base for their work without any concerns even if
> original author did not see it through upstream acceptance for some
> reason.


Right, fair enough.

      reply	other threads:[~2015-04-08 14:26 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
2015-04-08 14:24       ` Bastien Nocera
2015-04-05 23:56     ` Dmitry Torokhov
2015-04-08 14:25       ` Bastien Nocera [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=1428503110.28443.13.camel@hadess.net \
    --to=hadess@hadess.net \
    --cc=dmitry.torokhov@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.