From: Jeff LaBundy <jeff@labundy.com>
To: dmitry.torokhov@gmail.com, robh+dt@kernel.org
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
Jeff LaBundy <jeff@labundy.com>
Subject: [PATCH 5/6] input: iqs269a: Make sliders two-dimensional
Date: Sun, 16 Aug 2020 16:14:26 -0500 [thread overview]
Message-ID: <1597612467-15093-6-git-send-email-jeff@labundy.com> (raw)
In-Reply-To: <1597612467-15093-1-git-send-email-jeff@labundy.com>
libinput rejects devices that define one axis without the orthogonal
axis, as well as devices for which either axis's resolution is zero.
To solve this problem, present a thin y-axis with a resolution equal
to one.
Signed-off-by: Jeff LaBundy <jeff@labundy.com>
---
drivers/input/misc/iqs269a.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/input/misc/iqs269a.c b/drivers/input/misc/iqs269a.c
index 04947f1..4a0e4ec 100644
--- a/drivers/input/misc/iqs269a.c
+++ b/drivers/input/misc/iqs269a.c
@@ -1377,6 +1377,8 @@ static int iqs269_input_init(struct iqs269_private *iqs269)
EV_KEY, BTN_TOUCH);
input_set_abs_params(iqs269->slider[i],
ABS_X, 0, 255, 0, 0);
+ input_set_abs_params(iqs269->slider[i],
+ ABS_Y, 0, 1, 0, 0);
}
error = input_register_device(iqs269->slider[i]);
--
2.7.4
next prev parent reply other threads:[~2020-08-16 21:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-16 21:14 [PATCH 0/6] Add support for slider gestures and OTP variants Jeff LaBundy
2020-08-16 21:14 ` [PATCH 1/6] dt-bindings: input: iqs269a: Add bindings for slider gestures Jeff LaBundy
2020-08-25 2:22 ` Rob Herring
2020-08-16 21:14 ` [PATCH 2/6] input: iqs269a: Add support " Jeff LaBundy
2020-08-16 21:14 ` [PATCH 3/6] dt-bindings: input: iqs269a: Add bindings for OTP variants Jeff LaBundy
2020-08-25 2:24 ` Rob Herring
2020-08-16 21:14 ` [PATCH 4/6] input: iqs269a: Add support " Jeff LaBundy
2020-08-16 21:14 ` Jeff LaBundy [this message]
2020-08-16 21:14 ` [PATCH 6/6] input: iqs269a: Disable channels before configuring them Jeff LaBundy
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=1597612467-15093-6-git-send-email-jeff@labundy.com \
--to=jeff@labundy.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--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).