- 
                Notifications
    
You must be signed in to change notification settings  - Fork 8.2k
 
net: coap: Use 64bit timestamps #61026
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| 
           This PR should not be merged before #60887 but I just posted it to review before that.  | 
    
| 
           Can you please add a release note about the tickless operation and the 64-bit timestamps?  | 
    
f273abf    to
    81b85dd      
    Compare
  
    
          
 Added release notes as well.  | 
    
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
05cd0af    to
    99b3769      
    Compare
  
    | 
           Fixed the documentation build failure (minor whitespace problem).  | 
    
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we move to an implementation using the new timepoint API (#60232)?
          
 @SeppoTakalo @rlubos could you take a look and consider it as a follow-up?  | 
    
Use 64bit timestamps from k_uptime_get() so they don't roll over during the expected device lifetime. Fixes zephyrproject-rtos#60826 Signed-off-by: Seppo Takalo <seppo.takalo@nordicsemi.no>
CoAP fixes contain 64bit timer values. LwM2M now supports tickless mode. Signed-off-by: Seppo Takalo <seppo.takalo@nordicsemi.no>
99b3769    to
    92b5f92      
    Compare
  
    | 
           Apparently I left one bug in   | 
    
          
 I need to take a look. This is a new API for me which I was not aware of.  | 
    
| 
           Using these timepoints API would fix potential integer conversion problems. But there is one feature missing, comparison. In CoAP and LwM2M engine there are lists of potential timeouts and it would need a function to compare those and return a next timestamp to expire.  | 
    
          
 Could you please open an issue with the missing functionality and assign it to @npitre ?  | 
    
| 
           Actually, I just create a proposal PR, as this was (looking like) trivial problem #61037  | 
    
Use 64bit timestamps from k_uptime_get() so they don't roll over during the expected device lifetime.
Fixes #60826