From: Patrick Lai <plai@codeaurora.org>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@ti.com>
Subject: Re: Run-time CODEC reset
Date: Sun, 13 Nov 2011 20:52:37 -0800 [thread overview]
Message-ID: <4EC09E95.8080907@codeaurora.org> (raw)
In-Reply-To: <201111130729.05961.marek.vasut@gmail.com>
On 11/12/2011 10:29 PM, Marek Vasut wrote:
>> Hi,
>>
>> I have a use case which requires CODEC to be reset at run-time. As
>> application exercises playback/capture through PCM device and mixer, my
>> understanding is that there is no interface for application to reset
>> CODEC through ALSA ASoC framework. CODEC driver would have to build
>> non-standard interface for this purpose. Is there precedence in any of
>> asoc CODEC driver which provides reset interface?
>
> Why not describe the hardware / submit a patch to support the hardware first ?
> 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.
Thanks
Patrick
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2011-11-14 4:52 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 [this message]
2011-11-14 21:29 ` 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=4EC09E95.8080907@codeaurora.org \
--to=plai@codeaurora.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@ti.com \
--cc=marek.vasut@gmail.com \
/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.