Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions developer_guides/debugability/logger/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -190,6 +190,34 @@ A similar example may be prepared for components on a particular pipeline:

sof-loggerr -l ldc_file -t -Fc=* -Fv=*1.*

.. note::
To track verbose message use firmware build with selected "Trace verbose"
option under "Trace" menu.

Active trace filters are stored in firmware runtime memory, so after firmware
restart (eg. after power gating in sleep mode) filters settings will be reset.
Consider disabling power gating during your debug session.
Comment thread
lgirdwood marked this conversation as resolved.
It may be done by:

.. code:: bash

sudo su
echo on >/sys/devices/pci0000\:00/0000\:$(lspci -nn | grep "audio contoller" | awk '{print $1;}')/power/control

.. note::
Current device power status may be read by this command:

.. code:: bash

cat /sys/devices/pci0000\:00/0000\:$(lspci -nn | grep "audio controller" | awk '{print $1;}')/power/runtime_status

Logger trace filtration affect only traces sent after filter setup, so traces
already stored on kernel side will not be affected.

Filters are setup incrementally, so when logger will be run-up twice with
different settings, then filters from first run will not be restored to default
state but can be replaced by new one.
To reset filters to default state, firmware reset is needed.

Detailed description
--------------------
Expand Down