From: Marek Vasut <marex@denx.de>
To: Michael Gong <mksgong@gmail.com>, Nick Dyer <nick@shmanahar.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>, linux-input@vger.kernel.org
Subject: Re: [PATCH] Input: atmel_mxt_ts - support KoD knob
Date: Mon, 20 Jan 2025 10:27:39 +0100 [thread overview]
Message-ID: <2624fa66-a777-4931-9a06-f43c4ab433e5@denx.de> (raw)
In-Reply-To: <CAH6H9=T7a9DBKwi43qf7nodqM1Ghh6kY-LJYqvWBDQ6UrTD+0g@mail.gmail.com>
On 1/20/25 7:53 AM, Michael Gong wrote:
> Resending: Plain text mode:
Hi,
both emails made it through.
> Some clarifications:the two knobs on the display are configured to be
> predefined widget areas/shapes.
> In this case, two pushable knob dials with a predefined center area
> which acts as a push button.
> Current knobs report dents or an absolute position, relative data and
> graduations (although graduations are not well defined yet).
>
> Idea was to create two separate input devices (i.e. to associate all
> reports to these input devices) as the knobs are separately reporting
> wheel type data, although are part of the same touchscreen.
Indeed, I saw the downstream driver.
> Not clear what ABS_GAS event type is and assumed that REL_HWHEEL was
> more of a mouse related event code.
GAS is a gas pedal , like in a car , what would really be needed is
wheel2 code I think.
prev parent reply other threads:[~2025-01-20 9:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-23 19:03 [PATCH] Input: atmel_mxt_ts - support KoD knob Marek Vasut
2025-01-13 19:43 ` Dmitry Torokhov
2025-01-13 20:08 ` Marek Vasut
2025-01-16 1:01 ` Dmitry Torokhov
2025-01-16 2:48 ` Marek Vasut
2025-01-16 9:59 ` Nick Dyer
[not found] ` <CAH6H9=RjC4V1scV3A7=diixOXKde+Fd81ZhKGehtBGhBYS9pNQ@mail.gmail.com>
2025-01-20 6:53 ` Michael Gong
2025-01-20 9:27 ` Marek Vasut [this message]
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=2624fa66-a777-4931-9a06-f43c4ab433e5@denx.de \
--to=marex@denx.de \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=mksgong@gmail.com \
--cc=nick@shmanahar.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).