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:21:17 -0400 [thread overview]
Message-ID: <48F8833D.8080301@embeddedalley.com> (raw)
In-Reply-To: <20081017103857.GA2546@sirena.org.uk>
Mark Brown wrote:
> On Fri, Oct 17, 2008 at 08:06:21AM +0200, Takashi Iwai wrote:
>> Matthew Ranostay wrote:
>
>>> Add support for detecting line out pin insertion and reporting
>>> back to userspace with the jack abstraction layer. Line outs
>>> are reported with the macro defined SW_LINEOUT_INSERT code.
>
>>> Signed-off-by: Matthew Ranostay <mranostay@embeddedalley.com>
>
>> Thanks for the patch. Added Dmitry and Mark to Cc for review.
>
> Matthew, as a general comment it would be helpful if you would split
> your patches up to separate out changes more and post as a series
> rather than as a single patch. Doing that makes review easier. For
> example, this patch includes both an addition to the jack reporting API
> and support for using it in a particular device.
Duly noted.
>
>> Adding one element should be fine, but I'm wondering whether more and
>> more pin type would come up in future...
>
> That was a fear here - the conclusion was that we deal with that when it
> gets to be a problem.
>
>>> SND_JACK_HEADPHONE = 0x0001,
>>> SND_JACK_MICROPHONE = 0x0002,
>>> SND_JACK_HEADSET = SND_JACK_HEADPHONE | SND_JACK_MICROPHONE,
>>> + SND_JACK_LINEOUT = 0x0004,
>>> };
>
>> So, you don't need to judge different line-outs, such as front and
>> rear?
>
No, at least not at the moment.
> 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? Of course this will require some changes
in snd_jack_report.
>>> + err = snd_jack_new(codec->bus->card,
>>> + "Lineout Jack",
>>> + SND_JACK_LINEOUT, &spec->lineout_jack);
>
> "Line Out" with two words.
>
next prev parent reply other threads:[~2008-10-17 12:21 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 [this message]
2008-10-17 12:39 ` Mark Brown
2008-10-17 12:53 ` Matthew Ranostay
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=48F8833D.8080301@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.