From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: "Girdwood, Liam R" <liam.r.girdwood@intel.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Tanu Kaskinen <tanu.kaskinen@linux.intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH v3 1/2] ALSA: jack: create jack kcontrols for every jack input device
Date: Mon, 23 Mar 2015 07:57:30 -0700 [thread overview]
Message-ID: <20150323145730.GA14954@sirena.org.uk> (raw)
In-Reply-To: <s5hzj743p0x.wl-tiwai@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 582 bytes --]
On Mon, Mar 23, 2015 at 12:57:02PM +0100, Takashi Iwai wrote:
> It's a good point. The notification via kctl can't follow the
> complete state changes since it's nothing but a notification telling
> "something changed". So, events like buttons that need the complete
> state change history, the current implementation isn't appropriate.
> For things like jacks, we usually care only about the final state, and
> the state change is much less frequent, so kctl notification works
> well.
I'd expect the buttons to be going through only as input devices, not as
kcontrols at all.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-03-23 14:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 15:39 [PATCH v3 0/2] ALSA: jack: Refactoring for jack kctls Jie Yang
2015-03-20 15:39 ` [PATCH v3 1/2] ALSA: jack: create jack kcontrols for every jack input device Jie Yang
2015-03-20 16:17 ` Takashi Iwai
2015-03-21 2:22 ` Jie, Yang
2015-03-21 7:46 ` Takashi Iwai
2015-03-23 10:08 ` Tanu Kaskinen
2015-03-23 11:57 ` Takashi Iwai
2015-03-23 14:57 ` Mark Brown [this message]
2015-03-25 4:11 ` Jie, Yang
2015-03-25 5:27 ` Raymond Yau
2015-03-25 6:13 ` Takashi Iwai
2015-03-20 15:39 ` [PATCH v3 2/2] ALSA: hda - Remove jack kctls Jie Yang
2015-03-20 16:21 ` Takashi Iwai
2015-03-21 0:23 ` Jie, Yang
2015-03-23 9:18 ` [PATCH v3 0/2] ALSA: jack: Refactoring for " David Henningsson
2015-03-23 15:00 ` Mark Brown
2015-03-23 15:09 ` Takashi Iwai
2015-03-23 16:35 ` Mark Brown
2015-03-23 16:38 ` Takashi Iwai
2015-03-23 16:52 ` Mark Brown
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=20150323145730.GA14954@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=liam.r.girdwood@intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=tanu.kaskinen@linux.intel.com \
--cc=tiwai@suse.de \
/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