From: Lukasz Majewski <lukma@denx.de>
To: Mark Brown <broonie@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Lukasz Majewski <lukma@denx.de>
Subject: [PATCH 0/3] ARM: dspi: Provide slave mode support for Vybryd vf610
Date: Tue, 18 Sep 2018 11:34:34 +0200 [thread overview]
Message-ID: <20180918093437.26799-1-lukma@denx.de> (raw)
This patch series provides support for DSPI slave mode operation.
It tries to maximally reuse current DMA driver (including its limitations).
For testing the spidev_test program has been used.
Test script for this patch can be found here:
https://github.com/lmajewski/tests-spi/blob/master/tests/spi/spi_tests.sh
Lukasz Majewski (3):
dt-bindings: spi: Provide bindings for fsl dspi working in slave mode
ARM: dspi: Provide per DSPI instance of the MCR register (SLAVE mode)
ARM: dspi: Provide support for DSPI slave more operation (Vybryd
vf610)
.../devicetree/bindings/spi/spi-fsl-dspi.txt | 8 ++++
drivers/spi/spi-fsl-dspi.c | 54 ++++++++++++++++------
2 files changed, 49 insertions(+), 13 deletions(-)
--
2.11.0
next reply other threads:[~2018-09-18 9:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 9:34 Lukasz Majewski [this message]
2018-09-18 9:34 ` [PATCH 1/3] dt-bindings: spi: Provide bindings for fsl dspi working in slave mode Lukasz Majewski
2018-09-24 21:25 ` Rob Herring
2018-09-26 14:32 ` Lukasz Majewski
2018-09-26 15:37 ` Geert Uytterhoeven
2018-09-26 21:33 ` Lukasz Majewski
2018-09-18 9:34 ` [PATCH 2/3] ARM: dspi: Provide per DSPI instance of the MCR register (SLAVE mode) Lukasz Majewski
2018-09-18 9:34 ` [PATCH 3/3] ARM: dspi: Provide support for DSPI slave more operation (Vybryd vf610) Lukasz Majewski
2018-09-18 9:42 ` [PATCH 0/3] ARM: dspi: Provide slave mode support for Vybryd vf610 Lukasz Majewski
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=20180918093437.26799-1-lukma@denx.de \
--to=lukma@denx.de \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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).