Linux Input/HID development
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: "Kateřina Medvědová" <k8ie@mcld.eu>,
	"Erik Håkansson" <erikhakan@gmail.com>
Cc: bentiss@kernel.org, jikos@kernel.org, lains@riseup.net,
	 linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] HID: logitech: add Bolt receiver support for Logitech HID++ devices
Date: Thu, 30 Jul 2026 10:38:02 +0200	[thread overview]
Message-ID: <14807a258220aaa2bf4ae5020b452c7da4201168.camel@hadess.net> (raw)
In-Reply-To: <54844d1b-636c-4896-8994-f4e960e57944@mcld.eu>

On Tue, 2026-07-14 at 12:32 +0200, Kateřina Medvědová wrote:
> Hi,
> 
> Just tested V1 again with both of the receiver versions I have on
> hand 
> and the input issues I described happen on both.
> 
> btw, thank you for pointing out that you can check the FW version in 
> fwupd. This greatly simplified testing.
> 
> I do have one find -- when a device gets powered off (yanked battery,
> switch moved to the off position, switching devices), the battery
> stays 
> in upower. Unifying also does this, disconnected devices stay.

Unifying definitely didn't use to do this, I don't know whether it's a
problem in upower or the kernel.

"udevadm monitor -k -p" correctly shows the battery switching between
POWER_SUPPLY_ONLINE=0 and POWER_SUPPLY_ONLINE=1 when turning the device
off. Not sure whether that's what it used to do.

If someone has time, please test with older versions of upower (I would
say go back to 1.90.2 and start bisecting).

>  Either
> this was intentional or a bug. Either way the behavior is consistent 
> with the existing code and isn't introduced by your changes. I'm just
> not sure what the correct behavior should be. Sorry if this pollutes
> the 
> discussion, I'm completely new to the LKML.
> 
> I'm not sure what else I could try, I'll keep your V2 on my system
> and 
> let you know if any issues pop up.
> 
> Regards,
> Kate
> 
> On 7/14/26 2:54 AM, Erik Håkansson wrote:
> > Hi,
> > 
> > Thank you very much for your help.
> > 
> > Unfortunately I don't have a Windows system easily accessible, so I
> > can't check my firmware version in Options+.
> > fwupdmgr says:
> > > Current version:    MPR05.03_B0020
> > so perhaps that means 5.03.20.
> > 
> > Let me know if anything pops up if you dig some more,
> > Thanks,
> > Erik

  parent reply	other threads:[~2026-07-30  8:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-12  0:30 [PATCH 0/1] HID: logitech: add Bolt receiver support for Logitech HID++ devices Erik Håkansson
2026-07-12  0:30 ` [PATCH 1/1] " Erik Håkansson
2026-07-12 18:03   ` Kateřina Medvědová
2026-07-13 20:10     ` Erik Håkansson
2026-07-13 20:12     ` [PATCH v2 0/1] " Erik Håkansson
2026-07-13 20:12       ` [PATCH v2 1/1] " Erik Håkansson
2026-07-13 20:24         ` sashiko-bot
2026-07-13 21:09         ` Kateřina Medvědová
2026-07-14  0:54           ` Erik Håkansson
2026-07-14 10:32             ` Kateřina Medvědová
2026-07-14 15:33               ` Erik Håkansson
2026-07-30  8:38               ` Bastien Nocera [this message]
2026-08-01 23:25                 ` Erik Håkansson
2026-07-14  0:50         ` Erik Håkansson
2026-07-30  8:36         ` Bastien Nocera
2026-08-01 23:18           ` Erik Håkansson

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=14807a258220aaa2bf4ae5020b452c7da4201168.camel@hadess.net \
    --to=hadess@hadess.net \
    --cc=bentiss@kernel.org \
    --cc=erikhakan@gmail.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