Linux Input/HID development
 help / color / mirror / Atom feed
From: "Erik Håkansson" <erikhakan@gmail.com>
To: greyxor@protonmail.com, "Filipe Laíns" <lains@riseup.net>,
	"Jiri Kosina" <jikos@kernel.org>,
	"Benjamin Tissoires" <bentiss@kernel.org>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Kateřina Medvědová" <k8ie@mcld.eu>
Subject: Re: [PATCH] HID: logitech-dj: forward Bolt receiver input to the dj child device
Date: Tue, 1 Sep 2026 21:29:02 +0200	[thread overview]
Message-ID: <5eca65ce-d1f5-426b-8148-30ae151a369e@gmail.com> (raw)
In-Reply-To: <20260901-bolt-scroll-fix-v1-1-58bca7ae487f@protonmail.com>

Hi!

> Interface 0 is the keyboard endpoint, interface 1 the mouse endpoint and
> interface 2 carries DJ/HID++, which is the same layout as the other
> HID++ receivers. Set no_dj_interfaces to 3 and drop the special case, so
> interfaces 0 and 1 are claimed by the dj driver and their reports get
> forwarded to the child, where the multiplier is applied.

Thanks for finding this!
I can confirm that my MX Keys Business work fine after your patch.
However, your patch basically reverts to what I had in v1 of my patch.
The reason for the change was that Katerina Medvedova reported that
without the special treatment for Bolt, her mouse became very
sensitive, including phantom scrolls, and her keypresses were scrambled.

> Bolt support was tested with a keyboard, and a keyboard has no wheel
> multiplier to get wrong, which is probably why this was missed.

Katerina, you tested with a mouse and two different keyboards, I believe?
Can you perhaps test again with this patch to see if your issues remain
or if there was something else that caused it.

Best regards,
Erik Håkansson


      parent reply	other threads:[~2026-09-01 19:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01 16:22 [PATCH] HID: logitech-dj: forward Bolt receiver input to the dj child device Grégoire Stein via B4 Relay
2026-09-01 16:37 ` sashiko-bot
2026-09-01 17:55   ` GreyXor
2026-09-01 19:29 ` Erik Håkansson [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=5eca65ce-d1f5-426b-8148-30ae151a369e@gmail.com \
    --to=erikhakan@gmail.com \
    --cc=bentiss@kernel.org \
    --cc=greyxor@protonmail.com \
    --cc=jikos@kernel.org \
    --cc=k8ie@mcld.eu \
    --cc=lains@riseup.net \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@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