Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Almohanad Fayez <alfayez@aol.com>
To: alsa-devel@alsa-project.org
Subject: TWL4030 Line In/Out Loopback issue
Date: Sun, 7 Aug 2011 20:27:45 -0400 (EDT)	[thread overview]
Message-ID: <8CE237920E8878A-21B8-2B9F7@webmail-d033.sysops.aol.com> (raw)


 I'verealized that there is a loopback dependency between the audioinput/output dependency with the 2.6.38 kernel running on a gumstix overo and also using the 2.6.35 kernel running on the Beaglenboard.

You can replicate this issue by plugging some music into the Line injack and then fire up alsamixer.  Then you would need to modify theDAC2 Dig level, the one on the right no the left.  As you lower thevolume you'll hear your music input decreasing and as you increase itthe music level would increase.  If you lower it enough you can captureaudio from the input jack without hearing it out of your speaker butthe bad thing is that also controls your speaker output so if you tryto play some sound out of gumstix/beagleboard you won't be able to do because youneed to increase your DAC2 Dig level in alsamixer ... it's a catch22!!  I couldn't find any solutions readily.

I am running a console-only Angstrom image on both boards.  I've used the Beagleboard's line in/out capabilities with no issues using the 2.6.29 kernel in the past so is there an update in the TWL4030 ALSA driver that I should take into account?  thanks


al fayez
 

             reply	other threads:[~2011-08-08  0:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-08  0:27 Almohanad Fayez [this message]
2011-08-08  8:56 ` TWL4030 Line In/Out Loopback issue Péter Ujfalusi
2011-08-08 15:01   ` Almohanad Fayez
2011-08-09  6:40     ` Péter Ujfalusi
2011-08-09 16:12       ` Almohanad Fayez

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=8CE237920E8878A-21B8-2B9F7@webmail-d033.sysops.aol.com \
    --to=alfayez@aol.com \
    --cc=alsa-devel@alsa-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox