From: "Pali Rohár" <pali.rohar@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Tony Lindgren <tony@atomide.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Jarkko Nikula <jarkko.nikula@bitmer.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Aaro Koskinen <aaro.koskinen@iki.fi>, Nishanth Menon <nm@ti.com>,
Sebastian Reichel <sre@kernel.org>, Pavel Machek <pavel@ucw.cz>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
joerg Reisenweber <joerg@openmoko.org>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Nokia N900 headset detection & MIC Bias + TVOUT
Date: Mon, 9 Jan 2017 14:13:17 +0100 [thread overview]
Message-ID: <20170109131317.GD26301@pali> (raw)
In-Reply-To: <20170109112749.6gmtytxuqzfai57e@sirena.org.uk>
On Monday 09 January 2017 11:27:49 Mark Brown wrote:
> On Sat, Jan 07, 2017 at 12:07:49AM +0100, Pali Rohár wrote:
>
> > All that is needed in N900 sound driver, file sound/soc/omap/rx51.c. Can
> > you help me which functions should I call to enable/disable it
> > correctly? In headset detection code I need to be sure that nobody
> > (other kernel drivers or userspace via alsamixer) except current
> > function could change Bias settings.
>
> > MIC Bias is controlled by MICBIAS_CTRL in aic34 'B' part codec, file
> > tlv320aic3x.c.
>
> Microphone biases are normally controlled by supply widgets and managed
> via DAPM. You can see quite a few examples of this in existing drivers.
So... can I call snd_soc_dapm_mutex_lock(dapm) at function startup,
start doing cable detection and when needed call this?
snd_soc_dapm_enable_pin_unlocked(dapm, "HS Mic");
snd_soc_dapm_sync_unlocked(dapm);
And at the end of function revert back "HS Mic" pin status and call
snd_soc_dapm_mutex_unlock(dapm)?
--
Pali Rohár
pali.rohar@gmail.com
next prev parent reply other threads:[~2017-01-09 13:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 23:07 Nokia N900 headset detection & MIC Bias + TVOUT Pali Rohár
2017-01-09 11:27 ` Mark Brown
2017-01-09 13:13 ` Pali Rohár [this message]
2017-01-09 19:22 ` Mark Brown
2017-01-09 19:29 ` Pali Rohár
2017-01-09 19:38 ` Mark Brown
2017-01-09 20:32 ` Pali Rohár
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=20170109131317.GD26301@pali \
--to=pali.rohar@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=broonie@kernel.org \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=jarkko.nikula@bitmer.com \
--cc=joerg@openmoko.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=pavel@ucw.cz \
--cc=peter.ujfalusi@ti.com \
--cc=sre@kernel.org \
--cc=tony@atomide.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.