All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Marek Vasut <marex@denx.de>
Cc: linux-input@vger.kernel.org, Michael <mksgong@gmail.com>,
	Nick Dyer <nick@shmanahar.org>
Subject: Re: [PATCH] Input: atmel_mxt_ts - support KoD knob
Date: Mon, 13 Jan 2025 11:43:00 -0800	[thread overview]
Message-ID: <Z4VsxKJ56jqQnZGr@google.com> (raw)
In-Reply-To: <20241223190416.52871-1-marex@denx.de>

On Mon, Dec 23, 2024 at 08:03:24PM +0100, Marek Vasut wrote:
> Add support for T152 KoD knob events [1]. The KoD touch controller
> family supports up to two knobs attached to the glass. Each knob can
> be turned in either direction and the touch controller processes the
> event and reports the knob position for each knob. Each knob is also
> pressure sensitive, the pressure is reported as well. Each knob also
> supports center press and additional buttons, which are reported as
> BTN_0/BTN_1 for the center press for each knob, and BTN_A/BTN_B for
> the additional buttons on the knob.
> 
> The knob is similar to Dell Canvas 27 knob already supported by
> hid-multitouch, except it is non-removable and there can be up to
> two such knobs .
> 
> This implementation is extracted and heavily reworked from Atmel
> downstream patchset work by Michael <mksgong@gmail.com> from [2]
> branch master as of commit 9c77fbf32982 ("Merge pull request #35
> from atmel-maxtouch/20240103_HA_protocol_fixes").
> 
> [1] https://www.microchip.com/en-us/products/touch-and-gesture/maxtouch-touchscreen-controllers/kod-family
> [2] https://github.com/atmel-maxtouch/maXTouch_linux
> 
> Signed-off-by: Marek Vasut <marex@denx.de>
> ---
> Note: I am not sure whether reporting the second wheel as GAS/REL_HWHEEL
>       is the right thing to do, I don't think it is. Maybe there is some
>       better way to handle multiple knobs ?

How about creating separate input devices for these?

Thanks.

-- 
Dmitry

  reply	other threads:[~2025-01-13 19:43 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 [this message]
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

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=Z4VsxKJ56jqQnZGr@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=marex@denx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.