[Cherry-Pick] Use configTICKRATE_HZ macro to set the systick configuration #172
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 / Feature
This PR upstreams the clock-setting fixes for 917SoC from release_2.7-1.4 branch to main.
Change overview
After integrating the sl_main component into the Matter application, we observed a timing discrepancy in the device clock. Specifically, the clock was lagging by approximately 2%—for every 100 seconds of real time, the device clock advanced only 98 seconds. This deviation resulted in failure of time-sensitive operation. The deviation is seen as the tick rate is not being used while setting the systick configuration.
To fix this drift, the tick rate macro is leveraged while setting the systick configuration.
Below commits from release_2.7-1.4 branch are being cherry-picked :
#158
#165
Testing
Tested the timing related test-cases (like cadmin test-cases, where a commissioning window would be opened only for a particular amount of time) with lighting-app and lock-app and ensured that the device clock is functioning without any errors.