Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1605629 > unrolled thread
| Started by | Jiri Kosina <jikos@kernel.org> |
|---|---|
| First post | 2017-03-21 15:10 +0100 |
| Last post | 2017-03-21 15:10 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH v2] HID: remove initial reading of reports at connect Jiri Kosina <jikos@kernel.org> - 2017-03-21 15:10 +0100
| From | Jiri Kosina <jikos@kernel.org> |
|---|---|
| Date | 2017-03-21 15:10 +0100 |
| Subject | Re: [PATCH v2] HID: remove initial reading of reports at connect |
| Message-ID | <tnsE1-4nH-7@gated-at.bofh.it> |
On Wed, 8 Mar 2017, Benjamin Tissoires wrote: > It looks like a bunch of devices do not like to be polled for their > reports at init time. When you look into the details, it seems that for > those that are requiring the quirk HID_QUIRK_NO_INIT_REPORTS, the driver > fails to retrieve part of the features/inputs while others (more > generic) work. > > IMO, it should be acceptable to remove the need for the quirk in the > general case. On the small amount of cases where we actually need to > read the current values, the driver in charge (hid-mt or wacom) already > retrieves the features manually. Applied to for-4.12/nuke-no-init-reports-quirk. Thanks, -- Jiri Kosina SUSE Labs
Back to top | Article view | linux.kernel
csiph-web