From: Lee Jones <lee.jones@linaro.org>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
Brian Norris <briannorris@chromium.org>,
Shawn Nematbakhsh <shawnn@chromium.org>
Subject: Re: [PATCH 2/2] mfd: cros ec: spi: Simplify delay handling between SPI messages
Date: Wed, 29 Nov 2017 11:07:37 +0000 [thread overview]
Message-ID: <20171129110737.t5bm5nvwsgfzfye6@dell> (raw)
In-Reply-To: <1510607140-30582-2-git-send-email-jonathanh@nvidia.com>
On Mon, 13 Nov 2017, Jon Hunter wrote:
> The EC SPI driver prevents SPI transfers being to rapidly by keeping
> track of the time the last transfer was issued via the
> 'last_transfer_ns' variable. Previously, if the 'last_transfer_ns'
> variable was zero, this indicated that no previous transfer had been
> sent and that no delay was needed. However, the EC SPI driver has
> been updated to always initialise the 'last_transfer_ns' variable
> during probe and therefore, it is no longer necessary to test if it
> is zero. Remove the code that checks if this variable is zero.
>
> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> ---
> drivers/mfd/cros_ec_spi.c | 25 +++++++++----------------
> 1 file changed, 9 insertions(+), 16 deletions(-)
Applied, thanks.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2017-11-29 11:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 21:05 [PATCH 1/2] mfd: cros ec: spi: Don't send first message too soon Jon Hunter
2017-11-13 21:05 ` [PATCH 2/2] mfd: cros ec: spi: Simplify delay handling between SPI messages Jon Hunter
2017-11-13 21:22 ` Brian Norris
2017-11-29 11:07 ` Lee Jones [this message]
2017-11-13 21:19 ` [PATCH 1/2] mfd: cros ec: spi: Don't send first message too soon Brian Norris
2017-11-14 14:44 ` Jon Hunter
2017-11-29 11:07 ` 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=20171129110737.t5bm5nvwsgfzfye6@dell \
--to=lee.jones@linaro.org \
--cc=briannorris@chromium.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=shawnn@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
all inboxes | Powered by JetHome®