From: Lars-Peter Clausen <lars@metafoo.de>
To: noman pouigt <variksla@gmail.com>, tiwai@suse.de, perex@perex.cz
Cc: alsa-user@lists.sourceforge.net,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
omer.job@gmail.com
Subject: Re: ASoC: Max98090 Codec DAPM Widget setup in Open Embedded
Date: Tue, 24 Mar 2015 08:26:59 +0100 [thread overview]
Message-ID: <551111C3.3000704@metafoo.de> (raw)
In-Reply-To: <CAES_P+9kc9Q6TR7e1rdjV8cWHGWJs9bHoMLOz0Z0iHaYZbqpQw@mail.gmail.com>
On 03/24/2015 07:54 AM, noman pouigt wrote:
> On Mon, Mar 23, 2015 at 11:53 PM, noman pouigt <variksla@gmail.com> wrote:
>>> I would like to know which file I can use to connect/enable
>>> DPAM widgets permanently so a simple aplay/record can work?
>>>
>>> My environment is:
>>> - Yocto Linux Kernel 3.10 - (DTS based)
>>> - Max98090 Codec
>>> - imx6SL SoC
>>>
>>> I thought about doing this in alsa.conf or asound.conf but I couldn't
>>> find a single example with DAPM widgets .
>>
>> I am also stuck with the same problem. I am sure ALSA experts
>> can help here.
>>
>> What i want to know is how to set the dapm widgets in open
>> embedded? Is it alsa.conf or asound.conf ?
>>
>> I need to set something like this:
>> amixer cset name="LEFT MIXER DAC" 1
>>
>> Using amixer i am able to playback but i don't know how can i
>> modify conf file to have this dapm widgets associated with
>> a device.
>>
>> Any example would suffice.
Hi,
The whole point of DAPM (dynamic audio power management) is that you don't
have to manually power up or down a widget. Userspace configures the routing
of the audio paths and the kernel automatically detects which parts of the
chip need to be powered up for the current routing configuration.
Why do you want to manually enable a widget?
- Lars
next prev parent reply other threads:[~2015-03-24 7:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 6:54 ASoC: Max98090 Codec DAPM Widget setup in Open Embedded noman pouigt
2015-03-24 7:26 ` Lars-Peter Clausen [this message]
2015-03-24 16:02 ` Variksla
2015-03-25 7:22 ` Omer
-- strict thread matches above, loose matches on Subject: below --
2015-03-20 22:25 C. Omer Rafique
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=551111C3.3000704@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=alsa-user@lists.sourceforge.net \
--cc=omer.job@gmail.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
--cc=variksla@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.