mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean Young <sean@mess.org>
To: Alessandro Baldi <baldovic@virgilio.it>
Cc: mchehab@kernel.org, linux-media@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: imon: Add iMON VFD HID OEM v1.2 key mappings
Date: Mon, 18 May 2026 10:16:32 +0100	[thread overview]
Message-ID: <agrY8P7oYjUg7dZu@extorris.mess.org> (raw)
In-Reply-To: <20260517091415.3080-1-baldovic@virgilio.it>

On Sun, May 17, 2026 at 11:14:15AM +0200, Alessandro Baldi wrote:
> Add Vol+/Vol-/Mute panel button mappings for iMON VFD HID OEM v1.2.
> This version differs in the codes that generate the
> KEY_VOLUMEUP, KEY_VOLUMEDOWN and KEY_MUTE events.
> 
> Signed-off-by: Alessandro Baldi <baldovic@virgilio.it>

Thank you, patch applied.

Sean

> ---
> 
> Note: this is my first kernel contribution.
> Keycodes discovered by parsing USB packets with usbmon:
> - modprobe usbmon
> - cat /sys/kernel/debug/usb/usbmon/1u | grep Ii
> Tested on Thermaltake Mozart Sx case with LibreELEC media center.
> 
>  drivers/media/rc/imon.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/drivers/media/rc/imon.c b/drivers/media/rc/imon.c
> index 9bb27ba82..049a73b5f 100644
> --- a/drivers/media/rc/imon.c
> +++ b/drivers/media/rc/imon.c
> @@ -290,6 +290,10 @@ static const struct imon_usb_dev_descr imon_OEM_VFD = {
>  		{ 0x000100000000ffeell, KEY_VOLUMEUP },
>  		{ 0x010000000000ffeell, KEY_VOLUMEDOWN },
>  		{ 0x000000000100ffeell, KEY_MUTE },
> +		/* iMON VFD HID OEM v1.2 */
> +		{ 0x000000000a00ffeell, KEY_VOLUMEUP },
> +		{ 0x000000000b00ffeell, KEY_VOLUMEDOWN },
> +		{ 0x000000000c00ffeell, KEY_MUTE },
>  		/* 0xffdc iMON MCE VFD */
>  		{ 0x00010000ffffffeell, KEY_VOLUMEUP },
>  		{ 0x01000000ffffffeell, KEY_VOLUMEDOWN },
> -- 
> 2.34.1

      reply	other threads:[~2026-05-18  9:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-17  9:14 Alessandro Baldi
2026-05-18  9:16 ` Sean Young [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=agrY8P7oYjUg7dZu@extorris.mess.org \
    --to=sean@mess.org \
    --cc=baldovic@virgilio.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@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

all inboxes | Powered by JetHome®