You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Send time since boot to the firmware upon resume #41
@ranj063 Which board and branch did you test? I am working on UP2 board and SOF firmware will get error after suspend/resume. Also, the /sys/kernel/debug/sof/trace file will be empty after suspend/resume. It implies that rmbox -t will show nothing.
On 3/1/19 1:38 AM, Bard Liao wrote:
Close it as we are using sof-logger now
I am not clear as to how sof-logger solves the issues of timestamps not
being aligned between host and firmware. If there is no IPC to pass the
system time on resume, then the timestamps generated by the firmware
will not be aligned and will restart at zero.
What am I missing?
@plbossart If I recall it correctly, the issue is for rmbox. The main issue is that the log will be clean after runtime suspend. But it seems no one complain about that on sof-logger. It can be reopen if we still need this feature.
@plbossart@bardliao yes, this issue remains irrespective of the tool and yes we do need the feature so we can align the time stamps between the kernel and the fw
@plbossart@ranj063 I guess we can send jiffies to align the time stamps. But how do we handle the clock difference between kernel and firmware? e.g. 1000 on kernel and 19.2M on FW.
Activity
bardliao commentedon Sep 11, 2018
@ranj063 Which board and branch did you test? I am working on UP2 board and SOF firmware will get error after suspend/resume. Also, the /sys/kernel/debug/sof/trace file will be empty after suspend/resume. It implies that rmbox -t will show nothing.
gro_cell: add napi_disable in gro_cells_destroy
gro_cell: add napi_disable in gro_cells_destroy
bardliao commentedon Mar 1, 2019
Close it as we are using sof-logger now
plbossart commentedon Mar 1, 2019
bardliao commentedon Mar 4, 2019
@plbossart If I recall it correctly, the issue is for rmbox. The main issue is that the log will be clean after runtime suspend. But it seems no one complain about that on sof-logger. It can be reopen if we still need this feature.
plbossart commentedon Mar 4, 2019
@bardliao the requirement is the same regardless of the tool.
@ranj063 do we send the time on a resume?
ranj063 commentedon Mar 4, 2019
@plbossart @bardliao yes, this issue remains irrespective of the tool and yes we do need the feature so we can align the time stamps between the kernel and the fw
plbossart commentedon Mar 24, 2019
@bardliao are you working on this or do we need to ask @mengdonglin to assign someone else. This is a simple problem that should be fixed.
bardliao commentedon Mar 25, 2019
@plbossart Yes, I can do it.
bardliao commentedon Mar 25, 2019
@plbossart @ranj063 I guess we can send jiffies to align the time stamps. But how do we handle the clock difference between kernel and firmware? e.g. 1000 on kernel and 19.2M on FW.
10 remaining items
Bluetooth: fix kernel oops in store_pending_adv_report
scsi: target: tcmu: Fix xarray RCU warning
mm/huge_memory: use pfn_to_online_page() in split_huge_pages_all()
r8169: fix the KCSAN reported data-race in rtl_tx() while reading tp-…
r8169: fix the KCSAN reported data-race in rtl_tx while reading TxDes…
r8169: fix the KCSAN reported data race in rtl_rx while reading desc-…
ACPICA: Apply pack(1) to union aml_resource
crypto: scompress - increment scomp_scratch_users when already allocated
ACPICA: Apply pack(1) to union aml_resource
ACPICA: Avoid undefined behavior: member access within misaligned add…
selftests/bpf: Run cgroup1_hierarchy test in own mount namespace
drm/amd/display: Fix null pointer deref in dcn20_resource.c
drm/amd/display: fix a UBSAN warning in DML2.1
hwpoison, memory_hotplug: lock folio before unmap hwpoisoned folio
mm/hugetlb: fix kernel NULL pointer dereference when replacing free h…