All of lore.kernel.org
 help / color / mirror / Atom feed
From: Werner Sembach <werner@rdorf.de>
To: linux-input@vger.kernel.org
Subject: Re: Need information to implement correct handling of the GSP 370 wireless headset
Date: Fri, 7 Jul 2023 23:22:58 +0200	[thread overview]
Message-ID: <f26c2aab-7c89-d6e4-b8c1-f6740e08b034@rdorf.de> (raw)
In-Reply-To: <e01dbcd2-3ce3-ebaf-e685-3b89601ae55a@rdorf.de>

Am 07.07.23 um 23:12 schrieb Werner Sembach:
> Hi,
>
> The EPOS GSP 370 wireless headset has a volume control knob on the 
> headset. Turning this has 2 effects on Linux:
>
> - The volume gets adjusted in firmware
>
> - A volume up/down key event is sent to the OS and the volume is 
> adjustet on the OS level (the dongle registers both as a audio device 
> and an usb keyboard to do this)
>
> This double volume adjust is ofc not the intended behavior and induces 
> all kinds of wiredness, like the os is already displaying 100% volume 
> but you can still turn it higher because the firmware has not yet 
> reached max volume.
>
> Running Wireshark on Windows and Linux I recognized that Windows is 
> sending "URB_CONTROL out" events to the dongle on volume adjust, which 
> Linux doesn't, these events have a paylode that seems to encode a 
> volume value in 2 byte with little endianess.
>
> I'm unsure if I can attach pcap file or if it will get blocked in the 
> list so i will send them as a reply.
As I thought: The pcapng files are to big for the mailing list. When 
someone is interested let me know how I can send them (should I open a 
Bugzilla Ticket for it?).
>
> So my 2 questions are:
>
> - What are these USB "URB_CONTROL out" events? (Does not seem to be 
> HID reports?)
>
> - In which subsystem would I want to implement them? Or should this be 
> handled in userspace?
>
> Bast regards,
>
> Werner
>

  reply	other threads:[~2023-07-07 21:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07 21:12 Need information to implement correct handling of the GSP 370 wireless headset Werner Sembach
2023-07-07 21:22 ` Werner Sembach [this message]
2023-07-21  2:45   ` Rahul Rameshbabu
2023-07-21  8:50     ` Werner Sembach

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=f26c2aab-7c89-d6e4-b8c1-f6740e08b034@rdorf.de \
    --to=werner@rdorf.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.