linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Henrik Rydberg" <rydberg@euromail.se>
To: Ferruh Yigit <fery@cypress.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Kevin McNeely <kev@cypress.com>,
	Phil Warkentin <pwar@cypress.com>,
	Javier Martinez Canillas <javier@dowhile0.org>,
	Shawn Landden <shawnlandden@gmail.com>,
	Ashish Jangam <ashish.jangam@kpitcummins.com>,
	Olivier Sobrie <olivier@sobrie.be>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Input: cyttsp4 - driver for Cypress TMA4XX touchscreen devices
Date: Fri, 14 Sep 2012 20:46:36 +0200	[thread overview]
Message-ID: <20120914184636.GA2976@polaris.bitmath.org> (raw)
In-Reply-To: <1347644917-13269-1-git-send-email-fery@cypress.com>

Hi Ferruh,

> This driver is for Cypress TrueTouch(tm) Standard Product controllers,
> Generation4 devices.
> 
> This is second version of driver, code re-structured to match with
> existing Generation3 driver code.

To integrate with the existing gen3 driver is clearly not the same as
creating a parallel set of files, which obviously share a lot of code
with the gen3 code.

For instance, the i2c transfer layer seems more or less identical to
the existing one; just look at cyttsp_i2c_write_block_data() versus
cyttsp4_i2c_write_block_data(). If different generations of device
data cannot even be transported through the same _generic_ interface,
something is clearly not right.

You can't seriously expect anyone to want to maintain one set of files
for every new version. Please make sure to build on what is already
there.

Thanks.
Henrik

  parent reply	other threads:[~2012-09-14 18:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Ferruh Yigit <fery@cypress.com>
2012-08-07 13:09 ` [PATCH 1/4] Input: cyttsp4 - bus driver for Cypress TMA4XX touchscreen devices Ferruh Yigit
2012-08-07 20:05   ` Javier Martinez Canillas
2012-08-08  5:53     ` Ferruh Yigit
2012-08-24 13:06   ` Ferruh Yigit
2012-08-24 17:34     ` Henrik Rydberg
     [not found]       ` <503B099A.6010807@cypress.com>
2012-09-12 13:16         ` Ferruh Yigit
2012-09-12 13:34           ` Henrik Rydberg
2012-08-07 13:09 ` [PATCH 2/4] Input: cyttsp4 - core " Ferruh Yigit
2012-08-24 14:21   ` Michal Marek
2012-08-27  5:49     ` Ferruh Yigit
2012-08-07 13:10 ` [PATCH 3/4] Input: cyttsp4 - MultiTouch " Ferruh Yigit
2012-08-07 13:10 ` [PATCH 4/4] Input: cyttsp4 - I2C " Ferruh Yigit
2012-09-14 17:48 ` [PATCH v2 0/3] Input: cyttsp4 - " Ferruh Yigit
2012-09-14 17:48   ` [PATCH v2 1/3] Input: cyttsp4 - core " Ferruh Yigit
2012-09-14 17:48   ` [PATCH v2 2/3] Input: cyttsp4 - I2C " Ferruh Yigit
2012-09-14 17:48   ` [PATCH v2 3/3] Input: cyttsp4 - SPI " Ferruh Yigit
2012-09-14 18:46   ` Henrik Rydberg [this message]
2012-09-15 15:42     ` [PATCH v2 0/3] Input: cyttsp4 - " Javier Martinez Canillas
2012-09-19 12:02       ` Ferruh Yigit
2012-09-19 11:53     ` Ferruh Yigit

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=20120914184636.GA2976@polaris.bitmath.org \
    --to=rydberg@euromail.se \
    --cc=ashish.jangam@kpitcummins.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=fery@cypress.com \
    --cc=javier@dowhile0.org \
    --cc=kev@cypress.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olivier@sobrie.be \
    --cc=pwar@cypress.com \
    --cc=shawnlandden@gmail.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;
as well as URLs for NNTP newsgroup(s).