From: Jon Hunter <jonathanh@nvidia.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
"Brian Norris" <briannorris@chromium.org>,
Shawn Nematbakhsh <shawnn@chromium.org>,
Benson Leung <bleung@chromium.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH V2 1/2] mfd: cros ec: spi: Don't send first message too soon
Date: Tue, 28 Nov 2017 16:25:44 +0000 [thread overview]
Message-ID: <419f195f-8c38-5dd2-7742-3fff98d6795b@nvidia.com> (raw)
In-Reply-To: <1510670608-19594-1-git-send-email-jonathanh@nvidia.com>
Hi Lee,
On 14/11/17 14:43, Jon Hunter wrote:
> On the Tegra124 Nyan-Big chromebook the very first SPI message sent to
> the EC is failing.
>
> The Tegra SPI driver configures the SPI chip-selects to be active-high
> by default (and always has for many years). The EC SPI requires an
> active-low chip-select and so the Tegra chip-select is reconfigured to
> be active-low when the EC SPI driver calls spi_setup(). The problem is
> that if the first SPI message to the EC is sent too soon after
> reconfiguring the SPI chip-select, it fails.
>
> The EC SPI driver prevents back-to-back SPI messages being sent too
> soon by keeping track of the time the last transfer was sent via the
> variable 'last_transfer_ns'. To prevent the very first transfer being
> sent too soon, initialise the 'last_transfer_ns' variable after calling
> spi_setup() and before sending the first SPI message.
>
> Cc: <stable@vger.kernel.org>
>
> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> Reviewed-by: Brian Norris <briannorris@chromium.org>
> ---
> Changes since V1:
> - Added stable-tag and Brian's reviewed-by.
>
> Looks like this issue has been around for several Linux releases now
> and it just depends on timing if this issue is seen or not and so there
> is no specific commit this fixes. However, would be good to include for
> v4.15.
>
> drivers/mfd/cros_ec_spi.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/mfd/cros_ec_spi.c b/drivers/mfd/cros_ec_spi.c
> index c9714072e224..a14196e95e9b 100644
> --- a/drivers/mfd/cros_ec_spi.c
> +++ b/drivers/mfd/cros_ec_spi.c
> @@ -667,6 +667,7 @@ static int cros_ec_spi_probe(struct spi_device *spi)
> sizeof(struct ec_response_get_protocol_info);
> ec_dev->dout_size = sizeof(struct ec_host_request);
>
> + ec_spi->last_transfer_ns = ktime_get_ns();
>
> err = cros_ec_register(ec_dev);
> if (err) {
Can you queue this as a fix for v4.15-rc1?
Cheers
Jon
--
nvpublic
next prev parent reply other threads:[~2017-11-28 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 14:43 Jon Hunter
2017-11-14 14:43 ` [PATCH V2 2/2] mfd: cros ec: spi: Simplify delay handling between SPI messages Jon Hunter
2017-11-14 18:47 ` Doug Anderson
2017-11-19 6:17 ` Benson Leung
2017-11-14 18:46 ` [PATCH V2 1/2] mfd: cros ec: spi: Don't send first message too soon Doug Anderson
2017-11-19 6:09 ` Benson Leung
2017-11-28 16:25 ` Jon Hunter [this message]
2017-11-29 11:15 ` Lee Jones
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=419f195f-8c38-5dd2-7742-3fff98d6795b@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=bleung@chromium.org \
--cc=briannorris@chromium.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=shawnn@chromium.org \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®