On Wed, May 08, 2019 at 07:36:54AM -0700, Richard Cochran wrote:
> No the alarm functionality has been removed. It will not be coming
> back, unless there are really strong arguments to support it.
Here is some more background:
commit 3a06c7ac24f9f24ec059cd77c2dbdf7fbfd0aaaf
Author: Thom
On Wed, May 08, 2019 at 03:30:01AM +, Po Liu wrote:
> > Sorry, NAK, since we decided some time ago not to support timer_* operations
> > on dynamic clocks. You get much better application level timer performance
> > by synchronizing CLOCK_REALTIME to your PHC and using clock_nanosleep()
> > wi
org; linux-arm-ker...@lists.infradead.org; Y.b. Lu
> ; Claudiu Manoil ;
> da...@davemloft.net; Leo Li ; Roy Zang
> ; Mingkai Hu ;
> deepa.ker...@gmail.com
> Subject: [EXT] Re: [PATCH v1] timer:clock:ptp: add support the dynamic posix
> clock alarm set for ptp
>
> Caution: EXT Email
>
On Sun, May 05, 2019 at 05:02:05AM +, Po Liu wrote:
> Current kernel code do not support the dynamic posix clock alarm set.
> This code would support it by the posix timer structure.
>
> 319 const struct k_clock clock_posix_dynamic = {
>
> 320 .clock_getres = pc_clock_getres,
> 321
Current kernel code do not support the dynamic posix clock alarm set.
This code would support it by the posix timer structure.
319 const struct k_clock clock_posix_dynamic = {
320 .clock_getres = pc_clock_getres,
321 .clock_set = pc_clock_settime,
322 .clock_get