Re: [PATCH v2] time: Fix get_ticks being non-monotonic

2021-03-01 Thread Sean Anderson
On 3/1/21 11:40 AM, Michael Opdenacker wrote: Hi Simon, I'm back working on this old issue. Thanks for your help with this! So, SPL support for Atmel/Microchip SAMA5D3 is still broken in the latest mainline, at least for the Xplained board with the MMC configuration. My comments and further

Re: [PATCH v2] time: Fix get_ticks being non-monotonic

2021-03-01 Thread Michael Opdenacker
Hi Simon, I'm back working on this old issue. Thanks for your help with this! So, SPL support for Atmel/Microchip SAMA5D3 is still broken in the latest mainline, at least for the Xplained board with the MMC configuration. My comments and further questions below... On 11/22/20 12:07 AM, Simon

Re: [PATCH v2] time: Fix get_ticks being non-monotonic

2020-11-21 Thread Simon Glass
Hi Michael, On Thu, 19 Nov 2020 at 04:23, Michael Opdenacker wrote: > > Hi, > > Sorry, no messaging quoting, I was not subscribed to the list at that time. > > Merging this change into master actually broke the SPL on > Atmel/Microchip SAMA5D3, at least booting from MMC: > > RomBOOT > > > Could

Re: [PATCH v2] time: Fix get_ticks being non-monotonic

2020-11-19 Thread Michael Opdenacker
Hi, Sorry, no messaging quoting, I was not subscribed to the list at that time. Merging this change into master actually broke the SPL on Atmel/Microchip SAMA5D3, at least booting from MMC: RomBOOT Could not initialize timer (err -11) Could not initialize timer (err -11) Could not

Re: [PATCH v2] time: Fix get_ticks being non-monotonic

2020-10-14 Thread Tom Rini
On Wed, Sep 09, 2020 at 04:24:56PM -0400, Sean Anderson wrote: > get_ticks does not always succeed. Sometimes it can be called before the > timer has been initialized. If it does, it returns a negative errno. > This causes the timer to appear non-monotonic, because the value will > become much

Re: [PATCH v2] time: Fix get_ticks being non-monotonic

2020-09-10 Thread Simon Glass
On Wed, 9 Sep 2020 at 14:25, Sean Anderson wrote: > > get_ticks does not always succeed. Sometimes it can be called before the > timer has been initialized. If it does, it returns a negative errno. > This causes the timer to appear non-monotonic, because the value will > become much smaller after

[PATCH v2] time: Fix get_ticks being non-monotonic

2020-09-09 Thread Sean Anderson
get_ticks does not always succeed. Sometimes it can be called before the timer has been initialized. If it does, it returns a negative errno. This causes the timer to appear non-monotonic, because the value will become much smaller after the timer is initialized. No users of get_ticks which I