On Wed, Nov 07, 2012 at 02:03:14AM +0900, anish kumar wrote:
As I can see this commit has changed the log level from dev_warn to dev_dbg but this has caused a subtle problem.Right now we rely on this warning to find out issues related to "application not sending UCM
You shouldn't be relying on parsing dmesg for anything, that's never going to be robust as you've just found. dmesg is for humans.
If everyone agrees then I would be more than happy to send a patch.
Please come up with a better way of identifying this; something like information in debugfs for example or working on getting the media controller API support merged and then using that to parse out the routing map from that and notice the misconfiguration. This would be much better anyway since the same thing can happen elsewhere in DAPM and your current mechanism.