Indexed based CMA allocation changes #9136
Open
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
Signed-off-by: bisingha <[email protected]>
|
clang-tidy review says "All clean, LGTM! 👍" |
bisingha-xilinx
added
Please do not Review
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.
Problem solved by the commit
Indexed based CMA bo allocation.
Bug / issue (if any) fixed, which PR introduced the bug, how it was discovered
It's not a Bug but a new feature to allocate CMA buffer object from a specific CMA memory region.
How problem was solved, alternative solutions (if any) and why they were rejected
Problem was solved by allocating memory from a specific CMA memory region. If user provides invalid cma memory region, the driver will allocate bo from the default CMA.
Risks (if any) associated the changes in the commit
n/a
What has been tested and how, request additional testing if necessary
Tested on some edge testcases
Documentation impact (if any)
n/a