All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: "Felipe F. Tonello" <eu@felipetonello.com>,
	alsa-devel@alsa-project.org, Jaroslav Kysela <perex@perex.cz>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] ALSA: Added jack detection KControl support
Date: Fri, 9 Aug 2013 17:39:47 +0100	[thread overview]
Message-ID: <20130809163947.GK6427@sirena.org.uk> (raw)
In-Reply-To: <s5h38qj2cqj.wl%tiwai@suse.de>

[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]

On Fri, Aug 09, 2013 at 03:52:04PM +0200, Takashi Iwai wrote:

> Above all, the multiple indices don't work anyway with the snd_jack
> stuff in the current form.  The index was introduced only for kjack,
> and for HD-audio, snd_jack is provided just for a compatibility
> reason, thus it doesn't matter much even if the multiple indices don't
> work with it. 

> That being said, before going further, we need to consider how to
> handle the input jack stuff with multiple indices.

What's the big problem with indexes and input (hopefully also extcon...)
reporting?

> > -	snprintf(jack->name, sizeof(jack->name), "%s %s",
> > +	snprintf(jack->name, sizeof(jack->name), "%s %s Jack",
> >  		 card->shortname, jack->id);

> This breaks the compatibility with the existing code.
> You must not change the name of the existing input jack element.
> Some drivers create "Headphone" and some do "Headphone Jack", yes.
> It's bad, but too late to change.

We can probably do something cheap like just check if there's a "Jack"
already in the name?

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-08-09 16:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02  7:59 [PATCH v2 0/2] ALSA: Implement core jack support for kcontrol Felipe F. Tonello
2013-08-02  7:59 ` Felipe F. Tonello
2013-08-02  7:59 ` [PATCH v2 1/2] ALSA: Added jack detection KControl support Felipe F. Tonello
2013-08-07 16:45   ` Mark Brown
2013-08-07 16:45     ` Mark Brown
2013-08-07 23:06     ` Felipe Tonello
2013-08-08  5:45     ` Takashi Iwai
2013-08-09  6:21   ` [PATCH v3 " Felipe F. Tonello
2013-08-09  6:21     ` Felipe F. Tonello
2013-08-09 13:52     ` Takashi Iwai
2013-08-09 13:52       ` Takashi Iwai
2013-08-09 16:39       ` Mark Brown [this message]
2013-08-09 16:51         ` Takashi Iwai
2013-08-09 17:36       ` Felipe Tonello
2013-08-09 17:36         ` Felipe Tonello
2013-08-12 10:39         ` Takashi Iwai
2013-08-12 10:54           ` Mark Brown
2013-08-12 10:54             ` Mark Brown
2013-08-12 18:34           ` Felipe Tonello
2013-08-02  7:59 ` [PATCH v2 2/2] ALSA: SoC: Fix jack names according new API Felipe F. Tonello

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=20130809163947.GK6427@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=eu@felipetonello.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --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 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.