24 May
2019
24 May
'19
2:29 p.m.
On Fri, May 24, 2019 at 12:54:27AM -0700, bgoswami@codeaurora.org wrote:
From: Banajit Goswami bgoswami@codeaurora.org
Add a debug log to help track widgets being powered-up and powered-down by DAPM.
We already have huge amounts of trace available via tracepoints and having something on by default in the debug logs seems like it's going to get very verbose for people who aren't specifically working on audio. What's the advantage of adding dev_dbg() logs as well?