From: Lu Guanqun <guanqun.lu@intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: questions about asoc jack detection
Date: Wed, 20 Apr 2011 23:00:20 +0800 [thread overview]
Message-ID: <20110420150020.GA12389@qtel.sh.intel.com> (raw)
In-Reply-To: <20110420145358.GB25571@sirena.org.uk>
On Wed, Apr 20, 2011 at 10:53:58PM +0800, Mark Brown wrote:
> On Wed, Apr 20, 2011 at 10:06:15PM +0800, Lu Guanqun wrote:
>
> > Yes, it's related to policy. But I see some inconsistencies in handling
> > this stuff. In this above example, you suggest we should play out of
> > both outputs. However in HDA code, the common way when headphone is
> > inserted is to mute the speaker and enable the headphone. Is there some
> > differences between the HDA code and the ASoC code? Or this is just due
> > to legacy code?
>
> HDA code does this differently. I'd argue that they've taken the wrong
> implementation decision and that this should be a userspace issue but
> the use cases for PCs are a bit more basic.
I agree with you that this kind of policy should be put into userspace
instead of hardcoding it in kernel.
Good to hear the points from you. Thanks!
--
guanqun
next prev parent reply other threads:[~2011-04-20 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 6:52 questions about asoc jack detection Lu Guanqun
2011-04-20 9:31 ` Mark Brown
2011-04-20 14:06 ` Lu Guanqun
2011-04-20 14:53 ` Mark Brown
2011-04-20 15:00 ` Lu Guanqun [this message]
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=20110420150020.GA12389@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.