From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4 v3] spi: spi-mem: Use 2 SPI messages instead of a single full-duplex one
Date: Thu, 9 Aug 2018 08:22:46 +0200 [thread overview]
Message-ID: <20180809062249.10889-1-sr@denx.de> (raw)
Some SPI controller do not support full-duplex SPI transfers. This patch
changes the SPI transfer into 2 separate transfers - or 1, if no data is
to be transmitted.
With this change, only a small buffer for the command, address and
dummy bytes needs to be allocated. We use the TX and RX buffers that are
passed to spi_mem_exec_op() directly.
Signed-off-by: Stefan Roese <sr@denx.de>
Suggested-by: Boris Brezillon <boris.brezillon@bootlin.com>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Boris Brezillon <boris.brezillon@bootlin.com>
Cc: Jagan Teki <jagan@openedev.com>
Reviewed-by: Boris Brezillon <boris.brezillon@bootlin.com>
---
v3:
- Allocate buffer for cmd, addr and dummy bytes
- Return code for spi_xfer is checked
- Drop rx_data and tx_data and use rx_buf / tx_buf instead
as suggested by Boris
- Minor coding style changes
v2:
- Replaces patch "spi: spi-mem: Add optional half-duplex SPI transfer mode"
from first patchset version
- No compile-time option but the default to use 2 separate SPI messages
to transfer the command and data
drivers/spi/spi-mem.c | 85 ++++++++++++++++++++++---------------------
1 file changed, 43 insertions(+), 42 deletions(-)
diff --git a/drivers/spi/spi-mem.c b/drivers/spi/spi-mem.c
index 07ce799170..af9aef009a 100644
--- a/drivers/spi/spi-mem.c
+++ b/drivers/spi/spi-mem.c
@@ -196,12 +196,14 @@ EXPORT_SYMBOL_GPL(spi_mem_supports_op);
*/
int spi_mem_exec_op(struct spi_slave *slave, const struct spi_mem_op *op)
{
- bool rx_data = op->data.nbytes && (op->data.dir == SPI_MEM_DATA_IN);
- bool tx_data = op->data.nbytes && (op->data.dir == SPI_MEM_DATA_OUT);
struct udevice *bus = slave->dev->parent;
struct dm_spi_ops *ops = spi_get_ops(bus);
- unsigned int xfer_len, pos = 0;
- u8 *tx_buf, *rx_buf = NULL;
+ unsigned int pos = 0;
+ const u8 *tx_buf = NULL;
+ u8 *rx_buf = NULL;
+ u8 *op_buf;
+ int op_len;
+ u32 flag;
int ret;
int i;
@@ -330,67 +332,66 @@ int spi_mem_exec_op(struct spi_slave *slave, const struct spi_mem_op *op)
return -ENOTSUPP;
}
- xfer_len = sizeof(op->cmd.opcode) + op->addr.nbytes +
- op->dummy.nbytes + op->data.nbytes;
-
- /*
- * Allocate a buffer to transmit the CMD, ADDR cycles with kmalloc() so
- * we're guaranteed that this buffer is DMA-able, as required by the
- * SPI layer.
- */
- tx_buf = kzalloc(xfer_len, GFP_KERNEL);
- if (!tx_buf)
- return -ENOMEM;
-
- if (rx_data) {
- rx_buf = kzalloc(xfer_len, GFP_KERNEL);
- if (!rx_buf)
- return -ENOMEM;
+ if (op->data.nbytes) {
+ if (op->data.dir == SPI_MEM_DATA_IN)
+ rx_buf = op->data.buf.in;
+ else
+ tx_buf = op->data.buf.out;
}
+ op_len = sizeof(op->cmd.opcode) + op->addr.nbytes + op->dummy.nbytes;
+ op_buf = calloc(1, op_len);
+
ret = spi_claim_bus(slave);
if (ret < 0)
return ret;
- tx_buf[pos++] = op->cmd.opcode;
+ op_buf[pos++] = op->cmd.opcode;
if (op->addr.nbytes) {
for (i = 0; i < op->addr.nbytes; i++)
- tx_buf[pos + i] = op->addr.val >>
- (8 * (op->addr.nbytes - i - 1));
+ op_buf[pos + i] = op->addr.val >>
+ (8 * (op->addr.nbytes - i - 1));
pos += op->addr.nbytes;
}
- if (op->dummy.nbytes) {
- memset(tx_buf + pos, 0xff, op->dummy.nbytes);
- pos += op->dummy.nbytes;
- }
+ if (op->dummy.nbytes)
+ memset(op_buf + pos, 0xff, op->dummy.nbytes);
+
+ /* 1st transfer: opcode + address + dummy cycles */
+ flag = SPI_XFER_BEGIN;
+ /* Make sure to set END bit if no tx or rx data messages follow */
+ if (!tx_buf && !rx_buf)
+ flag |= SPI_XFER_END;
+
+ ret = spi_xfer(slave, op_len * 8, op_buf, NULL, flag);
+ if (ret)
+ return ret;
- if (tx_data)
- memcpy(tx_buf + pos, op->data.buf.out, op->data.nbytes);
+ /* 2nd transfer: rx or tx data path */
+ if (tx_buf || rx_buf) {
+ ret = spi_xfer(slave, op->data.nbytes * 8, tx_buf,
+ rx_buf, SPI_XFER_END);
+ if (ret)
+ return ret;
+ }
- ret = spi_xfer(slave, xfer_len * 8, tx_buf, rx_buf,
- SPI_XFER_BEGIN | SPI_XFER_END);
spi_release_bus(slave);
for (i = 0; i < pos; i++)
- debug("%02x ", tx_buf[i]);
+ debug("%02x ", op_buf[i]);
debug("| [%dB %s] ",
- tx_data || rx_data ? op->data.nbytes : 0,
- tx_data || rx_data ? (tx_data ? "out" : "in") : "-");
- for (; i < xfer_len; i++)
- debug("%02x ", tx_data ? tx_buf[i] : rx_buf[i]);
+ tx_buf || rx_buf ? op->data.nbytes : 0,
+ tx_buf || rx_buf ? (tx_buf ? "out" : "in") : "-");
+ for (i = 0; i < op->data.nbytes; i++)
+ debug("%02x ", tx_buf ? tx_buf[i] : rx_buf[i]);
debug("[ret %d]\n", ret);
+ free(op_buf);
+
if (ret < 0)
return ret;
-
- if (rx_data)
- memcpy(op->data.buf.in, rx_buf + pos, op->data.nbytes);
-
- kfree(tx_buf);
- kfree(rx_buf);
#endif /* __UBOOT__ */
return 0;
--
2.18.0
next reply other threads:[~2018-08-09 6:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 6:22 Stefan Roese [this message]
2018-08-09 6:22 ` [U-Boot] [PATCH 2/4 v3] cmd: mtd: Don't abort erase operation when a bad block is detected Stefan Roese
2018-08-09 6:22 ` [U-Boot] [PATCH 3/4 v3] cmd: mtd: Don't use with negative return codes for shell commands Stefan Roese
2018-08-09 6:22 ` [U-Boot] [PATCH 4/4 v3] cmd: mtd: Add info text to mtd erase subcommand Stefan Roese
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=20180809062249.10889-1-sr@denx.de \
--to=sr@denx.de \
--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