From: Lu Guanqun <guanqun.lu@intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org
Subject: questions about asoc jack detection
Date: Wed, 20 Apr 2011 14:52:12 +0800 [thread overview]
Message-ID: <20110420065212.GC21880@qtel.sh.intel.com> (raw)
Hi Mark,
I have a question wrt jack detection, suppose now I have internal
speaker enabled and then headphone is inserted. According to the current
jack code in asoc, the Headphone pin wil be enabled, but it does nothing
to Internal Speaker. There is still sound coming out from speaker.
The possible solution is to let the application make the policy to
switch the output source to Headphone, because the jack event can be
observed. If we decide to let the userspace application make the policy,
then why do we bother to enable the jack pin at the first place?
Hope I'm not missing something here. Could you provide some insights?
Thanks!
--
guanqun
next reply other threads:[~2011-04-20 6:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 6:52 Lu Guanqun [this message]
2011-04-20 9:31 ` questions about asoc jack detection Mark Brown
2011-04-20 14:06 ` Lu Guanqun
2011-04-20 14:53 ` Mark Brown
2011-04-20 15:00 ` Lu Guanqun
2011-04-20 15:14 ` Tobin Davis
2011-04-21 0:29 ` Lu Guanqun
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=20110420065212.GC21880@qtel.sh.intel.com \
--to=guanqun.lu@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.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.