All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Henningsson <david.henningsson@canonical.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: [RFC PATCH] HDA: Generic input jack handling
Date: Sun, 09 Oct 2011 10:38:57 +0200	[thread overview]
Message-ID: <4E915DA1.5040405@canonical.com> (raw)
In-Reply-To: <s5hpqi8t0tv.wl%tiwai@suse.de>

On 10/08/2011 09:11 AM, Takashi Iwai wrote:
> At Fri, 07 Oct 2011 18:04:37 +0200,
> David Henningsson wrote:
>>
>> On 10/07/2011 05:27 PM, Takashi Iwai wrote:
>>> That being said, I'm inclined to delay it for 3.3.  Now is so close to
>>> the merge window and we don't need to rush for a refactoring patch.
>>> It can be done more safely in the early development cycle.
>>> Sorry if it disappoints you.
>>
>> This is much more than a refactoring patch - Realtek has no input jacks
>> for everything but headphones (and mics only if autoswitch is enabled),
>> so this is a good new feature. And my planned next step was to add it to
>> patch_via, which currently does not have input jacks at all.
>
> OK.
>
>> To give you some background here. As you might know, I've written
>> patches for PulseAudio to use these input jacks, that's why they're
>> suddenly so much more important. Also, it is not certain whether the
>> next release of Ubuntu (12.04, released April next year) will use kernel
>> 3.2 or 3.3. Should it be 3.3, this is not a problem, but if it is 3.2,
>> it would be better if all this was working upstream. Should it not be
>> working, I'll need to apply it for Ubuntu only instead.
>
> Well, then really you shouldn't be rushing too much.
> As mentioned, the API function will be needed to be changed because
> it's wrong to call with jack_type.  So, if you merge it in 3.2, you'll
> get anyway API/ABI incompatibility for further changes.
>
> That is, if it were a self-contained patch only in patch_realtek.c, I
> wouldn't mind too much.  But it's an addition of API in HD-audio code
> code, so I do care about it.

I don't like copy-pasting the same code into several vendor's patch 
files when the function should really be generic. Therefore I don't want 
to make several self-contained patches.

So if you feel uncomfortable with having the generic function in 3.2, 
queue it up for 3.3 (after I've changed the jack_type stuff to your 
preference) and I'll try to backport it into Ubuntu's 3.2 kernel, should 
it become necessary.

-- 
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic

  parent reply	other threads:[~2011-10-09  8:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-07 11:49 [RFC PATCH] HDA: Generic input jack handling David Henningsson
2011-10-07 11:52 ` Mark Brown
2011-10-07 12:08 ` Takashi Iwai
2011-10-07 12:46   ` David Henningsson
2011-10-07 13:03     ` Takashi Iwai
2011-10-07 15:11       ` David Henningsson
2011-10-07 15:27         ` Takashi Iwai
2011-10-07 16:04           ` David Henningsson
2011-10-08  7:11             ` Takashi Iwai
2011-10-08  7:29               ` Raymond Yau
2011-10-09  8:38               ` David Henningsson [this message]
2011-10-09 10:32                 ` Takashi Iwai
2011-10-09 11:14                   ` David Henningsson
2011-10-13  6:40                     ` Takashi Iwai
2011-10-18 13:13                       ` David Henningsson
2011-10-18 13:23                         ` Takashi Iwai

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=4E915DA1.5040405@canonical.com \
    --to=david.henningsson@canonical.com \
    --cc=alsa-devel@alsa-project.org \
    --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.