From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Patrick Lai <plai@codeaurora.org>
Cc: Marek Vasut <marek.vasut@gmail.com>,
alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>
Subject: Re: Run-time CODEC reset
Date: Mon, 14 Nov 2011 21:29:47 +0000 [thread overview]
Message-ID: <20111114212946.GC6528@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4EC09E95.8080907@codeaurora.org>
On Sun, Nov 13, 2011 at 08:52:37PM -0800, Patrick Lai wrote:
> On 11/12/2011 10:29 PM, Marek Vasut wrote:
> >Then you can ask the developers for help. You can be helped more if you share
> >your problematic code.
> Actually, there is no bug. The use case is more to do with self test
> mode. After running some audio tests to verify different audio paths
> (i.e handset mode), self test application would like to trigger
> codec reset interface to restore CODEC default state. I was told
> that there are already ASOC CODEC drivers offering such interface. I
> want to see how this use case is handled by other CODEC drivers
> especially if command comes during playback/capture.
There's no such interface. This doesn't sound like something drivers
should support, it just sounds like your test application wants to save
the state before it starts and restore it afterwards, or the user should
use some external utility like alsactl to do so. Why would an
application care if the codec hardware had been physically reset, that's
the sort of detail that the driver should be hiding?
Patrick, we routinely need to ask you for this sort of background
information in order to understand what it is you're actually trying to
do. Normally you've already jumped very far into the implementation and
you don't mention the reasoning that you're relying on.
prev parent reply other threads:[~2011-11-14 21:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 6:15 Run-time CODEC reset Patrick Lai
2011-11-13 6:29 ` Marek Vasut
2011-11-14 4:52 ` Patrick Lai
2011-11-14 21:29 ` Mark Brown [this message]
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=20111114212946.GC6528@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.com \
--cc=marek.vasut@gmail.com \
--cc=plai@codeaurora.org \
/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.