Messages in this thread | | | From | Stanley Chu <> | Date | Tue, 2 Aug 2022 10:41:25 +0800 | Subject | Re: [PATCH v3] ufs: core: ufshcd: use local_clock() for debugging timestamps |
| |
On Tue, Aug 2, 2022 at 8:32 AM Daniil Lunev <dlunev@chromium.org> wrote: > > CLOCK_MONOTONIC is not advanced when the system is in suspend. This > becomes problematic when debugging issues related to suspend-resume: > the timestamps printed by ufshcd_print_trs can not be correlated with > dmesg entries, which are timestamped with local_clock(). > > This CL changes the used clock to local_clock() for the informational > timestamp variables and adds mirroring *_local_clock instances for > variables used in subsequent derevations (to not change the semantics of > those derevations). > > Signed-off-by: Daniil Lunev <dlunev@chromium.org>
Acked-by: Stanley Chu <stanley.chu@mediatek.com>
| |