alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Dylan Reid <dgreid@chromium.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: Jack detection on HDA vs SoC
Date: Sat, 4 Feb 2012 13:20:29 +0000	[thread overview]
Message-ID: <20120204132029.GA7438@sirena.org.uk> (raw)
In-Reply-To: <CAEUnVG4AGOk4tTC+KKiY_HgXNZs2wx5dD_mOy0vsaYP-ag24jA@mail.gmail.com>

On Fri, Feb 03, 2012 at 06:01:41PM -0800, Dylan Reid wrote:

You're more likely to get responses to mails if you CC maintainers.

> Is there a plan for the soc code to use the control-based method?

Not exactly.  I'm expecting that the new interface will be integrated
into the generic ALSA jack support rather than done as a custom thing in
the HDA drivers which will mean that anything supporting accessory
detect will get support, including ASoC.  This stuff should really be
handled in the core rather than in individual drivers, there's also
extcon which we'll need to integrate with.

> Is there a consensus on whether new drivers should auto-switch or not?

For embedded systems they definitely should not, it's frequently
inappropriate (the most common case is things like ringtones which many
userspaces think should always play to speaker so people can hear them
even if they have removed their headphones).  I think the consensus was
to move the PC audio to supporting runtime switching between the two
modes so that if PulseAudio or whatever userspace sound manager is there
wants to it can take control and do the switching for cases like the
above.

  parent reply	other threads:[~2012-02-04 13:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-04  2:01 Jack detection on HDA vs SoC Dylan Reid
2012-02-04  3:41 ` Raymond Yau
2012-02-04 13:20 ` Mark Brown [this message]
2012-02-04 14:02   ` Mark Brown
2012-02-06  9:48     ` Takashi Iwai
2012-02-06 11:06       ` Mark Brown
2012-02-06  7:56   ` Dylan Reid

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=20120204132029.GA7438@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=dgreid@chromium.org \
    /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).