[alsa-devel] commit: dpcm: Allow FE to be opened without valid BE routes
anish198519851985 at gmail.com
Wed Nov 7 13:56:39 CET 2012
On Wed, 2012-11-07 at 09:48 +0100, Mark Brown wrote:
> 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.
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
Thanks for reading.
> > 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.
More information about the Alsa-devel