Hi Mark,
On 06/10/2021 14:23, Mark Brown wrote:
On Wed, Oct 06, 2021 at 02:06:26PM +0300, Peter Ujfalusi wrote:
Hi,
The aim of this series is to clean up, make it easier to interpret and less 'chatty' prints aimed for debugging errors.
For example currently the DSP/IPC dump is printed every time we have an IPC timeout and it is posible to lost the first and more indicative dump to find the rootcause.
You might want to look at tracepoints and/or trace_printk, apart from anything else they're very useful for flight recorder style applications since they're very low overhead and have comparitively speeaking lots of storage available.
The trace infra is indeed a direction which would help on new hardware, architecture bringup.
I should have used different subject for the cover letter as the end result is to have better quality bug reports from users in the unlikely event that something goes wrong (mostly on the firmware side).
To speed up the turnaround to get it fixed as the first report should contain enough details to hint us where to look.
At the end the series will actually reduce the noise from dev_err() in case of a failure by printing only needed information without repetition.