CHROMIUM: hid-logitech-wtp: Set HID_QUIRK_NO_INIT_REPORTS

The usual flow of a driver's probe function is:

- hid_parse()
- hid_hw_start() (which sets up /dev/input/event#)
- do some i/o w/ the device

However, b/c we need to do i/o before we set up /dev/input/event,
we do this order:

- hid_parse()
- do some i/o w/ the device
- hid_hw_start()

In the 3.8 kernel w/ bluetooth, this was fine. In the 3.10 kernel,
this is causing a memory overrun in hid_hw_start, in the stack trace
you can see above. Since the overrun is happening in hid_hw_start() w/
the init code, it turns out we can not run that code w/ a quirk.
It seems to work great, so I guess we didn't need that init code.

Signed-off-by: Andrew de los Reyes <adlr@chromium.org>
Signed-off-by: Benson Leung <bleung@chromium.org>

BUG=chromium:323784
TEST=Pair a Logitech T651 with Falco running chromeos-3.10.
Ensure that the trackpad works with MT data reported in evtest.

Change-Id: I7e3f4570001eb08b09b9913d99796bc9f2ef0207
Reviewed-on: https://chromium-review.googlesource.com/181037
Reviewed-by: Dennis Kempin <denniskempin@chromium.org>
Reviewed-by: Benson Leung <bleung@chromium.org>
Commit-Queue: Benson Leung <bleung@chromium.org>
Tested-by: Benson Leung <bleung@chromium.org>