All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@samsung.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Rob Herring <robh+dt@kernel.org>
Cc: Javier Martinez Canillas <javier@dowhile0.org>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	linux-input@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Andi Shyti <andi.shyti@samsung.com>,
	Andi Shyti <andi@etezian.org>
Subject: [PATCH v4 0/2] STM FingerTip S touchscreen support for TM2 board
Date: Wed, 31 May 2017 15:59:13 +0900	[thread overview]
Message-ID: <20170531065915.15695-1-andi.shyti@samsung.com> (raw)
In-Reply-To: CGME20170531065928epcas1p20b5ee8e7d3c74670fda56cb1ed4ca06e@epcas1p2.samsung.com

Hi,

this patchset provides support for the ST-Microelectronics
FingerTip S touchscreen device.

It's tested on top of mainline kernel on TM2 and TM2e boards.

Thanks,
Andi

Changelog V3-V4
===============
V3: https://marc.info/?l=linux-kernel&m=149062016401170&w=2
After an offline discussion, I applied some changes suggested by
Dmitry.

 - some cosmetic changes
 - interrupt gets disabled explicitly instead of using
   IRQ_NOAUTOEN
 - cleaner management of the input reports
 - the parsing of the event has been split into two major switch
   chunks, this might cause some event id overlapping, but the
   probability is quite rare

Changelog V2-V3
===============
V2: https://marc.info/?l=linux-kernel&m=148669314305915&w=2

 - fixed multi touch broken protocol reported by Chanwoo;
 - disabled irqs at the registration by setting the IRQ_NOAUTOEN
   flag, as suggested by Andrzej;
 - changed the interrupt handling policy: in the V1 and V2 the
   events were read one by one (8 each), this was increasing the
   overhead. Now all the events are read in a single operation,
   but because the stack is deep 32 events (256bytes, 32*8), it's
   impossible to use the smbus protocol. The i2c_transfer()
   functions is used instead;
 - random code changes;
 - patch 3 in the V1 and V2 patchset has been omitted because
   Krzysztof already merged it.

Changelog V1-V2
===============
V1: https://marc.info/?l=linux-kernel&m=148466204431327&w=2

 - fixed Javier's, Krzysztof's and Dmitry's reviews
 - added Javier's review tag on patch 1 and 3
 - the main difference of the driver from v2 is that the driver
   generates only one input interface instead of two (one for the
   touchscreen and one for the touchkeys). The job of filtering
   the events is demanded to userspace applications that are
   accessing the device. This is done by making an ioctl call:

	ioctl(fd, EVIOCSMASK, &mask);

   where 'mask' is an 'input_mask' structure that contains the type
   variable of the EV_* that needs to be filtered out.

Andi Shyti (2):
  Input: add STMicroelectronics FingerTip touchscreen driver
  Input: add support for the STMicroelectronics FingerTip touchscreen

 .../bindings/input/touchscreen/st,stmfts.txt       |  43 ++
 drivers/input/touchscreen/Kconfig                  |  11 +
 drivers/input/touchscreen/Makefile                 |   1 +
 drivers/input/touchscreen/stmfts.c                 | 823 +++++++++++++++++++++
 4 files changed, 878 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/input/touchscreen/st,stmfts.txt
 create mode 100644 drivers/input/touchscreen/stmfts.c

-- 
2.11.0

       reply	other threads:[~2017-05-31  6:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170531065928epcas1p20b5ee8e7d3c74670fda56cb1ed4ca06e@epcas1p2.samsung.com>
2017-05-31  6:59 ` Andi Shyti [this message]
     [not found]   ` <CGME20170531065928epcas1p2b6473d8eb979258cda797bd2664b7680@epcas1p2.samsung.com>
2017-05-31  6:59     ` [PATCH v4 1/2] Input: add STMicroelectronics FingerTip touchscreen driver Andi Shyti
2017-05-31  6:59       ` Andi Shyti
     [not found]   ` <CGME20170531065929epcas5p475bca54e20576338815d89526996653e@epcas5p4.samsung.com>
2017-05-31  6:59     ` [PATCH v4 2/2] Input: add support for the STMicroelectronics FingerTip touchscreen Andi Shyti

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=20170531065915.15695-1-andi.shyti@samsung.com \
    --to=andi.shyti@samsung.com \
    --cc=andi@etezian.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=javier@dowhile0.org \
    --cc=krzk@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.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.