diff options
| author | Pratyush Yadav <p.yadav@ti.com> | 2021-06-25 22:17:04 +0300 |
|---|---|---|
| committer | Jagan Teki <jagan@amarulasolutions.com> | 2021-06-28 09:25:11 +0300 |
| commit | d15de623013cbb3334e9466fafb0929e7f6a31c7 (patch) | |
| tree | 8413453cbbbd9d558babedda18ec1afc2c5014ac /drivers/spi/mtk_snfi_spi.c | |
| parent | a1eb40b70b40d208a72765c0f56cffed4e22ff30 (diff) | |
| download | u-boot-d15de623013cbb3334e9466fafb0929e7f6a31c7.tar.xz | |
spi: spi-mem: allow specifying a command's extension
In xSPI mode, flashes expect 2-byte opcodes. The second byte is called
the "command extension". There can be 3 types of extensions in xSPI:
repeat, invert, and hex. When the extension type is "repeat", the same
opcode is sent twice. When it is "invert", the second byte is the
inverse of the opcode. When it is "hex" an additional opcode byte based
is sent with the command whose value can be anything.
So, make opcode a 16-bit value and add a 'nbytes', similar to how
multiple address widths are handled.
All usages of sizeof(op->cmd.opcode) also need to be changed to be
op->cmd.nbytes because that is the actual indicator of opcode size.
Signed-off-by: Pratyush Yadav <p.yadav@ti.com>
Reviewed-by: Jagan Teki <jagan@amarulasolutions.com>
Diffstat (limited to 'drivers/spi/mtk_snfi_spi.c')
| -rw-r--r-- | drivers/spi/mtk_snfi_spi.c | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/drivers/spi/mtk_snfi_spi.c b/drivers/spi/mtk_snfi_spi.c index b6ab5fa3ad..65d0ce0981 100644 --- a/drivers/spi/mtk_snfi_spi.c +++ b/drivers/spi/mtk_snfi_spi.c @@ -64,8 +64,7 @@ static int mtk_snfi_adjust_op_size(struct spi_slave *slave, * or the output+input data must not exceed the GPRAM size. */ - nbytes = sizeof(op->cmd.opcode) + op->addr.nbytes + - op->dummy.nbytes; + nbytes = op->cmd.nbytes + op->addr.nbytes + op->dummy.nbytes; if (nbytes + op->data.nbytes <= SNFI_GPRAM_SIZE) return 0; |