SPI Block maxsize #124
Open
SPI Block maxsize #124
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The SPI driver should, if possible, use as large buffer as possible. Currently, only
xfer3is adhering to the requested max blk size specified in/sys/module/spidev/parameters/bufsizbut is sending it in chunks. For all otherxferfunctions, the block size is limited to 4096.I believe that
xfer3was introduced to fix this, however, it is still limited to 4096 chunks.This PR aims to clarify
xfer3behavior and allow for arbitrary xfer buffer size.