Normaly that driver should not be used. The helptext is saying that clear:
Say Y here if you want to provide HID I/O Drivers from user-space. This allows to write I/O drivers in user-space and feed the data from the device into the kernel. The kernel parses the HID reports, loads the corresponding HID Device Driver or provides input devices on top of your user-space device.
This driver cannot be used to parse HID-reports in user-space and write special HID-drivers. You should use hidraw for that. Instead, this driver allows to write the transport-layer driver in user-space like USB-HID and Bluetooth-HID do in kernel-space.
If unsure, say N.
To compile this driver as a module, choose M here: the module will be called uhid.
Our kernel has set CONFIG_HIDRAW=y.
But i can enable UHID as module, let's see, what's getting broken with that.