sample: drivers: counter: alarm: adapt test to driver change
Due to counter driver implementation change "driver/counter/counter_ll_stm32_rtc.c: Add 1 tick to alarm" It is necessary to adapt sample test (sanitycheck) to take into consideration 1 tick precision/tolerance. Signed-off-by: Alexandre Bourdiol <alexandre.bourdiol@st.com>
This commit is contained in:
parent
5559430654
commit
507ebecffc
2 changed files with 5 additions and 1 deletions
|
@ -9,6 +9,10 @@ This sample provides an example of alarm application using counter API.
|
||||||
It sets an alarm with an initial delay of 2 seconds. At each alarm
|
It sets an alarm with an initial delay of 2 seconds. At each alarm
|
||||||
expiry, a new alarm is configured with a delay multiplied by 2.
|
expiry, a new alarm is configured with a delay multiplied by 2.
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
In case of 1Hz frequency (RTC for example), precision is 1 second.
|
||||||
|
Therefore, the sample output may differ in 1 second
|
||||||
|
|
||||||
Requirements
|
Requirements
|
||||||
************
|
************
|
||||||
|
|
||||||
|
|
|
@ -13,5 +13,5 @@ tests:
|
||||||
- "Counter alarm sample"
|
- "Counter alarm sample"
|
||||||
- "Set alarm in 2 sec"
|
- "Set alarm in 2 sec"
|
||||||
- "!!! Alarm !!!"
|
- "!!! Alarm !!!"
|
||||||
- "Now: 2"
|
- "Now: [2|3]"
|
||||||
depends_on: counter
|
depends_on: counter
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue