From: Florian Echtler <floe@butterbrot.org>
To: hverkuil@xs4all.nl, linux-media@vger.kernel.org
Cc: linux-input@vger.kernel.org, modin@yuri.at,
Florian Echtler <floe@butterbrot.org>
Subject: [PATCH 1/4] add missing blob structure field for tag id
Date: Wed, 7 Feb 2018 14:00:35 +0100 [thread overview]
Message-ID: <1518008438-26603-2-git-send-email-floe@butterbrot.org> (raw)
In-Reply-To: <1518008438-26603-1-git-send-email-floe@butterbrot.org>
The SUR40 can recognize specific printed patterns directly in hardware;
this information (i.e. the pattern id) is present but currently unused
in the blob structure.
Signed-off-by: Florian Echtler <floe@butterbrot.org>
---
drivers/input/touchscreen/sur40.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/input/touchscreen/sur40.c b/drivers/input/touchscreen/sur40.c
index f16f835..8375b06 100644
--- a/drivers/input/touchscreen/sur40.c
+++ b/drivers/input/touchscreen/sur40.c
@@ -81,7 +81,10 @@ struct sur40_blob {
__le32 area; /* size in pixels/pressure (?) */
- u8 padding[32];
+ u8 padding[24];
+
+ __le32 tag_id; /* valid when type == 0x04 (SUR40_TAG) */
+ __le32 unknown;
} __packed;
--
2.7.4
next prev parent reply other threads:[~2018-02-07 13:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 13:00 [PATCH v3] add video controls for SUR40 driver Florian Echtler
2018-02-07 13:00 ` Florian Echtler [this message]
2018-02-07 13:00 ` [PATCH 2/4] add default settings and module parameters for video controls Florian Echtler
2018-02-07 13:20 ` Hans Verkuil
2018-02-07 13:00 ` [PATCH 3/4] add panel register access functions Florian Echtler
2018-02-07 13:00 ` [PATCH 4/4] add video control handlers using V4L2 control framework Florian Echtler
2018-02-07 13:22 ` Hans Verkuil
-- strict thread matches above, loose matches on Subject: below --
2018-02-08 8:43 [PATCH v4] add video controls for SUR40 driver Florian Echtler
2018-02-08 8:43 ` [PATCH 1/4] add missing blob structure field for tag id Florian Echtler
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=1518008438-26603-2-git-send-email-floe@butterbrot.org \
--to=floe@butterbrot.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-input@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=modin@yuri.at \
/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).