Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: liam.r.girdwood@intel.com, alsa-devel@alsa-project.org,
	David Henningsson <david.henningsson@canonical.com>
Subject: Re: [PATCH v3 0/2] ALSA: jack: Refactoring for jack kctls
Date: Mon, 23 Mar 2015 09:35:43 -0700	[thread overview]
Message-ID: <20150323163543.GD14954@sirena.org.uk> (raw)
In-Reply-To: <s5ha8z34uoi.wl-tiwai@suse.de>


[-- Attachment #1.1: Type: text/plain, Size: 996 bytes --]

On Mon, Mar 23, 2015 at 04:09:33PM +0100, Takashi Iwai wrote:

> Right, but it's a bit irrelevant.  We do want to have a common core
> code, indeed.  However, as David suggested, the latest patchset still
> doesn't care about "phantom" jack that is a mandatory feature.
> HD-audio create kctl items even for fixed pins without jack detection.
> This is needed for having consistent pin mapping.

OK, right - phantom jacks aren't something I was aware of.

> Now the question is whether we need representing the same item for
> input jack, even though it's nothing but a place holder.  If we want
> to have consistency between input and kctl jack items, then yes.
> OTOH, we might want to drop buttons from kctls in anyway, so such a
> consistency has no importance.  Then we may just ignore phantom jacks
> for input jacks but create only phatom jack kctls, too, either by
> adding a new flag to indicate that, or let type=0 behaving like that.

I'm not sure I see the relevancy of buttons here?

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2015-03-23 16:35 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
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 [this message]
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=20150323163543.GD14954@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=david.henningsson@canonical.com \
    --cc=liam.r.girdwood@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