On Fri, 8 Sep 2017, vpalatin@xxxxxxxxxx wrote: > Re-sending (seems I forgot the HTML subpart that linux-input doesn't like) > > On Fri, Sep 8, 2017 at 3:13 PM, Jiri Kosina <jikos@xxxxxxxxxx> wrote: > > > > On Tue, 5 Sep 2017, nolsen@xxxxxxxxx wrote: > > > > > From: Niels Skou Olsen <nolsen@xxxxxxxxx> > > > > > > Two Jabra speakerphone devices were added to the ignore list in 2013 > > > because, at the time, the device HID interfaces didn't work well > > > with > > > kernel usbhid driver, and could reportedly cause volume key event > > > storm. > > > > Also apparently there was an userspace application that made use of > > these keys, and required the usbhid driver to be unbound from them. > > > > How come this is not the case any more? I can't really tell why, but it could be that our firmware has "improved" since 2013, and maybe also the Linux drivers and user mode stuff like PulseAudio have improved the situation. Anyway, I don't see the volume event storm issue when I test on a Ubuntu desktop with patched 4.4 and 4.13 kernels, and our firmware SPEAK410/1.8.0 and SPEAK510/2.10.0. > On our side, we are still using a custom userspace for the Jabra speakers (ie the > jabra_vold daemon: > https://chromium.googlesource.com/chromiumos/platform/jabra_vold/+/master > plus some direct USB interfacing in a Chrome app). > while If somebody is using the device another way, we can blacklist it or detach it on > our side in the future, I'm somewhat surprised that it's working well through the HID > interface with the Jabra speakerphone 510. Even if there is no longer any basic > breakage, in my experience there are other challenges to overcome with the 510 > firmware (at least the one I had on my devices) e.g. for the volume key to work more > than once, you need to do a precise sequence on the USB audio interface every time > one of the volume key is released. > Do you have another kernel driver for this ? a userspace software ? Thank you for your input, Vincent. As mentioned above I can't reproduce the volume event storm. I can, however, reproduce the issue you mention, that our device only emits an event for the first volume key press. We have a new firmware fixing that, so that volume keys now behave sanely on Linux. I would be happy to send you the new firmware, if you could find the time to try it out with ChromiumOS. Just let me know. Could we remove the blacklisting even if the current firmware behaves a bit "weird" with regard to volume button handling? I don't think this quirk is severe enough to warrant the complete blacklisting. As mentioned we have a new firmware coming out now that fixes it. And if ChromiumOS intends to continue with jabra_vold and blacklisting in the future, I guess there is no conflict? Thanks, Niels **** GN GROUP NOTICE - AUTOMATICALLY INSERTED**** The information in this e-mail (including attachments, if any) is considered confidential and is intended only for the recipient(s) listed above. Any review, use, disclosure, distribution or copying of this e-mail is prohibited except by or on behalf of the intended recipient. If you have received this email in error, please notify me immediately by reply e-mail, delete this e-mail, and do not disclose its contents to anyone. Any opinions expressed in this e-mail are those of the individual and not necessarily the GN group. Thank you. ******************** DISCLAIMER END ************************ ��.n��������+%������w��{.n�����{��)��^n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�
