From: Clark Wang <xiaoning.wang@nxp.com>
To: "broonie@kernel.org" <broonie@kernel.org>
Cc: "linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [PATCH V2 0/8] spi: lpspi: Fix bugs and Add some functions support
Date: Wed, 6 Mar 2019 06:30:32 +0000 [thread overview]
Message-ID: <20190306063020.793-1-xiaoning.wang@nxp.com> (raw)
Hi Mark,
Sorry for replying so late. This patchset contains changes based on your and other
reviewers' comments.
As subject, these fucntions support, including:
- Support i.MX8 series boards;
- Support cs-gpio fucntion;
- Support DMA mode for both master and salve mode.
These are some notes about cs-gpio and DMA:
- cs-gpio:
Because LPSPI driver don't use default implementation of
transfer_one_message(), I do the cs-gpio control way as same as the way
used in spi core;
- DMA:
Any frame length longer than half txfifosize will be sent by DMA mode.
For now, there are some limits:
1. The maximum transfer speed in master mode depends on the slave device,
at least 40MHz on i.MX8 series (tested by spi-nor on 8qm-lpddr4-arm2
base board);
2. The maximum transfer speed I test in slave mode is 15MHz(i.MX7ULP),
20MHz(i.MX8 series). In order to reach the maximum speed which is
mentioned in datasheet, the load of connect wires between master and
slave should be less than 15pF.
Each patch in this patchset should base on the previous one when applied.
Thank you!
Clark Wang (7):
spi: lpspi: Add i.MX8 boards support for lpspi
doc: lpspi: Document DT bindings for LPSPI clocks
spi: lpspi: add the error info of transfer speed setting
spi: lpspi: use the core way to implement cs-gpio function
spi: lpspi: add dma mode support
spi: lpspi: Add the missing NULL check
spi: lpspi: Code cleanup
Han Xu (1):
spi: lpspi: enable runtime pm for lpspi
.../devicetree/bindings/spi/spi-fsl-lpspi.txt | 10 +-
drivers/spi/spi-fsl-lpspi.c | 543 ++++++++++++++++--
2 files changed, 495 insertions(+), 58 deletions(-)
--
2.17.1
next reply other threads:[~2019-03-06 6:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 6:30 Clark Wang [this message]
2019-03-06 6:30 ` [PATCH V2 1/8] spi: lpspi: Add i.MX8 boards support for lpspi Clark Wang
2019-03-06 6:30 ` [PATCH V2 2/8] doc: lpspi: Document DT bindings for LPSPI clocks Clark Wang
2019-03-18 14:52 ` Applied "doc: lpspi: Document DT bindings for LPSPI clocks" to the spi tree Mark Brown
2019-03-06 6:30 ` [PATCH V2 3/8] spi: lpspi: enable runtime pm for lpspi Clark Wang
2019-03-06 6:30 ` [PATCH V2 4/8] spi: lpspi: add the error info of transfer speed setting Clark Wang
2019-03-06 6:30 ` [PATCH V2 5/8] spi: lpspi: use the core way to implement cs-gpio function Clark Wang
2019-03-18 14:52 ` Applied "spi: lpspi: use the core way to implement cs-gpio function" to the spi tree Mark Brown
2019-03-06 6:30 ` [PATCH V2 6/8] spi: lpspi: add dma mode support Clark Wang
2019-03-18 14:52 ` Applied "spi: lpspi: add dma mode support" to the spi tree Mark Brown
2019-03-06 6:30 ` [PATCH V2 7/8] spi: lpspi: Add the missing NULL check Clark Wang
2019-03-18 14:52 ` Applied "spi: lpspi: Add the missing NULL check" to the spi tree Mark Brown
2019-03-06 6:30 ` [PATCH V2 8/8] spi: lpspi: Code cleanup Clark Wang
2019-03-18 14:52 ` Applied "spi: lpspi: Code cleanup" to the spi tree 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=20190306063020.793-1-xiaoning.wang@nxp.com \
--to=xiaoning.wang@nxp.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@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;
as well as URLs for NNTP newsgroup(s).