[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200720202243.180230-1-linux@roeck-us.net>
Date: Mon, 20 Jul 2020 13:22:39 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Enric Balletbo i Serra <enric.balletbo@...labora.com>
Cc: Benson Leung <bleung@...omium.org>,
Jonathan Cameron <jic23@...nel.org>, linux-iio@...r.kernel.org,
linux-kernel@...r.kernel.org, Yu-Hsuan Hsu <yuhsuan@...omium.org>,
Prashant Malani <pmalani@...omium.org>,
Guenter Roeck <linux@...ck-us.net>
Subject: [PATCH v2 0/4] platform/chrome: cros_ec_proto: Convert EC error codes to Linux error codes
The EC reports a variety of error codes. Most of those, with the exception
of EC_RES_INVALID_VERSION, are converted to -EPROTO. As result, the actual
error code gets lost. In cros_ec_cmd_xfer_status(), convert all EC errors
to Linux error codes to report a more meaningful error to the caller to aid
debugging.
To prepare for this change, handle error codes other than -EPROTO for all
callers of cros_ec_cmd_xfer_status(). Specifically, no longer assume that
-EPROTO reflects an error from the EC and all other error codes reflect a
transfer error.
v2: Add patches 1/4 to 3/4 to handle callers of cros_ec_cmd_xfer_status()
----------------------------------------------------------------
Guenter Roeck (4):
iio: cros_ec: Accept -EOPNOTSUPP as 'not supported' error code
cros_ec_lightbar: Accept more error codes from cros_ec_cmd_xfer_status
platform/chrome: cros_ec_sysfs: Report range of error codes from EC
platform/chrome: cros_ec_proto: Convert EC error codes to Linux error codes
.../iio/common/cros_ec_sensors/cros_ec_sensors.c | 2 +-
drivers/platform/chrome/cros_ec_lightbar.c | 10 +++---
drivers/platform/chrome/cros_ec_proto.c | 37 +++++++++++++++++-----
drivers/platform/chrome/cros_ec_sysfs.c | 24 ++++++--------
4 files changed, 43 insertions(+), 30 deletions(-)
Powered by blists - more mailing lists