From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: linux-input@vger.kernel.org
Cc: linux-rpi-kernel@lists.infradead.org, stefan.wahren@i2se.com,
eric@anholt.net, agraf@suse.de,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh@kernel.org>,
Eugen Hristev <eugen.hristev@microchip.com>,
Hans de Goede <hdegoede@redhat.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Masanari Iida <standby24x7@gmail.com>,
Zhu Yi <yi.zhu5@cn.bosch.com>,
Corentin Labbe <clabbe.montjoie@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH RFC 0/2] input: driver for RPi's official 7" touchscreen
Date: Wed, 5 Dec 2018 23:09:01 +0100 [thread overview]
Message-ID: <20181205220902.27682-1-nsaenzjulienne@suse.de> (raw)
This small series adds support for Raspberry pi's 7" touchscreen. Which
alongside with the backlight driver are the last devices needed to have
a functional touchscreen upstream.
With this setup the board's VC4 firmware takes care of communicating
with the touch chip and provides data though a shared memory area
provided by the driver. The driver takes care of polling the firmware
whenever at around 60Hz since there is no interrupt line available.
The 1.0 revision of the touchscreen is based on the ft5426 chip.
Technically, with some changes in edt-ft54x4.c we should be able to
access the data directly through I2C. Yet this bus is meant to be owned
by RPi's firmware and might access it anytime. For example, to
configure RPi's camera device. As sharing the bus master interface is
not possible a series of alternatives have been tested unsuccessfully
[1]. It seems that we'll be unable to access the chip directly in a
"clean" way which leaves us with this firmware based solution.
The driver was rewritten based on the one available on the downstream
Raspberry Pi kernel tree: https://github.com/raspberrypi/linux/.
This series is based on v4.20-rc5 and was tested on a RPi 3 B+.
[1] https://lists.infradead.org/pipermail/linux-rpi-kernel/2018-December/008444.html
===
Nicolas Saenz Julienne (2):
input: add official Raspberry Pi's 7" touchscreen driver
Input: raspberrypi-ts - add devicetree binding documentation
.../touchscreen/raspberrypi,firmware-ts.txt | 25 ++
drivers/input/touchscreen/Kconfig | 12 +
drivers/input/touchscreen/Makefile | 1 +
drivers/input/touchscreen/raspberrypi-ts.c | 252 ++++++++++++++++++
4 files changed, 290 insertions(+)
create mode 100644 Documentation/devicetree/bindings/input/touchscreen/raspberrypi,firmware-ts.txt
create mode 100644 drivers/input/touchscreen/raspberrypi-ts.c
--
2.19.2
next reply other threads:[~2018-12-05 22:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 22:09 Nicolas Saenz Julienne [this message]
2018-12-05 22:09 ` [PATCH RFC 1/2] input: add official Raspberry Pi's 7" touchscreen driver Nicolas Saenz Julienne
2018-12-09 4:43 ` Dmitry Torokhov
2018-12-05 22:09 ` [PATCH RFC 2/2] Input: raspberrypi-ts - add devicetree binding documentation Nicolas Saenz Julienne
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=20181205220902.27682-1-nsaenzjulienne@suse.de \
--to=nsaenzjulienne@suse.de \
--cc=Jonathan.Cameron@huawei.com \
--cc=agraf@suse.de \
--cc=clabbe.montjoie@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=eric@anholt.net \
--cc=eugen.hristev@microchip.com \
--cc=hdegoede@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=robh@kernel.org \
--cc=standby24x7@gmail.com \
--cc=stefan.wahren@i2se.com \
--cc=yi.zhu5@cn.bosch.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
all inboxes | Powered by JetHome®