On Wed, Nov 07, 2012 at 09:56:39PM +0900, anish kumar wrote:
On Wed, 2012-11-07 at 09:48 +0100, Mark Brown wrote:
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.
Probably I couldn't explain the problem clearly.Problem is that in our case we get sometimes(very random) audio mute in android devices due to UCM commands from the platform not sent properly or sent in such a way that FE and BE don't get connected. This issues are very hard to reproduce and only gets reproduced randomly by the test engineer and when it does happen, test engineer takes crash dump and provides us the log.So it is almost impossible to know what caused this audio mute at that time and all we have is this very log(dev_warn(FE and BE not connected)) to let us know that this mute was due to platform and not codec or any other problem with the kernel. Anyway looks like this idea is not liked by the community so I won't push further.
This really just sounds like a basic debugging issue, you can either add additional trace locally or work to improve the trace infrastructure - for example, make sure there's tracepoints showing what DPCM does in the same way there are tracepoints for DAPM.