All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Ranostay <mranostay@embeddedalley.com>
To: Mark Brown <broonie@sirena.org.uk>
Cc: Takashi Iwai <tiwai@suse.de>, Dmitry Torokhov <dtor@mail.ru>,
	alsa-devel@alsa-project.org
Subject: Re: [PATCH] hda: add SW_LINEOUT_INSERT support
Date: Fri, 17 Oct 2008 08:53:17 -0400	[thread overview]
Message-ID: <48F88ABD.3010905@embeddedalley.com> (raw)
In-Reply-To: <20081017123928.GD2546@sirena.org.uk>

Mark Brown wrote:
> On Fri, Oct 17, 2008 at 08:21:17AM -0400, Matthew Ranostay wrote:
>> Mark Brown wrote:
> 
>>> For line outputs I think providing that information in the device name
>>> would be better - the reason for providing the distinction in the switch
>>> is to provide information when the function of the device attached to
>>> the jack changes at runtime.  As far as the hardware is concerned one
>>> line output is much the same as another.
> 
>> 	err = snd_jack_new(codec->bus->card,
>> 		"Jack Detection",
>> 		SND_JACK_HEADPHONE | SND_JACK_LINEOUT, &spec->jack);
> 
>> Do you mean something like this?
> 
> I'm not sure exactly what you mean by that change.  What the code says
> is that you have a single jack and can detect at runtime if the device
> plugged into it is a line or headphone.  If that is the case then yes,
> you should do something like that though that's not a very good name for
> the jack (ideally it should correspond to something like the label given
> to the jack on the machine case).
> 
Well is generally only one HP out jack, but there can be several line-out
reported by the one instance(lineout_jack). I assume this isn't the correct usage.

>>                                   Of course this will require some changes
>> in snd_jack_report.
> 
> Could you explain what changes you think are required?  The API already
> supports multi-function jacks.
> 

  reply	other threads:[~2008-10-17 12:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17  2:18 [PATCH] hda: add SW_LINEOUT_INSERT support Matthew Ranostay
2008-10-17  6:06 ` Takashi Iwai
2008-10-17 10:38   ` Mark Brown
2008-10-17 12:21     ` Matthew Ranostay
2008-10-17 12:39       ` Mark Brown
2008-10-17 12:53         ` Matthew Ranostay [this message]
2008-10-17 13:05           ` Mark Brown
2008-10-17 13:15             ` Matthew Ranostay
2008-10-17 14:19               ` 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=48F88ABD.3010905@embeddedalley.com \
    --to=mranostay@embeddedalley.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@sirena.org.uk \
    --cc=dtor@mail.ru \
    --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.