diff options
author | reillyg@chromium.org <reillyg@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-07-28 22:01:26 +0000 |
---|---|---|
committer | reillyg@chromium.org <reillyg@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-07-28 22:01:26 +0000 |
commit | 054293034c1e79f6ee7ff5b11e6a35673d7f38a3 (patch) | |
tree | 8f1a63690fbcdb0396c25c57d9de79d04a3853f8 /device/hid/hid_service_linux.cc | |
parent | 3e65977489925662657d91d334d6e9d1b520c60a (diff) | |
download | chromium_src-054293034c1e79f6ee7ff5b11e6a35673d7f38a3.zip chromium_src-054293034c1e79f6ee7ff5b11e6a35673d7f38a3.tar.gz chromium_src-054293034c1e79f6ee7ff5b11e6a35673d7f38a3.tar.bz2 |
hid: Remove size from receive APIs and return report ID separately.
The size parameter is unnecessary when calling chrome.hid.receive and
chrome.hid.receiveFeatureReport because, since the caller does not know
which report ID will be returned, it should always be set to the maximum
input or feature report size provided by the device. The size of the
report ID is now not included in the maximum report sizes for the device
since it no longer effects buffer size.
In addition increase consistency by always providing the report ID to
the chrome.hid.receive callback instead of including it as the first
byte of the data buffer only if it is non-zero.
BUG=
Review URL: https://codereview.chromium.org/413913003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@285989 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'device/hid/hid_service_linux.cc')
-rw-r--r-- | device/hid/hid_service_linux.cc | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/device/hid/hid_service_linux.cc b/device/hid/hid_service_linux.cc index 25230e7..8146c14 100644 --- a/device/hid/hid_service_linux.cc +++ b/device/hid/hid_service_linux.cc @@ -190,6 +190,7 @@ void HidServiceLinux::OnRequestAccessComplete( HidReportDescriptor report_descriptor(rpt_desc.value, rpt_desc.size); report_descriptor.GetDetails(&device_info->collections, + &device_info->has_report_id, &device_info->max_input_report_size, &device_info->max_output_report_size, &device_info->max_feature_report_size); |