-
Notifications
You must be signed in to change notification settings - Fork 288
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
apps: linux: generic: Use accessor functions for struct remoteproc_mem #563
Conversation
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.
do you plan to propose an update for other applications that also abuse of the remoteproc_mem
struct?
Yes, here let me add a couple more to this series. |
b7b23c3
to
e347711
Compare
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.
minor remarks , then LGTM but need ACK from AMD
The remoteproc_mem struct contents are internal to remoteproc. The struct should be accessed using the provided accessors, not directly. This is done in preparation of making this struct opaque to code outside of the remoteproc drivers. Signed-off-by: Andrew Davis <[email protected]>
The remoteproc_mem and rproc structs contents are internal to remoteproc. These should be accessed using the provided accessors, not directly. This is done in preparation of making these struct opaque to code outside of the remoteproc drivers. Signed-off-by: Andrew Davis <[email protected]>
The memory list is already initialized before this callback is called. Remove this redundant initialization. Signed-off-by: Andrew Davis <[email protected]>
e347711
to
408e698
Compare
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.
Looks good to go.
@tanmays, @bentheredonethat |
yes LGTM |
The remoteproc_mem struct contents are internal to remoteproc. The struct should be accessed using the provided accessors, not directly. This is done in preperation of making this struct opaque to code outside of the remoteproc drivers.