public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Nikula <jhnikula@gmail.com>
To: "Rok Markovič" <rok@kanardia.eu>
Cc: linux-omap@vger.kernel.org
Subject: Re: Asoc with TWL4030 on overo
Date: Thu, 18 Mar 2010 16:40:02 +0200	[thread overview]
Message-ID: <20100318164002.70c710a3.jhnikula@gmail.com> (raw)
In-Reply-To: <201003180823.55248.rok@kanardia.eu>

Hi

On Thu, 18 Mar 2010 08:23:55 +0100
Rok Markovič <rok@kanardia.eu> wrote:

> I am trying to play sound on overo board. With latest kernel I cannot get 
> any sound, while with kernel 2.6.33-rc6-07400-ga05966f-dirty sound is 
> played by ALSA correctly. I am using ALSA 1.0.22 with asound.conf like 

Beagle plays fine on linux-omap head. One reason could be the patch
below as it requires that the user space must activate the headset
output path by proper mixer settings.

commit e47c796d58a21fc58b00dffb7265bb66de987773
Author: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Date:   Wed Feb 17 09:49:54 2010 +0200

    ASoC: TWL4030: Use codec defaults for Headset initial configuration
    
    Disable the amplifiers for the headset outputs, and do not select
    routings by default to the headset outputs.


Does it work if you active the Headset path?

amixer set -D hw:0 'Headset' 0dB
amixer set -D hw:0 'HeadsetL Mixer AudioL2' on
amixer set -D hw:0 'HeadsetR Mixer AudioR2' on


-- 
Jarkko
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-03-18 14:38 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 [this message]
2010-03-18 14:52   ` Rok Markovič
2010-03-18 15:42     ` 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=20100318164002.70c710a3.jhnikula@gmail.com \
    --to=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