From: Rob Herring <robh@kernel.org>
To: Anthony Kim <anthony.kim@hideep.com>
Cc: dmitry.torokhov@gmail.com, mark.rutland@arm.com,
rydberg@bitmath.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] Input: add support for HiDeep touchscreen
Date: Tue, 22 Aug 2017 19:07:48 -0500 [thread overview]
Message-ID: <20170823000748.t6hgghj7udpm6nzb@rob-hp-laptop> (raw)
In-Reply-To: <1503392618-26853-1-git-send-email-anthony.kim@hideep.com>
On Tue, Aug 22, 2017 at 06:03:38PM +0900, Anthony Kim wrote:
> The HiDeep touchscreen device is a capacitive multi-touch controller
> mainly for multi-touch supported devices use. It use I2C interface for
> communication to IC and provide axis X, Y, Z locations for ten finger
> touch through input event interface to userspace.
>
> It support the Crimson and the Lime two type IC. They are different
> the number of channel supported and FW size. But the working protocol
> is same.
>
> Signed-off-by: Anthony Kim <anthony.kim@hideep.com>
> ---
> .../bindings/input/touchscreen/hideep.txt | 39 +
> .../devicetree/bindings/vendor-prefixes.txt | 1 +
Acked-by: Rob Herring <robh@kernel.org>
> drivers/input/touchscreen/Kconfig | 11 +
> drivers/input/touchscreen/Makefile | 1 +
> drivers/input/touchscreen/hideep_core.c | 1294 ++++++++++++++++++++
> drivers/input/touchscreen/hideep_core.h | 221 ++++
> 6 files changed, 1567 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/input/touchscreen/hideep.txt
> create mode 100644 drivers/input/touchscreen/hideep_core.c
> create mode 100644 drivers/input/touchscreen/hideep_core.h
next prev parent reply other threads:[~2017-08-23 0:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 6:19 [PATCH] Input: add support for HiDeep touchscreen Anthony Kim
[not found] ` <1499235588-32219-1-git-send-email-anthony.kim-7TZDMcjUQMzQT0dZR+AlfA@public.gmane.org>
2017-07-10 1:17 ` Rob Herring
2017-07-12 5:24 ` Anthony Kim
[not found] ` <1499837054-4659-1-git-send-email-anthony.kim-7TZDMcjUQMzQT0dZR+AlfA@public.gmane.org>
2017-07-17 17:31 ` Rob Herring
2017-07-20 0:22 ` Anthony Kim
[not found] ` <1500510154-6661-1-git-send-email-anthony.kim-7TZDMcjUQMzQT0dZR+AlfA@public.gmane.org>
2017-07-24 19:52 ` Rob Herring
2017-07-25 6:53 ` Anthony Kim
[not found] ` <1500965607-2446-1-git-send-email-anthony.kim-7TZDMcjUQMzQT0dZR+AlfA@public.gmane.org>
2017-08-03 17:50 ` Rob Herring
2017-08-09 7:54 ` Anthony Kim
2017-08-09 23:49 ` Dmitry Torokhov
2017-08-10 8:01 ` Anthony Kim
2017-08-22 9:03 ` Anthony Kim
2017-08-23 0:07 ` Rob Herring [this message]
2017-08-31 6:51 ` Dmitry Torokhov
2017-09-11 7:27 ` Anthony Kim
2017-09-12 14:17 ` Rob Herring
2017-09-13 7:50 ` kbuild test robot
2017-09-13 8:51 ` kbuild test robot
2017-09-14 4:36 ` Anthony Kim
2017-09-14 18:51 ` Dmitry Torokhov
2017-09-18 19:03 ` Rob Herring
2017-09-26 1:42 ` Anthony Kim
2017-09-26 3:28 ` Anthony Kim
2017-09-26 3:30 ` Anthony Kim
-- strict thread matches above, loose matches on Subject: below --
2017-07-11 8:01 김태영
[not found] ` <CA+d1ZXLAVrWHpgOzQMtWzPN9kz0=EdAxa7gKE=UxMbzVms3Npg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-07-17 17:27 ` Rob Herring
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=20170823000748.t6hgghj7udpm6nzb@rob-hp-laptop \
--to=robh@kernel.org \
--cc=anthony.kim@hideep.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rydberg@bitmath.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