Commit c373643b authored by Mark Brown's avatar Mark Brown

spi: Remove note about transfer limit for spi_write_then_read()

Originally spi_write_then_read() used a fixed statically allocated
buffer which limited the maximum message size it could handle.  This
restriction was removed a while ago so that we could dynamically
allocate a buffer if required but the kerneldoc was not updated to
reflect this, do so.
Reported-by: default avatarMarc Kleine-Budde <mkl@pengutronix.de>
Signed-off-by: default avatarMark Brown <broonie@kernel.org>
Link: https://lore.kernel.org/r/20200525133120.57273-1-broonie@kernel.orgSigned-off-by: default avatarMark Brown <broonie@kernel.org>
parent aee67fe8
...@@ -3858,8 +3858,7 @@ static u8 *buf; ...@@ -3858,8 +3858,7 @@ static u8 *buf;
* is zero for success, else a negative errno status code. * is zero for success, else a negative errno status code.
* This call may only be used from a context that may sleep. * This call may only be used from a context that may sleep.
* *
* Parameters to this routine are always copied using a small buffer; * Parameters to this routine are always copied using a small buffer.
* portable code should never use this for more than 32 bytes.
* Performance-sensitive or bulk transfer code should instead use * Performance-sensitive or bulk transfer code should instead use
* spi_{async,sync}() calls with dma-safe buffers. * spi_{async,sync}() calls with dma-safe buffers.
* *
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment