From: David Lechner <david@lechnology.com>
To: linux-spi@vger.kernel.org, linux-iio@vger.kernel.org
Cc: David Lechner <david@lechnology.com>,
Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Mark Brown <broonie@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] spi: SPI_CS_WORD followup
Date: Tue, 18 Sep 2018 12:08:47 -0500 [thread overview]
Message-ID: <20180918170850.2749-1-david@lechnology.com> (raw)
This is a followup to the series "spi: introduce SPI_CS_WORD mode flag" [1] to
address some review comments.
- The first two patches handle the case for GPIO CS
- The last patch is the IIO patch from the previous series with an expanded
commit message.
[1]: https://lore.kernel.org/lkml/20180913003920.30600-1-david@lechnology.com/
David Lechner (3):
spi: always use software fallback for SPI_CS_WORD when using cs_gio
spi: spi-davinci: Don't error when SPI_CS_WORD and cs_gpio
iio: adc: ti-ads7950: use SPI_CS_WORD to reduce CPU usage
drivers/iio/adc/ti-ads7950.c | 53 +++++++++++++++++++++---------------
drivers/spi/spi-davinci.c | 3 --
drivers/spi/spi.c | 6 ++--
3 files changed, 35 insertions(+), 27 deletions(-)
--
2.17.1
next reply other threads:[~2018-09-18 17:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 17:08 David Lechner [this message]
2018-09-18 17:08 ` [PATCH 1/3] spi: always use software fallback for SPI_CS_WORD when using cs_gio David Lechner
2018-09-18 17:45 ` Applied "spi: always use software fallback for SPI_CS_WORD when using cs_gio" to the spi tree Mark Brown
2018-09-18 17:08 ` [PATCH 2/3] spi: spi-davinci: Don't error when SPI_CS_WORD and cs_gpio David Lechner
2018-09-18 17:45 ` Applied "spi: spi-davinci: Don't error when SPI_CS_WORD and cs_gpio" to the spi tree Mark Brown
2018-09-18 17:08 ` [PATCH 3/3] iio: adc: ti-ads7950: use SPI_CS_WORD to reduce CPU usage David Lechner
2018-09-18 17:14 ` David Lechner
2018-09-22 9:12 ` Jonathan Cameron
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=20180918170850.2749-1-david@lechnology.com \
--to=david@lechnology.com \
--cc=broonie@kernel.org \
--cc=geert@linux-m68k.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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).