mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-11-10 23:24:38 +00:00
spi: spi-mem-nodm: Fix read data size issue
When slave drivers don't set the max_read_size, the spi-mem should
directly use data.nbytes and not limit to any size. But current
logic will limit to the max_write_size.
This commit mirrors the same changes in the dm version done in
commit 535b1fdb8e
("spi: spi-mem: Fix read data size issue").
Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Jagan Teki <jagan@amarulasolutions.com>
This commit is contained in:
parent
9102cce7f4
commit
cb42425aa1
1 changed files with 6 additions and 4 deletions
|
@ -93,12 +93,14 @@ int spi_mem_adjust_op_size(struct spi_slave *slave,
|
|||
if (slave->max_write_size && len > slave->max_write_size)
|
||||
return -EINVAL;
|
||||
|
||||
if (op->data.dir == SPI_MEM_DATA_IN && slave->max_read_size)
|
||||
op->data.nbytes = min(op->data.nbytes,
|
||||
slave->max_read_size);
|
||||
else if (slave->max_write_size)
|
||||
if (op->data.dir == SPI_MEM_DATA_IN) {
|
||||
if (slave->max_read_size)
|
||||
op->data.nbytes = min(op->data.nbytes,
|
||||
slave->max_read_size);
|
||||
} else if (slave->max_write_size) {
|
||||
op->data.nbytes = min(op->data.nbytes,
|
||||
slave->max_write_size - len);
|
||||
}
|
||||
|
||||
if (!op->data.nbytes)
|
||||
return -EINVAL;
|
||||
|
|
Loading…
Reference in a new issue