Make the CRC Platform Abstraction Layer multi-context-safe#90
Open
parmi93 wants to merge 1 commit into
Open
Conversation
22074e5 to
13a4548
Compare
Contributor
Author
|
I just realized that this PR targets the |
71273fe to
eda5991
Compare
Contributor
|
Tx to solve conflicts.
|
13a4548 to
a709937
Compare
Contributor
Author
|
Fix the conflicts by rebasing my branch ( |
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
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.
stse_crc16_context_tstruct context.stse_platform_Crc16_ContextInit()andstse_platform_Crc16_ContextRelease()PAL APIs.stse_platform_Crc16_Accumulate()PAL API.stse_platform_Crc16_Calculate()PAL API.These changes resolve issue #65 by allowing users to adapt the CRC16 PAL implementation to scenarios where communication with multiple STSAFE devices takes place concurrently.
Additionally, they make it possible to implement thread-safe CRC16 PAL APIs when CRC computation is performed by a shared hardware peripheral. This ensures that concurrent access from multiple threads can be managed safely, even when those threads are not necessarily communicating with different STSAFE devices.