From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: anish kumar <anish198519851985@gmail.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org, lrg@ti.com
Subject: Re: commit: dpcm: Allow FE to be opened without valid BE routes
Date: Wed, 7 Nov 2012 09:48:56 +0100 [thread overview]
Message-ID: <20121107084856.GC12323@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1352221394.4968.38.camel@anish-Inspiron-N5050>
[-- Attachment #1.1: Type: text/plain, Size: 849 bytes --]
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.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-11-07 8:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.495.1352127790.820.alsa-devel@alsa-project.org>
2012-11-06 17:03 ` commit: dpcm: Allow FE to be opened without valid BE routes anish kumar
2012-11-06 17:32 ` Liam Girdwood
2012-11-07 8:48 ` Mark Brown [this message]
2012-11-07 12:56 ` anish kumar
2012-11-07 14:28 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121107084856.GC12323@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=anish198519851985@gmail.com \
--cc=lrg@ti.com \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.