public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Péter Ujfalusi" <peter.ujfalusi@ti.com>
To: Maximilian Schwerin <Maximilian.Schwerin@tigris.de>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: ALSA SoC TWL4030 driver
Date: Tue, 16 Aug 2011 17:16:01 +0300	[thread overview]
Message-ID: <5512338.Wi2WCLqT7N@barack> (raw)
In-Reply-To: <5448984682E7954C9BFF27F747A9C6CA4EAEF5@dolphin.TIGRIS.local>

On Tuesday 16 August 2011 15:33:09 Maximilian Schwerin wrote:
> Hi,
> 
> I'm currently working on a beagle board clone.
> 
> I've got some problems getting the micbias1 output on the TPS65950 to work.
> I can record audio coming from a line out or if I connect micbias1 to an
> extern 1.8V supply.
> 
> /sys/devices/platform/soc-audio/TWL4030/dapm_widget shows Mic Bias 1 to be
> off at all times. Is there something I have to do to enable this other than
> to start recording? Or could this be a bug in the driver? Does anyone have
> experience with the mic input of the TPS65950?

In your machine driver you need to connect the corresponding mic bias, like it 
is done in for example for zoom2:

	/* Headset Mic: HSMIC with bias */
	{"HSMIC", NULL, "Headset Mic Bias"},
	{"Headset Mic Bias", NULL, "Headset Mic"},

Note: Beagle only have support for line-in, does your board have additional 
inputs jack (Headset?)

-- 
Péter
--
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:[~2011-08-16 14:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-16 13:33 ALSA SoC TWL4030 driver Maximilian Schwerin
2011-08-16 14:16 ` Péter Ujfalusi [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=5512338.Wi2WCLqT7N@barack \
    --to=peter.ujfalusi@ti.com \
    --cc=Maximilian.Schwerin@tigris.de \
    --cc=linux-omap@vger.kernel.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