author | Sujith S <sujith.s@ti.com> | |
Wed, 10 Mar 2021 09:00:27 +0000 (14:30 +0530) | ||
committer | Sujith S <sujith.s@ti.com> | |
Wed, 10 Mar 2021 09:00:27 +0000 (14:30 +0530) | ||
commit | f330068f7e9567f7071aa68a6ffde4f7d31e6eb1 | |
tree | 99ad20e4ffb871aa3aa40943a5a754c509087d64 | tree | snapshot (tar.xz tar.gz zip) |
parent | 49553e2e020016b893b13b0a141d8ecdda483487 | commit | diff |
PDK-6534 : un-expected ISR if the timer were running, before creation
If the timer was running before the timer was created, on creation
especially in user start mode, an ISR would be triggered before
the timer was started.
Root cause : The timer module is not reset before the ISR registration
so, if the timer count lapses after creation but before starting the
the timer, an FALSE isr would be triggered.
Fix: Reset the timer peripheral at create time. This ensures that
counter is disabled and interrupt notification is disabled
Testing: Tested both baremetal & ti rtos unit test of the timer, it
works as expected. OSAL_Baremetal_TestApp and OSAL_TestApp works as
expected
Signed-off-by: Sujith S <sujith.s@ti.com>
If the timer was running before the timer was created, on creation
especially in user start mode, an ISR would be triggered before
the timer was started.
Root cause : The timer module is not reset before the ISR registration
so, if the timer count lapses after creation but before starting the
the timer, an FALSE isr would be triggered.
Fix: Reset the timer peripheral at create time. This ensures that
counter is disabled and interrupt notification is disabled
Testing: Tested both baremetal & ti rtos unit test of the timer, it
works as expected. OSAL_Baremetal_TestApp and OSAL_TestApp works as
expected
Signed-off-by: Sujith S <sujith.s@ti.com>
packages/ti/osal/src/nonos/timer/v1/TimerP_nonos.c | diff | blob | history |