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 v3 0/3] spi: A better solution for cros_ec_spi reliability
Date: Tue, 14 May 2019 11:39:32 -0700 [thread overview]
Message-ID: <20190514183935.143463-1-dianders@chromium.org> (raw)
This series is a much better solution for getting the Chrome OS EC to
talk reliably.
Patch #1 in this series is the most important. It can land any time.
Patch #2 in this series (a SPI framework patch) needs to land before
patch #3. Note that patches #2 and #3 really just fix a corner case
and just having patch #1 is the most important. We don't end up on
the pumping thread very often.
Note:
- If you want some history on investigation done here, feel free to
peruse the Chrome OS bug: <https://crbug.com/948742>.
Changes in v3:
- cros_ec realtime patch replaces revert; now patch #1
- SPI core change now like patch v1 patch #2 (with name "rt").
- Updated description and variable name since we no longer force.
Changes in v2:
- Now only force transfers to the thread for devices that want it.
- Squashed patch #1 and #2 together.
- Renamed variable to "force_rt_transfers".
- Renamed variable to "force_rt_transfers".
Douglas Anderson (3):
platform/chrome: cros_ec_spi: Move to real time priority for transfers
spi: Allow SPI devices to request the pumping thread be realtime
platform/chrome: cros_ec_spi: Request the SPI thread be realtime
drivers/platform/chrome/cros_ec_spi.c | 89 +++++++++++++++++++++++----
drivers/spi/spi.c | 36 +++++++++--
include/linux/spi/spi.h | 2 +
3 files changed, 110 insertions(+), 17 deletions(-)
--
2.21.0.1020.gf2820cf01a-goog
next reply other threads:[~2019-05-14 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 18:39 Douglas Anderson [this message]
[not found] ` <20190514183935.143463-1-dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2019-05-14 18:39 ` [PATCH v3 2/3] spi: Allow SPI devices to request the pumping thread be realtime Douglas Anderson
2019-05-14 19:44 ` Guenter Roeck
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=20190514183935.143463-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).