From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
To: Lee Jones <lee.jones@linaro.org>
Cc: Wolfram Sang <wsa@the-dreams.de>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Doug Anderson <dianders@chromium.org>,
Simon Glass <sjg@chromium.org>,
Bill Richardson <wfrichar@chromium.org>,
Andrew Bresticker <abrestic@chromium.org>,
Derek Basehore <dbasehore@chromium.org>,
Todd Broch <tbroch@chromium.org>, Olof Johansson <olof@lixom.net>,
Andreas Faerber <afaerber@suse.de>,
linux-i2c@vger.kernel.org, linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH v3 5/6] mfd: cros_ec: wait for completion of commands that return IN_PROGRESS
Date: Thu, 18 Sep 2014 09:42:27 +0200 [thread overview]
Message-ID: <541A8CE3.30206@collabora.co.uk> (raw)
In-Reply-To: <20140917162336.GK30918@lee--X1>
Hello Lee,
Thanks a lot for your feedback.
On 09/17/2014 06:23 PM, Lee Jones wrote:
>>
>> mutex_lock(&ec_dev->lock);
>> ret = ec_dev->cmd_xfer(ec_dev, msg);
>> + if (msg->result == EC_RES_IN_PROGRESS) {
>> + int i;
>> + struct cros_ec_command status_msg;
>> + struct ec_response_get_comms_status status;
>> +
>> + status_msg.version = 0;
>> + status_msg.command = EC_CMD_GET_COMMS_STATUS;
>> + status_msg.outdata = NULL;
>> + status_msg.outsize = 0;
>> + status_msg.indata = (uint8_t *)&status;
>> + status_msg.insize = sizeof(status);
>> +
>> + /*
>> + * Query the EC's status until it's no longer busy or
>> + * we encounter an error.
>> + */
>> + for (i = 0; i < EC_COMMAND_RETRIES; i++) {
>> + usleep_range(EC_RETRY_DELAY_MS, EC_RETRY_DELAY_MS + 1);
>
> Remove the EC_RETRY_DELAY_MS define and place the values in raw.
>
Ok, will do.
> You're now sleeping for 10us. Did you test the changes?
>
Duh, I must had been sleepy since I thought about changing the define but I
completely missed... which proves your point that raw values are more explicit
than using a define here.
Yes, I'm testing the changes and making sure that it does not add any
regression but I was not able to reproduce the case when an EC command result
is IN_PROGRESS. I'll investigate further on how to properly test that branch
before posting v4.
Best regards,
Javier
next prev parent reply other threads:[~2014-09-18 7:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 9:38 [PATCH v3 0/6] Second batch of cleanups for cros_ec Javier Martinez Canillas
2014-09-11 9:38 ` [PATCH v3 1/6] mfd: cros_ec: Delay for 50ms when we see EC_CMD_REBOOT_EC Javier Martinez Canillas
2014-09-11 9:38 ` [PATCH v3 4/6] mfd: cros_ec: move locking into cros_ec_cmd_xfer Javier Martinez Canillas
[not found] ` <1410428289-18229-1-git-send-email-javier.martinez-ZGY8ohtN/8pPYcu2f3hruQ@public.gmane.org>
2014-09-11 9:38 ` [PATCH v3 2/6] i2c: i2c-cros-ec-tunnel: Set retries to 3 Javier Martinez Canillas
2014-09-11 9:38 ` [PATCH v3 3/6] mfd: cros_ec: stop calling ->cmd_xfer() directly Javier Martinez Canillas
2014-09-11 9:38 ` [PATCH v3 5/6] mfd: cros_ec: wait for completion of commands that return IN_PROGRESS Javier Martinez Canillas
2014-09-17 16:23 ` Lee Jones
2014-09-18 7:42 ` Javier Martinez Canillas [this message]
2014-09-11 9:38 ` [PATCH v3 6/6] mfd: cros_ec: Instantiate sub-devices from device tree Javier Martinez Canillas
[not found] ` <1410428289-18229-7-git-send-email-javier.martinez-ZGY8ohtN/8pPYcu2f3hruQ@public.gmane.org>
2014-09-17 16:31 ` Lee Jones
2014-09-18 7:49 ` Javier Martinez Canillas
2014-09-18 15:33 ` Javier Martinez Canillas
[not found] ` <541A8E88.6050707-ZGY8ohtN/8pPYcu2f3hruQ@public.gmane.org>
2014-09-19 0:15 ` Lee Jones
2014-09-25 13:53 ` Javier Martinez Canillas
2014-09-25 14:48 ` Lee Jones
2014-09-25 15:42 ` Javier Martinez Canillas
[not found] ` <542437DE.4090701-ZGY8ohtN/8pPYcu2f3hruQ@public.gmane.org>
2014-09-26 7:21 ` Lee Jones
2014-09-26 7:47 ` Javier Martinez Canillas
2014-09-29 7:33 ` Javier Martinez Canillas
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=541A8CE3.30206@collabora.co.uk \
--to=javier.martinez@collabora.co.uk \
--cc=abrestic@chromium.org \
--cc=afaerber@suse.de \
--cc=dbasehore@chromium.org \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=sjg@chromium.org \
--cc=tbroch@chromium.org \
--cc=wfrichar@chromium.org \
--cc=wsa@the-dreams.de \
/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).