drivers: xspi: cache64: Fix cache management issue #597
+6
−6
Conversation
This file contains hidden or 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
Fix issue that the calculation of address is wrong. The last byte is not handled by cache api. Signed-off-by: Ruijia Wang <[email protected]>
SuperHeroAbner
force-pushed
the
support-xspi-on-rt700
branch
from
023ad6e to
efa778d
Compare
|
@Albort12138 to review the change. |
mmahadevan108
requested review from
ZhaoxiangJin,
decsny,
dleach02 and
mmahadevan108
|
Hello @SuperHeroAbner, is this patch unique to hal_nxp? Is this patch also in the SDK? |
|
@ZhaoxiangJin If it's a real issue. It should be also in SDK. Currently just fix this Zephyr test problem. |
|
Please coordinate this patch with the SDK-NG team and their update |
|
This change not in SDK, so just keep this PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Fix issue that the calculation of address is wrong. The last byte is not handled by cache api.