From: Oreste Salerno <oreste.salerno@tomtom.com>
To: linux-kernel@vger.kernel.org
Cc: linux-input@vger.kernel.org, fery@cypress.com,
dmitry.torokhov@gmail.com, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
devicetree@vger.kernel.org, oreste.salerno@tomtom.com
Subject: [PATCH v4 0/4] Add device tree support to the cyttsp driver
Date: Thu, 21 Jan 2016 20:21:12 +0100 [thread overview]
Message-ID: <cover.1453403916.git.oreste.salerno@tomtom.com> (raw)
Implement a number of updates for the cyttsp driver to be able to parse generic
ACPI/of/static properties and drop support for platform data (no platform data
user is present in the kernel tree).
---
Changes in v4:
Major rework based on Dmitry's review:
- Use device_property_read() functions instead of of_property()
- Use touchscreen_parse_properties to parse common properties
- Drop support for platform data
- Used devres managed allocations
Changes in v3:
- Rework binding names and descriptions
Changes in v2:
- Fix err_cast.cocci warning in patch 2/3
Oreste Salerno (4):
Input: cyttsp - use devres managed resource allocations
Input: cyttsp - check return value of input_mt_init_slots
Input: cyttsp - switch to using device properties
Input: cyttsp - perform hard reset of the chip during probe
.../bindings/input/touchscreen/cyttsp.txt | 95 ++++++++++
drivers/input/touchscreen/cyttsp_core.c | 197 +++++++++++++--------
drivers/input/touchscreen/cyttsp_core.h | 10 +-
drivers/input/touchscreen/cyttsp_i2c.c | 10 --
drivers/input/touchscreen/cyttsp_spi.c | 10 --
include/linux/input/cyttsp.h | 15 --
6 files changed, 231 insertions(+), 106 deletions(-)
create mode 100644 Documentation/devicetree/bindings/input/touchscreen/cyttsp.txt
--
1.9.1
next reply other threads:[~2016-01-21 19:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 19:21 Oreste Salerno [this message]
2016-01-21 19:21 ` [PATCH v4 1/4] Input: cyttsp - use devres managed resource allocations Oreste Salerno
[not found] ` <20e9f0188f07fc420912b3defa747303be3cf290.1453403916.git.oreste.salerno-Jdzig1fPfSTQT0dZR+AlfA@public.gmane.org>
2016-01-21 19:29 ` Dmitry Torokhov
2016-01-21 20:22 ` Oreste Salerno
2016-01-21 21:32 ` Dmitry Torokhov
2016-01-21 19:21 ` [PATCH v4 2/4] Input: cyttsp - check return value of input_mt_init_slots Oreste Salerno
2016-01-21 19:21 ` [PATCH v4 3/4] Input: cyttsp - switch to using device properties Oreste Salerno
[not found] ` <03a328d762d8ed654095d9a6edf648bc1c7fa262.1453403916.git.oreste.salerno-Jdzig1fPfSTQT0dZR+AlfA@public.gmane.org>
2016-01-21 19:25 ` Oreste Salerno
2016-01-21 19:35 ` Dmitry Torokhov
2016-01-21 20:44 ` Oreste Salerno
2016-01-21 21:33 ` Dmitry Torokhov
2016-01-21 19:21 ` [PATCH v4 4/4] Input: cyttsp - perform hard reset of the chip during probe Oreste Salerno
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=cover.1453403916.git.oreste.salerno@tomtom.com \
--to=oreste.salerno@tomtom.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=fery@cypress.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--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 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).