The function below is the callback that is registered when the timer is set up. Of concern is the proper method to add time to the hrtimer for its next callback trigger. I am using ‘hrtimer_ add_expires_ns ‘ with the understanding that this will add xx ns to the time that was last set for the timer to expire.
So to answer this myself: This is a problem of wrong expectations. What we expected here is to set the timer forward during the callback by the amount we set (24us). But if we take a look at the kernel implementation of hrtimer_forward_now()we can see that the time is actually added to the last event/occurrence of the timer (see the calculation of delta):, Latest Bootlin videos and slides. given at the. Live Embedded Event, Linux kernel source tree. Contribute to torvalds/linux development by creating an account on GitHub .
Sign in. android / kernel / mediatek / android-6.0.1_r0.110 / . / kernel / hrtimer.c. blob: a29fbfcc3d132445493455ca7370635a65db5955 [] [] [], void hrtimer_ add_expires_ns (timer, u64 ns) ktime_t hrtimer_get_softexpires (timer) // without added tolerance (i.e. soft), Since commit 7dffa3c673fbcf835cd7be80bb4aec8ad3f51168 the ntp subsystem has used an hrtimer for triggering the leapsecond adjustment. However, this can cause a …
Latest Bootlin videos and slides. given at the. Live Embedded Event, Generated while processing linux/arch/x86/boot/compressed/acpi.c Generated on 2019-Mar-29 from project linux revision v5.1-rc2 Powered by Code Browser 2.1 Generator …
diff –git a/Makefile b/Makefile index a19c22a77728..9053bda13f60 100644— a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 3 PATCHLEVEL = 14-SUBLEVEL = 65
