On Fri, Mar 05, 2021 at 08:07:19PM +0530, b_lkasam@codeaurora.org wrote:
On 2021-03-05 15:29, Mark Brown wrote:
this if you like? I can see that the separate tracepoint would be useful, I mostly use the regmap tracepoints for that purpose but not every widget has register I/O. Tracepoints are less noisy for the system as a whole than tracing every DAPM operation in dmesg, that tends to irritate other users if it's left in as standard.
Thanks Mark for the response. But this is not default err/info print and only dynamic debug print which should not result in noise. In case of customer OEMs/final product versions where less options of debugging, dynamic dmesg logging is preferable provided faster and this print is used to identify issues debug fastly sometimes.
This is precisely the use case tracepoints were added for and I know that they are being succesfully used in the development of major mobile handsets. They are very low overhead, you can even leave them recording in production usage without getting in anyone's way, and they're also simple to flip on and off at runtime.