Linux Input/HID development
 help / color / mirror / Atom feed
From: Helge Bahmann <hcb@chaoticmind.net>
To: Jiri Kosina <jikos@kernel.org>,
	linux-input@vger.kernel.org, Basavaraj Natikar <bnatikar@amd.com>
Cc: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Subject: [PATCH 0/2] asus vivobook tablet mode
Date: Tue, 21 Jul 2026 16:28:30 +0200	[thread overview]
Message-ID: <5234335.GXAFRqVoOG@zephyr> (raw)
In-Reply-To: <ecadaac8-e222-420a-ac5b-4d529fb3317e@amd.com>

Hi Basavaraj,

Here the two patches implementing the split hid/input
driver for the tablet mode support. I mulled over what 
exactly to use as report descriptor in the hid driver, and
there is no clean and easy solution -- I hope this is what
you had in mind? I could not figure a way how to do
a stand-alone input driver without doing any hid indirection,
as I simply could not find a way to bind to the physical
dev twice.

Please let me know in comments to the patches how you
would like to proceed.

Thanks!
Helge



  parent reply	other threads:[~2026-07-21 14:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27  6:22 [PATCH] amd-sfh-hid: tablet mode switch and asus quirk Helge Bahmann
2026-05-12 16:06 ` Jiri Kosina
2026-05-12 17:09   ` Basavaraj Natikar
2026-05-14  7:59   ` Helge Bahmann
2026-06-10 17:12     ` Basavaraj Natikar
2026-06-12  4:22       ` Helge Bahmann
2026-07-21 14:28       ` Helge Bahmann [this message]
2026-07-21 17:52         ` [PATCH 0/2] asus vivobook tablet mode Basavaraj Natikar
2026-07-21 14:29       ` [PATCH 1/2] amd-sfh-hid: tablet mode hid report and asus quirk Helge Bahmann
2026-07-21 14:47         ` sashiko-bot
2026-07-21 14:29       ` [PATCH 2/2] amd-sfh-tabletmode: interpret sfh tablet mode hid report Helge Bahmann
2026-07-21 14:41         ` sashiko-bot
2026-08-03 17:33         ` Jiri Kosina
2026-08-03 17:42           ` Basavaraj Natikar
2026-08-03 18:23             ` Jiri Kosina
2026-06-10 16:33 ` [PATCH] amd-sfh-hid: tablet mode switch and asus quirk Jiri Kosina

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=5234335.GXAFRqVoOG@zephyr \
    --to=hcb@chaoticmind.net \
    --cc=Basavaraj.Natikar@amd.com \
    --cc=bnatikar@amd.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.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