public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Bergmeier <abergmeier@gmx.net>
To: Andreas Bergmeier <abergmeier@gmx.net>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	linux-input@vger.kernel.org,
	USB mailing list <linux-usb@vger.kernel.org>,
	Alan Stern <stern@rowland.harvard.edu>,
	Jiri Kosina <jikos@kernel.org>,
	linux-leds@vger.kernel.org,
	Nestor Lopez Casado <nlopezcasad@logitech.com>
Subject: Re: Litra Glow on Linux
Date: Sun, 27 Nov 2022 12:04:09 +0100 (CET)	[thread overview]
Message-ID: <5ea1b921-d4b3-403c-64cd-58939571c638@9300> (raw)
In-Reply-To: <e6cb795-e8c4-4570-7a7b-3bbd133b98cb@9300>


On Sat, 19 Nov 2022, Andreas Bergmeier wrote:

> So after some tinkering I have code now that succeeds in retrieving state
> via sending reports once. After that all following sends time out.
> I am at a loss what I am doing wrong, tbh. RFC below.
I noticed that by default hidraw, hiddev and hid-input are loaded for
Glow. Probably because it exposes a Consumer Control page in Reports.
Is it possible that hid-input interferes with hid-logitech-hidpp?
I was trying to disable hid-input using
- HIDPP_QUIRK_NO_HIDINPUT
- hid_ignore_list

For the former it still seems to load hid-input.
For the latter it doesn't seem to load hid-logitech-hidpp.
I couldn't yet untangle all the hid driver indirections and loading.

  reply	other threads:[~2022-11-27 11:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 15:17 Litra Glow on Linux Alan Stern
2022-10-19 15:48 ` Bastien Nocera
2022-10-19 15:49 ` Bastien Nocera
2022-10-19 19:40   ` Andreas Bergmeier
2022-10-20 18:22 ` Andreas Bergmeier
2022-10-22 12:42 ` Andreas Bergmeier
2022-10-25  7:46   ` Benjamin Tissoires
2022-10-26 20:49     ` Andreas Bergmeier
2022-10-27  9:45       ` Benjamin Tissoires
2022-10-29  8:21         ` Andreas Bergmeier
2022-10-31  9:30           ` Benjamin Tissoires
2022-11-04  7:45             ` Andreas Bergmeier
2022-11-04 11:40               ` Pavel Machek
2022-11-09 20:27             ` Andreas Bergmeier
2022-11-10  3:29               ` Andreas Bergmeier
2022-11-10  9:22                 ` Benjamin Tissoires
2022-11-10 12:24                   ` Andreas Bergmeier
2022-11-10 13:39                     ` Benjamin Tissoires
2022-11-19 20:18                       ` Andreas Bergmeier
2022-11-27 11:04                         ` Andreas Bergmeier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-17 16:45 Andreas Bergmeier

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=5ea1b921-d4b3-403c-64cd-58939571c638@9300 \
    --to=abergmeier@gmx.net \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=nlopezcasad@logitech.com \
    --cc=stern@rowland.harvard.edu \
    /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