deference at null.net
2021-Nov-24 03:18 UTC
[Nut-upsdev] Looking for history: usbhid-ups - powercom.
Hello, This is a cross post in an attempt to dig up a bit a history and hopefully some tips regarding the driver for POWERCOM UPS devices. The discussion is on the LKML and can be viewed here: https://lkml.org/lkml/2021/11/14/375 In the NUT source tree there is: https://github.com/networkupstools/nut/blob/master/drivers/usbhid-ups.c This is a driver for some ups devices. I own a powercom one, a newer model we think, that disconnects and reconnects continuously from the Linux Kernel (version 5.15.X). My UPS's vendor ID is 0d9f (POWERCOM) and the product ID is 0004. It's called "OPTI-UPS Thunder Shield TS2250B". There's a quirk entry in the Linux kernel for entry for 0d9f:0002. It tells the kernel to completely ignore the UPS and allow something else (NUT?) to handle it. The Linux Kernel driver says to not request reports from USB devices as this can be problematic for some of them. Ben notes that, "HID_QUIRK_ALWAYS_POLL *might* be a way to force the [UPS] device to stay with a USB connection up." We would like to know, does anyone know the history of this? Do you have any tips on getting my UPS to talk to my Linux PC? Should I be asking for help with my UPS from the NUT team instead of the Linux Kernel devs because you have a driver for some UPS-es? Thanks, David