From: Jagan Teki <jagan@amarulasolutions.com>
To: u-boot@lists.denx.de
Subject: [PATCH 0/3] spi: Support SPI I/O protocol lines
Date: Mon, 20 Apr 2020 17:39:18 +0530 [thread overview]
Message-ID: <20200420120921.12840-1-jagan@amarulasolutions.com> (raw)
Some of the SPI controllers have a special set of format
registers that defines how the transfer initiated to the
FIFO by means of I/O protocol lines.
Each mode of transfer from slave would be required to configure
the I/O protocol lines so-that the master would identify how
many number I/O protocol lines were used and alter the protocol
bits on the controller.
To address this issue (on these kinds of SPI controllers) this
series is trying to send the I/O protocol lines being used
on particular transfers.
patch 1: Transfer the opcode alone
patch 2: Add SPI I/O protocol lines via spi->proto
patch 3: Use spi->proto on SiFive SPI controller
Any inputs?
Jagan.
Jagan Teki (3):
spi: spi-mem: Xfer opcode alone for non spi-mem
spi: Support SPI I/O protocol lines
spi: sifive: Fix format register proto field
drivers/spi/spi-mem.c | 68 +++++++++++++++++++++++++---------------
drivers/spi/spi-sifive.c | 11 +++++--
drivers/spi/spi-uclass.c | 7 +++++
include/spi.h | 9 ++++++
4 files changed, 67 insertions(+), 28 deletions(-)
--
2.17.1
next reply other threads:[~2020-04-20 12:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 12:09 Jagan Teki [this message]
2020-04-20 12:09 ` [PATCH 1/3] spi: spi-mem: Xfer opcode alone for non spi-mem Jagan Teki
2020-04-20 12:09 ` [PATCH 2/3] spi: Support SPI I/O protocol lines Jagan Teki
2020-04-20 12:09 ` [PATCH 3/3] spi: sifive: Fix format register proto field Jagan Teki
2020-04-20 23:14 ` Bin Meng
2020-04-21 15:47 ` Sagar Kadam
2020-04-23 17:05 ` Jagan Teki
2020-04-21 7:19 ` [PATCH 0/3] spi: Support SPI I/O protocol lines Vignesh Raghavendra
2020-04-21 8:08 ` Jagan Teki
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=20200420120921.12840-1-jagan@amarulasolutions.com \
--to=jagan@amarulasolutions.com \
--cc=u-boot@lists.denx.de \
/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