[PATCH] posix: Fix relative CLOCK_REALTIME sleep

2022-08-01 Thread Sebastian Huber
A relative CLOCK_REALTIME time out shall not be affected by CLOCK_REALTIME changes through clock_settime(). Since our CLOCK_REALTIME is basically just CLOCK_MONOTONIC plus an offset, we can simply use the CLOCK_MONOTONIC watchdog for relative CLOCK_REALTIME time outs. Update #4690. --- cpukit/po

Re: [PATCH] posix: Fix relative CLOCK_REALTIME sleep

2022-08-01 Thread Chris Johns
On 1/8/2022 5:22 pm, Sebastian Huber wrote: > A relative CLOCK_REALTIME time out shall not be affected by CLOCK_REALTIME > changes through clock_settime(). Since our CLOCK_REALTIME is basically just > CLOCK_MONOTONIC plus an offset, we can simply use the CLOCK_MONOTONIC watchdog > for relative CLO

Re: [PATCH] posix: Fix relative CLOCK_REALTIME sleep

2022-08-01 Thread Sebastian Huber
On 01/08/2022 10:16, Chris Johns wrote: On 1/8/2022 5:22 pm, Sebastian Huber wrote: A relative CLOCK_REALTIME time out shall not be affected by CLOCK_REALTIME changes through clock_settime(). Since our CLOCK_REALTIME is basically just CLOCK_MONOTONIC plus an offset, we can simply use the CLOC

Re: [PATCH] posix: Fix relative CLOCK_REALTIME sleep

2022-08-01 Thread Chris Johns
On 1/8/2022 6:20 pm, Sebastian Huber wrote: > On 01/08/2022 10:16, Chris Johns wrote: >> On 1/8/2022 5:22 pm, Sebastian Huber wrote: >>> A relative CLOCK_REALTIME time out shall not be affected by CLOCK_REALTIME >>> changes through clock_settime().  Since our CLOCK_REALTIME is basically just >>> CL

Re: [PATCH] posix: Fix relative CLOCK_REALTIME sleep

2022-08-01 Thread Sebastian Huber
On 01/08/2022 10:48, Chris Johns wrote: On 1/8/2022 6:20 pm, Sebastian Huber wrote: On 01/08/2022 10:16, Chris Johns wrote: On 1/8/2022 5:22 pm, Sebastian Huber wrote: A relative CLOCK_REALTIME time out shall not be affected by CLOCK_REALTIME changes through clock_settime().  Since our CLOCK_R

Re: [PATCH v5 2/4] bsps: New GPIO API & peripherals API framework

2022-08-01 Thread oss
Hello Duc, Am 01.08.22 um 05:50 schrieb Duc Doan: Hello Christian, On Sat, 2022-07-30 at 17:50 +0200, o...@c-mauderer.de wrote: Hello Duc, Am 24.07.22 um 14:01 schrieb Duc Doan: ---   bsps/include/bsp/gpio2.h    | 528   bsps/include/bsp/periph_api.h

Re: [PATCH v5 1/4] bsps/stm32f4 Include STM32F4 HAL

2022-08-01 Thread oss
Hello Duc, Am 01.08.22 um 04:13 schrieb Duc Doan: Hello Christian, On Sun, 2022-07-31 at 20:01 +0200, o...@c-mauderer.de wrote: Hello Duc, Am 31.07.22 um 17:07 schrieb Duc Doan: Hello Christian, On Sat, 2022-07-30 at 16:32 +0200, o...@c-mauderer.de wrote: Hello Duc, general note for the p

Re: [PATCH] posix: Fix relative CLOCK_REALTIME sleep

2022-08-01 Thread Chris Johns
On 1/8/2022 6:52 pm, Sebastian Huber wrote: > On 01/08/2022 10:48, Chris Johns wrote: >> On 1/8/2022 6:20 pm, Sebastian Huber wrote: >>> On 01/08/2022 10:16, Chris Johns wrote: On 1/8/2022 5:22 pm, Sebastian Huber wrote: > A relative CLOCK_REALTIME time out shall not be affected by CLOCK_R

[PATCH] testsuite/psxclock: Check setting realtime clock

2022-08-01 Thread chrisj
Hi This patch adds a test to make sure threads sleeping on a clock_nanosleep(CLOCK_REALTIME) call are not effected by a change in the realtime clock via the clock_settime(CLOCK_REALTIME). The tests checks the sleeping thread's period using clock ticks. I have checked the test and Sebastian's p

[PATCH] testsuite/psxclock: Check setting realtime clock does not effect sleeping tasks

2022-08-01 Thread chrisj
From: Chris Johns Closes #4690 --- testsuites/psxtests/psxclock/init.c | 172 +++- 1 file changed, 171 insertions(+), 1 deletion(-) diff --git a/testsuites/psxtests/psxclock/init.c b/testsuites/psxtests/psxclock/init.c index 2300056f61..743cfa6d78 100644 --- a/testsuite

Re: [PATCH v5 1/4] bsps/stm32f4 Include STM32F4 HAL

2022-08-01 Thread Duc Doan
Hello Christian, On Mon, 2022-08-01 at 20:32 +0200, o...@c-mauderer.de wrote: > Hello Duc, > > Am 01.08.22 um 04:13 schrieb Duc Doan: > > Hello Christian, > > > > On Sun, 2022-07-31 at 20:01 +0200, o...@c-mauderer.de wrote: > > > Hello Duc, > > > > > > Am 31.07.22 um 17:07 schrieb Duc Doan: > >