Displaying 6 results from an estimated 6 matches for "report_size".
2014 Mar 12
0
Developing the UPS side of the UPS-NUT equation (via usbhid)
...or NUT to work correctly? I assume it's not requesting reports because there is nothing it wants to know about.
Here is what I have so far:
USAGE_PAGE (Power Device)
USAGE (UPS)
COLLECTION (Application)
USAGE (BatterySystem)
COLLECTION (Physical)
REPORT_ID (1)
USAGE (Voltage)
REPORT_SIZE (8)
REPORT_COUNT (1)
UNIT (SI Lin:Volts)
LOGICAL_MINIMUM (0)
LOGICAL_MAXIMUM (255)
FEATURE (Data,Var,Abs)
REPORT_ID (2)
USAGE (Temperature)
REPORT_SIZE (8)
REPORT_COUNT (1)
LOGICAL_MINIMUM (0)
LOGICAL_MAXIMUM (255)
UNIT (SI Lin:Temperature)
FEATURE...
2014 Mar 12
4
Developing the UPS side of the UPS-NUT equation (via usbhid)
The syntax is beginning (just beginning) to make sense to me now, so I'm looking now to try and implement just a few items in the report descriptor, and then I figured I can progress from there if all goes well.
The power HID docs seem to encourage drawing out your system first, and then letting the report descriptor flow from there. So, my very simplified system goes like this:
2015 Mar 13
0
Problems with NUT 2.7.2 on CentOS 7 and using the Mini-Box OpenUPS
...49.222717] usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=4
> [ 49.229879] usb 4-5: Product: OPEN-UPS
> [ 49.233658] usb 4-5: Manufacturer: Mini-Box.Com
> [ 49.238218] usb 4-5: SerialNumber: PBSO4-LiFePO
> [ 49.259143] hid-generic 0003:04D8:D004.0002: invalid report_size 248
> [ 49.265603] hid-generic 0003:04D8:D004.0002: item 0 1 1 7 parsing failed
> [ 49.272485] hid-generic: probe of 0003:04D8:D004.0002 failed with error -22
You can ignore the hid-generic errors; NUT detaches that kernel driver and bypasses it with libusb.
That said, it means the HID...
2015 Mar 13
3
Problems with NUT 2.7.2 on CentOS 7 and using the Mini-Box OpenUPS
I?m a new user of NUT and the OpenUPS - in the past I?ve used APC hardware and apcupsd on Centos 6.
I?ve built NUT 2.7.2 from source but used the OpenUPS HID driver v0.4 that?s in github. I?m using firmware version 1.5 on the openups which is the latest published version; I?ve also tried 1.7 which Mini-box sent to me but reverted to the published version. Their support seems a bit slow!
I?ve got
2020 Oct 17
10
[RFC] treewide: cleanup unreachable breaks
...default:
/* what do we have here ? An unsupported Product-ID ? */
dev_err(&dev->interface->dev, "%s - not supported for product=0x%x\n",
__func__, dev->product_id);
retval = -EFAULT;
goto exit;
- break;
}
error:
usb_free_coherent(dev->udev, dev->report_size, buf,
int_out_urb->transfer_dma);
error_no_buffer:
diff --git a/drivers/usb/serial/iuu_phoenix.c b/drivers/usb/serial/iuu_phoenix.c
index b4ba79123d9d..f1201d4de297 100644
--- a/drivers/usb/serial/iuu_phoenix.c
+++ b/drivers/usb/serial/iuu_phoenix.c
@@ -848,11 +848,10 @@ static int iuu_ua...
2020 Oct 17
10
[RFC] treewide: cleanup unreachable breaks
...default:
/* what do we have here ? An unsupported Product-ID ? */
dev_err(&dev->interface->dev, "%s - not supported for product=0x%x\n",
__func__, dev->product_id);
retval = -EFAULT;
goto exit;
- break;
}
error:
usb_free_coherent(dev->udev, dev->report_size, buf,
int_out_urb->transfer_dma);
error_no_buffer:
diff --git a/drivers/usb/serial/iuu_phoenix.c b/drivers/usb/serial/iuu_phoenix.c
index b4ba79123d9d..f1201d4de297 100644
--- a/drivers/usb/serial/iuu_phoenix.c
+++ b/drivers/usb/serial/iuu_phoenix.c
@@ -848,11 +848,10 @@ static int iuu_ua...