tree bd15b031be36618b8796d84017658caa9316076d
parent 651022382c7f8da46cb4872a545ee1da6d097d2a
author Brian Norris <briannorris@chromium.org> 1541645378 -0800
committer Benson Leung <bleung@chromium.org> 1542173114 -0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iQIzBAABCgAdFiEE6gYDF28Li+nEiKLaHwn1ewov5lgFAlvrsb0ACgkQHwn1ewov
 5liZCxAAqtYZG9oW2HROlUAvdTciT1JP/J3riaFp2vblIi/keUZ6ULhmtvXEV5E2
 yZAuufAg64+IXubv/Yp/0pR6uYN49fR2N+gL385eW8tOCa1JBGxpgc9A7wjrZdry
 F36MNKhMyIDu+85TTQZANUdk/HdqF7IKAHNu4qyFhBhaKMYFDtff0CODgZeA+DuX
 SDtuRYPf3GdoyOyMqvNhILV4q7o0s9LhM+SuwTdktCC+Yise1MfGx5BMrHCKtdCz
 VZDjjgBkxtHiB+48xI48N3pzYACHuPghRIofSpz8WQdzYc0jnyA+voa5fbhsuPWY
 iVbfFMgTKb3VLE4T2VTOv5oHHClSOfV5fM336LijN1nLhTDEJMQE0OobnwqPrEpI
 nx2YxVgcH2kuUg/H3JDQ2OmXcVWrl1v9MAdzUQqS20JTDKFjJ/lM/ftXs4Isa0Qq
 xjo6k4spvxWU9lEzuMWsbA+0bQ8W2RxOrp1tiiW58PE6sfEkK9hM2BQoSQLMygDh
 WVP2WaHr8r4bMWz5Wznzim9cqVzPRBxqxGtZJI0ZbmmXkZaTJ9Tv/rD37yEBcVcZ
 c0wxWMxZcJYC+Yu5KyH6j7Vpg8jFQjBIZ1tNmTN60DoU1L1nDTngbibJ9IK0dXg4
 mXR++OXbBQPc6iUgTz2uF4HMZdoCxn9ISYryA2z0btb9f+iiGrI=
 =kw5p
 -----END PGP SIGNATURE-----

platform/chrome: straighten out cros_ec_get_{next,host}_event() error codes

cros_ec_get_next_event() is documented to return 0 for success and
negative for errors. It currently returns negative for some errors, and
non-negative (number of bytes received) for success (including some "no
data available" responses as zero). This mostly works out OK, because the
callers were more or less ignoring the documentation, and only treating
positive values as success (and indepdently checking the modification of
'wakeup').

Let's button this up by avoiding pretending to handle event/wakeup
distinctions when no event info was retrieved (i.e., returned 0 bytes).
And fix the documentation of cros_ec_get_host_event() and
cros_ec_get_next_event() to accurately describe their behavior.

Signed-off-by: Brian Norris <briannorris@chromium.org>
Acked-by: Lee Jones <lee.jones@linaro.org>
Signed-off-by: Benson Leung <bleung@chromium.org>