From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: "linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>
Subject: Re: Automatically disabling internal speakers when headphones are plugged in
Date: Thu, 20 Jan 2011 20:39:20 +0000 [thread overview]
Message-ID: <20110120203920.GB1555@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF0310955716@HQMAIL01.nvidia.com>
On Thu, Jan 20, 2011 at 11:17:08AM -0800, Stephen Warren wrote:
> However, I wonder if that's the correct approach; should the plug detect
> logic only control the headphone output (i.e. only include the first array
> entry in jack_pins[] above), and leave it up to user-space whether to
> disable the speaker in this case, using a custom Speaker Function control
> created by the machine driver, as I see many other drivers expose?
You really should leave the headphone alone unless there's a reason the
two can't be simultaneously active (eg, being wired in parallel to the
same outputs or power constraints) but it won't break anything from an
ASoC point of view. It will disable some use cases, though, the main
one being that it won't be possible to play notifications to headphones
and speaker simultaneously. This is often used for notifications on
portable devices as the user may have inserted headphones during music
playback but removed them for some reason, rendering tones played only
through the headphones inaudible.
> Do the jack reports make it up to user-space so that could be implemented?
The jacks appear in userspace as input devices.
prev parent reply other threads:[~2011-01-20 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 19:17 Automatically disabling internal speakers when headphones are plugged in Stephen Warren
2011-01-20 20:39 ` Mark Brown [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=20110120203920.GB1555@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=swarren@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).