From: Eric Anholt <eric@anholt.net>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
Henrik Rydberg <rydberg@bitmath.org>
Cc: linux-rpi-kernel@lists.infradead.org, stefan.wahren@i2se.com,
agraf@suse.de, afaerber@suse.com,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Corentin Labbe <clabbe.montjoie@gmail.com>,
Mark Jonas <mark.jonas@de.bosch.com>,
Masanari Iida <standby24x7@gmail.com>,
Heiko Schocher <hs@denx.de>, Hans de Goede <hdegoede@redhat.com>,
Eugen Hristev <eugen.hristev@microchip.com>,
Zhu Yi <yi.zhu5@cn.bosch.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH v2 2/2] input: add official Raspberry Pi's touchscreen driver
Date: Thu, 20 Dec 2018 10:39:07 -0800 [thread overview]
Message-ID: <87r2ecdovo.fsf@anholt.net> (raw)
In-Reply-To: <20181211112408.9524-3-nsaenzjulienne@suse.de>
[-- Attachment #1: Type: text/plain, Size: 514 bytes --]
Nicolas Saenz Julienne <nsaenzjulienne@suse.de> writes:
> Add's support to Raspberry Pi's 7" Touch device. Instead of using a
> conventional bus all information is copied into a memory mapped area by
> RPi's firmware.
>
> Based on the driver found in RPi's kernel repository.
>
> Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
While I wish we could just have a native driver instead, it does make
sense to have this driver upstream given the constraints.
Acked-by: Eric Anholt <eric@anholt.net>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-12-20 18:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 11:23 [PATCH v2 0/2] input: driver for RPi's official 7" touchscreen Nicolas Saenz Julienne
2018-12-11 11:23 ` [PATCH v2 1/2] dt-bindings: input: Add Raspberry Pi Touchscreen Nicolas Saenz Julienne
2018-12-18 16:52 ` Rob Herring
2018-12-11 11:23 ` [PATCH v2 2/2] input: add official Raspberry Pi's touchscreen driver Nicolas Saenz Julienne
2018-12-20 18:39 ` Eric Anholt [this message]
2018-12-20 19:12 ` Nicolas Saenz Julienne
2018-12-21 8:49 ` Dmitry Torokhov
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=87r2ecdovo.fsf@anholt.net \
--to=eric@anholt.net \
--cc=Jonathan.Cameron@huawei.com \
--cc=afaerber@suse.com \
--cc=agraf@suse.de \
--cc=clabbe.montjoie@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=eugen.hristev@microchip.com \
--cc=hdegoede@redhat.com \
--cc=hs@denx.de \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mark.jonas@de.bosch.com \
--cc=nsaenzjulienne@suse.de \
--cc=rydberg@bitmath.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