alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Lai <plai@codeaurora.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Vinod Koul <vinod.koul@linux.intel.com>,
	alsa-devel <alsa-devel@alsa-project.org>,
	Liam Girdwood <lrg@ti.com>
Subject: Re: Signaling user-space through kcontrol
Date: Wed, 28 Sep 2011 09:27:31 -0700	[thread overview]
Message-ID: <4E834AF3.6020800@codeaurora.org> (raw)
In-Reply-To: <20110928104855.GA28309@sirena.org.uk>

> Something like that specific example should probably be reported via the
> snd_jack accessory detection infrastructure which can then offer a
> consistent interface between all sound cards with minimal work on the
> part of the individual driver.  There will doubtless be other examples
> though.

Agree that should go through consistent interface but not exactly sure
if going through input device interface is appropriate though. Isn't
the same reasoning why it has been decided to create ALSA specific API
for headset detection?

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

  reply	other threads:[~2011-09-28 17:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-28  6:14 Signaling user-space through kcontrol Patrick Lai
2011-09-28  6:15 ` Vinod Koul
2011-09-28  6:47   ` Patrick Lai
2011-09-28  7:03     ` Vinod Koul
2011-09-28  7:26       ` Patrick Lai
2011-09-28 10:48         ` Mark Brown
2011-09-28 16:27           ` Patrick Lai [this message]
2011-09-28 17:17             ` Mark Brown
2011-09-28  8:41 ` Clemens Ladisch
2011-09-28  9:33 ` Sebastian H.

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=4E834AF3.6020800@codeaurora.org \
    --to=plai@codeaurora.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@ti.com \
    --cc=vinod.koul@linux.intel.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).