From: "Pali Rohár" <pali.rohar@gmail.com>
To: Tony Lindgren <tony@atomide.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Jarkko Nikula <jarkko.nikula@bitmer.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: 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: Nokia N900 headset detection & MIC Bias + TVOUT
Date: Sat, 7 Jan 2017 00:07:49 +0100 [thread overview]
Message-ID: <201701070007.49137@pali> (raw)
[-- Attachment #1: Type: Text/Plain, Size: 915 bytes --]
Hi!
For jack cable and headset detection in Nokia N900 I would need to
enable/disable MIC Bias and also enable/disable TVOUT output.
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.
And according to RX-51 Schematics TVOUT is controlled by OMAP3430 pins:
TV_OUT1 and TV_VFB1. I have not found any references to them in kernel,
just in omap trm. How is OMAP3430's TV_OUT1 controlled?
(Existing code in Maemo 2.6.28 kernel is doing it by big hack - exports
function which directly modify MICBIAS_CTRL)
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2017-01-06 23:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 23:07 Pali Rohár [this message]
2017-01-09 11:27 ` Nokia N900 headset detection & MIC Bias + TVOUT Mark Brown
2017-01-09 13:13 ` Pali Rohár
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=201701070007.49137@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.