tests-mbed_hal-common_tickers / lp ticker speed test : remove set_interrupt call loop

[jeromecoutant]

Description

There is some issue when lp_ticker_set_interrupt function is called into a loop with no delay between.

NB: extract of STM32 reference manual (in chip supporting LPTIM feature):
After a write to the LPTIM_ARR register or the LPTIM_CMP register, a new write operation
to the same register can only be performed when the previous write operation is completed.
Any successive write before respectively the ARROK flag or the CMPOK flag be set, will
lead to unpredictable results.

After dicussion, we decide to remove the loop and check requirement time during an unique call

@LMESTM @c1728p9 @sg- @bulislaw

Additional question:
is there really a sense to define the same requirement for ticker_set_interrupt time completion for usticket and lpticker ?

Pull request type

[X] Fix
[ ] Refactor
[ ] New target
[ ] Feature
[ ] Breaking change

[0xc0170]

@bulislaw @c1728p9 Can you review PR head issue? some tests do not build (lp timeout) due to some recent changes (rebase?), does not look related to this changeset

[jeromecoutant]

some tests do not build (lp timeout) due to some recent changes (rebase?)

yes, DEVICE_LOWPOWERTIMER #if has not been updated in TESTS\mbed_drivers\timeout\timeout_tests.h

[jeromecoutant]

Rebase done

[0xc0170]

/morph build

[0xc0170]

Still waiting for the review.

After a write to the LPTIM_ARR register or the LPTIM_CMP register, a new write operation
to the same register can only be performed when the previous write operation is completed.

Based on the description above, I would expect the target implementation handles the case (wait for completion of the command) ?

[mbed-ci]

Build : SUCCESS

Build number : 1650
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/6459/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build
/morph mbed2-build

[mbed-ci]

Exporter Build : SUCCESS

Build number : 1282
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/6459/

[mbed-ci]

Test : SUCCESS

Build number : 1439
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/6459/1439

[0xc0170]

After dicussion, we decide to remove the loop and check requirement time during an unique call

@c1728p9 Is this correct? Even with your latest ticker updates, is this PR still valid?

@LMESTM If we remove, we remove the lines, not commented out.

[LMESTM]

@0xc0170 Jerome (@jeromecoutant) is the one to remove lines instead of commenting out.
and yes, driver will make sure to not write in a timing that is not allowed by the hardware

[c1728p9]

With #6536 this test should pass even with the loop so this change may not be needed.

[0xc0170]

Thanks @c1728p9 for the confirmation, will wait for that one to land