]> git.ipfire.org Git - thirdparty/kernel/linux.git/commit
ASoC: SOF: sof-client-probes-ipc4: Human readable debugfs "probe_points"
authorJyri Sarha <jyri.sarha@linux.intel.com>
Fri, 29 Aug 2025 09:30:21 +0000 (12:30 +0300)
committerMark Brown <broonie@kernel.org>
Fri, 29 Aug 2025 11:34:18 +0000 (13:34 +0200)
commitb6082647f7222c05d34db94455a4e81981c51da1
tree3c81415a53cd95bfd18f00c78a33178b25055df3
parente6cf5e44ce1eed7aa72e7fb0cbff054e3f1dec0d
ASoC: SOF: sof-client-probes-ipc4: Human readable debugfs "probe_points"

The current output of three integers is not very human readable. Use
ipc4 functions to describe in more detail what the struct
sof_probe_point_desc buffer_id is actually referring to in an ipc4 SOF
system.

Before this commit the "probe_points" debugfs file could read as:

Id: 0x01000004  Purpose: 0  Node id: 0x100
Id: 0x00000006  Purpose: 0  Node id: 0x100

And after in the same situation in an ipc4 system it reads:

0x7,0x0,0x100   gain.1.1 input buf idx 0 (connected)
0x1000005,0x0,0x100     host-copier.0.playback output buf idx 0 (connected)

The triplet in the beginning of the line can be used to reinserted the
probe point again by writing it into "probe_points" debugfs file, if
its first removed by writing the fist number in "probe_points_remove".
The last number is ignored when creating a probe point.

Signed-off-by: Jyri Sarha <jyri.sarha@linux.intel.com>
Reviewed-by: Liam Girdwood <liam.r.girdwood@intel.com>
Signed-off-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
Message-ID: <20250829093022.32094-5-peter.ujfalusi@linux.intel.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
sound/soc/sof/sof-client-probes-ipc4.c
sound/soc/sof/sof-client-probes.c
sound/soc/sof/sof-client-probes.h