-
Notifications
You must be signed in to change notification settings - Fork 3k
QSPI write alignment fix for nRF52x #9866
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@j3hill, thank you for your changes. |
if (ret != NRF_SUCCESS ) { | ||
return QSPI_STATUS_ERROR; | ||
} | ||
pos+=diff; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
small change request : following coding style, using space around operators (pos < *length)
and similar
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've made the change, and I'll be sure to make the spacing consistent going forward.
If the data buffer for a write is not 4-byte aligned, use an aligned 16 byte buffer on the stack
CI started while idle and waiting for master fix . |
Test run: SUCCESSSummary: 13 of 13 test jobs passed |
Description
If the start address of the data buffer for a QSPI write operation is not WORD/4-byte aligned, use an aligned 16 x WORD length buffer on the stack
Pull request type