From: Guenter Roeck <linux@roeck-us.net>
To: Brian Norris <briannorris@chromium.org>
Cc: "Enric Balletbo i Serra" <enric.balletbo@collabora.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Benson Leung" <bleung@chromium.org>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Gwendal Grignou" <gwendal@chromium.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org, linux-pwm@vger.kernel.org,
"Yu-Hsuan Hsu" <yuhsuan@chromium.org>,
"Prashant Malani" <pmalani@chromium.org>
Subject: Re: [PATCH v3 6/6] platform/chrome: cros_ec_proto: Convert EC error codes to Linux error codes
Date: Wed, 29 Jul 2020 16:22:04 -0700 [thread overview]
Message-ID: <ae5aeae1-4dfc-0fd7-3392-bf1ca3540866@roeck-us.net> (raw)
In-Reply-To: <20200729222150.GA970863@google.com>
On 7/29/20 3:21 PM, Brian Norris wrote:
> Hi Guenter,
>
> On Sun, Jul 26, 2020 at 03:01:01PM -0700, Guenter Roeck wrote:
>> v3: Use -ENOPROTOOPT for EC_RES_INVALID_VERSION
>> Implement function to convert error codes
>> v2: No change
>>
>> drivers/platform/chrome/cros_ec_proto.c | 52 ++++++++++++++++++++-----
>> 1 file changed, 42 insertions(+), 10 deletions(-)
>>
>> diff --git a/drivers/platform/chrome/cros_ec_proto.c b/drivers/platform/chrome/cros_ec_proto.c
>> index e5bbec979a2a..a081b8245682 100644
>> --- a/drivers/platform/chrome/cros_ec_proto.c
>> +++ b/drivers/platform/chrome/cros_ec_proto.c
>> @@ -15,6 +15,43 @@
>>
>> #define EC_COMMAND_RETRIES 50
>>
>> +static const int cros_ec_error_map[] = {
>> + [EC_RES_INVALID_COMMAND] = -EOPNOTSUPP,
>> + [EC_RES_ERROR] = -EIO,
>> + [EC_RES_INVALID_PARAM] = -EINVAL,
>> + [EC_RES_ACCESS_DENIED] = -EACCES,
>> + [EC_RES_INVALID_RESPONSE] = -EPROTO,
>> + [EC_RES_INVALID_VERSION] = -ENOPROTOOPT,
>> + [EC_RES_INVALID_CHECKSUM] = -EBADMSG,
>> + [EC_RES_IN_PROGRESS] = -EINPROGRESS,
>> + [EC_RES_UNAVAILABLE] = -ENODATA,
>> + [EC_RES_TIMEOUT] = -ETIMEDOUT,
>> + [EC_RES_OVERFLOW] = -EOVERFLOW,
>> + [EC_RES_INVALID_HEADER] = -EBADR,
>> + [EC_RES_REQUEST_TRUNCATED] = -EBADR,
>> + [EC_RES_RESPONSE_TOO_BIG] = -EFBIG,
>> + [EC_RES_BUS_ERROR] = -EFAULT,
>> + [EC_RES_BUSY] = -EBUSY,
>> + [EC_RES_INVALID_HEADER_VERSION] = -EBADMSG,
>> + [EC_RES_INVALID_HEADER_CRC] = -EBADMSG,
>> + [EC_RES_INVALID_DATA_CRC] = -EBADMSG,
>> + [EC_RES_DUP_UNAVAILABLE] = -ENODATA,
>> +};
>
> Sorry I didn't pay attention to this earlier, but is there any
> programmatic way to ensure that we don't have unexpected holes here? If
> we do (e.g., we add new error codes, but they aren't contiguous for
> whatever reasons), then those will get treated as "success" with your
> current patch.
>
> I say "unexpected" hole, because EC_RES_SUCCESS (0) is an expected hole.
>
>> +
>> +static int cros_ec_map_error(uint32_t result)
>> +{
>> + int ret = 0;
>> +
>> + if (result != EC_RES_SUCCESS) {
>> + if (result < ARRAY_SIZE(cros_ec_error_map) && cros_ec_error_map[result])
>> + ret = cros_ec_error_map[result];
>
> ^^ Maybe we want to double check 'ret != 0'? Or maybe
>
> ret = cros_ec_error_map[result];
> if (!ret) {
'ret' won't ever be 0 here. Above:
&& cros_ec_error_map[result]
and below:
else
ret = -EPROTO;
> ret = -EPROTO;
> dev_err(..., "Unexpected EC result code %d\n", result);
> }
>
> ? Could even be WARN_ON(), since this would be an actionable programming
> error, not exactly an external factor. Or maybe I'm being paranoid, and
> future programmers are perfect.
>
I think, if anything, we might consider adding the message below (result >=
ARRAY_SIZE(cros_ec_error_map) is just as bad). Not sure myself. I am
open to adding it if people think it would be useful/desirable.
Thanks,
Guenter
> Otherwise:
>
> Reviewed-by: Brian Norris <briannorris@chromium.org>
>
>> + else
>> + ret = -EPROTO;
>> + }
>> +
>> + return ret;
>> +}
>> +
>> static int prepare_packet(struct cros_ec_device *ec_dev,
>> struct cros_ec_command *msg)
>> {
next prev parent reply other threads:[~2020-07-29 23:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-26 22:00 [PATCH v3 0/6] platform/chrome: cros_ec_proto: Convert EC error codes to Linux error codes Guenter Roeck
2020-07-26 22:00 ` [PATCH v3 1/6] iio: cros_ec: Accept -EOPNOTSUPP as 'not supported' error code Guenter Roeck
2020-07-26 22:00 ` [PATCH v3 2/6] cros_ec_lightbar: Accept more error codes from cros_ec_cmd_xfer_status Guenter Roeck
2020-07-26 22:00 ` [PATCH v3 3/6] platform/chrome: cros_ec_sysfs: Report range of error codes from EC Guenter Roeck
2020-07-26 22:00 ` [PATCH v3 4/6] pwm: cros-ec: Accept more error codes from cros_ec_cmd_xfer_status Guenter Roeck
2020-07-27 8:35 ` Thierry Reding
2020-08-01 7:21 ` Uwe Kleine-König
2020-08-01 16:32 ` Guenter Roeck
2020-08-02 20:27 ` Uwe Kleine-König
2020-07-26 22:01 ` [PATCH v3 5/6] platform/input: cros_ec: Replace -ENOTSUPP with -ENOPROTOOPT Guenter Roeck
2020-07-30 4:53 ` Dmitry Torokhov
2020-07-26 22:01 ` [PATCH v3 6/6] platform/chrome: cros_ec_proto: Convert EC error codes to Linux error codes Guenter Roeck
2020-07-29 22:21 ` Brian Norris
2020-07-29 23:22 ` Guenter Roeck [this message]
2020-07-29 23:29 ` Brian Norris
2020-07-29 22:27 ` [PATCH v3 0/6] " Brian Norris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ae5aeae1-4dfc-0fd7-3392-bf1ca3540866@roeck-us.net \
--to=linux@roeck-us.net \
--cc=bleung@chromium.org \
--cc=briannorris@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=enric.balletbo@collabora.com \
--cc=gwendal@chromium.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=pmalani@chromium.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=yuhsuan@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).