On Fri, May 6, 2022 at 12:04 AM Vicki Pfau <vi@xxxxxxxxxxx> wrote: > > Hello, > > On 5/5/22 01:57, Benjamin Tissoires wrote: > > On Thu, Apr 28, 2022 at 12:52 AM Vicki Pfau <vi@xxxxxxxxxxx> wrote: > >> > >> When using the hidraw node directly, disable the touchpad endpoint to prevent > >> it from sending separate mouse-like reports. This is accomplished in the same > >> way that the hid-steam driver does it, by creating and attaching an input_dev > >> with a custom low-level transport driver, which monitors and reports when the > >> hidraw node is opened or closed. Reports sent by the real device are reported > >> to the "fake" device, and the real device is prevented from creating a hidraw > >> node. This "fake" device is connected with only a hidraw node, and is exposed > >> with identifying information that is identical to the original device, so the > >> "fake" device's hidraw node appears as the node associated with the dev. > > > > Besides the "we should have a generic way of doing this", why do we > > only prevent touchpad events from being reported? > > As, from what I can tell, most windowing systems treat it as a mouse, it's the most prone to "double input" problems when prodded by both the hidraw and the windowing system. Windowing systems generally don't do anything with the other exposed inputs, as far as I can tell. > > > > > [looking at the code further down] > > > > So it seems you are entirely disabling the input nodes, which is what > > I would have expected, so the commit description needs some changes. > > Or am I reading this wrong? > > I am unsure where this discrepancy lies in the description. Can you be more specific? > When I read the code, I was under the impression that when an hidraw node was opened, it was disabling all other input nodes (joysticks, buttons and touchpad). But maybe this is just disabling the touchpad, which still leaves you with duplicated events on the gamepad side. So either we need to also disable those other events, or the code is doing just that and the description is not correct :) Cheersm Benjamin
