From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Rok Markovi?? <rok@kanardia.eu>
Cc: Jarkko Nikula <jhnikula@gmail.com>, linux-omap@vger.kernel.org
Subject: Re: Asoc with TWL4030 on overo
Date: Thu, 18 Mar 2010 15:42:57 +0000 [thread overview]
Message-ID: <20100318154256.GA17200@sirena.org.uk> (raw)
In-Reply-To: <201003181552.00203.rok@kanardia.eu>
On Thu, Mar 18, 2010 at 03:52:00PM +0100, Rok Markovi?? wrote:
> Yes muted sound was the culprit. :), why does not kernel enable sound by
> default and why are there so many mixer controls.
It is difficult for the kernel to know what a sensible configuration is
for all hardware at all times - much embedded hardware has a wide range
of possible audio configurations, and often the choice depends not only
on the hardware but also which sounds are being played.
prev parent reply other threads:[~2010-03-18 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 7:23 Asoc with TWL4030 on overo Rok Markovič
2010-03-18 14:40 ` Jarkko Nikula
2010-03-18 14:52 ` Rok Markovič
2010-03-18 15:42 ` 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=20100318154256.GA17200@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=jhnikula@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=rok@kanardia.eu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox