From: Douglas Anderson <dianders@chromium.org>
To: Mark Brown <broonie@kernel.org>,
Benson Leung <bleung@chromium.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: linux-rockchip@lists.infradead.org, drinkcat@chromium.org,
Guenter Roeck <groeck@chromium.org>,
briannorris@chromium.org, mka@chromium.org,
Douglas Anderson <dianders@chromium.org>,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org
Subject: [PATCH 0/4] spi: A better solution for cros_ec_spi reliability
Date: Fri, 10 May 2019 15:34:33 -0700 [thread overview]
Message-ID: <20190510223437.84368-1-dianders@chromium.org> (raw)
This series is a much better solution for getting the Chrome OS EC to
talk reliably and replaces commit 37a186225a0c ("platform/chrome:
cros_ec_spi: Transfer messages at high priority").
Note that the cros_ec bits can't land until the SPI bits are
somewhere. If the SPI bits look OK to land it might be convenient if
they could be placed somewhere with a stable git hash?
Special thanks to Guenter Roeck for pointing out the "realtime"
feature of the SPI framework so I didn't re-invent the wheel. I have
no idea how I missed it. :-/
Douglas Anderson (4):
spi: For controllers that need realtime always use the pump thread
spi: Allow SPI devices to specify that they are timing sensitive
platform/chrome: cros_ec_spi: Set ourselves as timing sensitive
Revert "platform/chrome: cros_ec_spi: Transfer messages at high
priority"
drivers/platform/chrome/cros_ec_spi.c | 81 +++------------------------
drivers/spi/spi.c | 41 +++++++++++---
include/linux/spi/spi.h | 3 +
3 files changed, 43 insertions(+), 82 deletions(-)
--
2.21.0.1020.gf2820cf01a-goog
next reply other threads:[~2019-05-10 22:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 22:34 Douglas Anderson [this message]
2019-05-10 22:34 ` [PATCH 1/4] spi: For controllers that need realtime always use the pump thread Douglas Anderson
2019-05-11 0:24 ` Guenter Roeck
[not found] ` <20190510223437.84368-2-dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2019-05-12 7:33 ` Mark Brown
2019-05-13 20:24 ` Doug Anderson
2019-05-14 9:30 ` Mark Brown
2019-05-14 14:42 ` Doug Anderson
2019-05-14 15:06 ` Mark Brown
2019-05-10 22:34 ` [PATCH 2/4] spi: Allow SPI devices to specify that they are timing sensitive Douglas Anderson
[not found] ` <20190510223437.84368-3-dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2019-05-11 0:31 ` Guenter Roeck
2019-05-12 7:42 ` Mark Brown
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=20190510223437.84368-1-dianders@chromium.org \
--to=dianders@chromium.org \
--cc=bleung@chromium.org \
--cc=briannorris@chromium.org \
--cc=broonie@kernel.org \
--cc=drinkcat@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=mka@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).