uadk: adjust internal file include relationships #527
Closed
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 file inclusion relationship in the current uadk is confusing, and there are multiple repeated inclusions, which leads to confusion in the internal inclusion relationship.
In addition, the interface to the APP application layer and the interface to the user mode driver layer are mixed together, making it inconvenient for the APP application layer to use UADK. After adjustment, when the APP application layer calls the uadk interface to execute services, it only needs to call the header file of the corresponding algorithm , and driver development only needs to include its own header file and the driver-side interface of the corresponding algorithm.