From: Lee Jones <lee.jones@linaro.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
Kukjin Kim <kgene.kim@samsung.com>,
Tomasz Figa <tomasz.figa@gmail.com>,
broonie@kernel.org, sjg@chromium.org, olof@lixom.net,
javier.martinez@collabora.co.uk, ch.naveen@samsung.com,
swarren@wwwdotorg.org, khilman@linaro.org, ajaynumb@gmail.com,
rahul.sharma@samsung.com, tushar.b@samsung.com,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] mfd: cros_ec: spi: Fix end of transfer on devices with no spi-msg-delay
Date: Mon, 16 Jun 2014 15:24:04 +0100 [thread overview]
Message-ID: <20140616142404.GY14323@lee--X1> (raw)
In-Reply-To: <1402683213-23120-1-git-send-email-dianders@chromium.org>
> cros_ec_spi makes the assumption that a 0-length message will put the
> spi chip select back to normal (non cs_toggle mode). This used to be
> the case back on kernel-3.8 on the spi-s3c64xx driver but doesn't
> appear to be true anymore. It seems like it was a pretty questionable
> assumption to begin with, so let's fix the code to be more robust. We
> know that a message with a single 0-length segment _will_ put things
> back in order. Change cros_ec_spi to handle this.
>
> This wasn't a problem on the main user of cros_ec_spi upstream (tegra)
> because it specified 'google,cros-ec-spi-msg-delay'.
>
> Signed-off-by: Doug Anderson <dianders@chromium.org>
> ---
> drivers/mfd/cros_ec_spi.c | 18 +++++++-----------
> 1 file changed, 7 insertions(+), 11 deletions(-)
Looks fine to me and I'm sure you've tested this on your platform.
Applied, thanks.
> diff --git a/drivers/mfd/cros_ec_spi.c b/drivers/mfd/cros_ec_spi.c
> index 0b8d328..0cbc3db 100644
> --- a/drivers/mfd/cros_ec_spi.c
> +++ b/drivers/mfd/cros_ec_spi.c
> @@ -266,18 +266,14 @@ static int cros_ec_command_spi_xfer(struct cros_ec_device *ec_dev,
> dev_err(ec_dev->dev, "spi transfer failed: %d\n", ret);
> }
>
> - /* turn off CS */
> + /*
> + * Turn off CS, possibly adding a delay to ensure the rising edge
> + * doesn't come too soon after the end of the data.
> + */
> spi_message_init(&msg);
> -
> - if (ec_spi->end_of_msg_delay) {
> - /*
> - * Add delay for last transaction, to ensure the rising edge
> - * doesn't come too soon after the end of the data.
> - */
> - memset(&trans, 0, sizeof(trans));
> - trans.delay_usecs = ec_spi->end_of_msg_delay;
> - spi_message_add_tail(&trans, &msg);
> - }
> + memset(&trans, 0, sizeof(trans));
> + trans.delay_usecs = ec_spi->end_of_msg_delay;
> + spi_message_add_tail(&trans, &msg);
>
> final_ret = spi_sync(ec_spi->spi, &msg);
> ktime_get_ts(&ts);
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2014-06-16 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 18:13 [PATCH 1/2] mfd: cros_ec: spi: Fix end of transfer on devices with no spi-msg-delay Doug Anderson
2014-06-13 18:13 ` [PATCH 2/2] ARM: dts: Add cros_ec to exynos5420-peach-pit and exynos5800-peach-pi Doug Anderson
2014-06-17 16:37 ` Javier Martinez Canillas
2014-06-16 14:24 ` Lee Jones [this message]
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=20140616142404.GY14323@lee--X1 \
--to=lee.jones@linaro.org \
--cc=ajaynumb@gmail.com \
--cc=broonie@kernel.org \
--cc=ch.naveen@samsung.com \
--cc=dianders@chromium.org \
--cc=javier.martinez@collabora.co.uk \
--cc=kgene.kim@samsung.com \
--cc=khilman@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=rahul.sharma@samsung.com \
--cc=sameo@linux.intel.com \
--cc=sjg@chromium.org \
--cc=swarren@wwwdotorg.org \
--cc=tomasz.figa@gmail.com \
--cc=tushar.b@samsung.com \
/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