alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Raymond Yau <superquad.vortex2@gmail.com>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: ALSA and MediaController
Date: Mon, 23 May 2011 13:39:08 +0800	[thread overview]
Message-ID: <BANLkTinyHbZWHUwEK0D4w1xrmKyLXRH-2w@mail.gmail.com> (raw)
In-Reply-To: <20110521105732.GA10004@sirena.org.uk>

2011/5/21 Mark Brown <broonie@opensource.wolfsonmicro.com>:
>
>> How Media controller or PA handle hda jack retasking of those 3 jacks
>> motherboard (channel mode or smart 5.1 switch) ?
>
>> For those mini ITX motherboard without front audio panel, there will
>> be no capture source if the HDA codec does not support stereo mix
>> after the driver retask those input jacks for 5.1 outputs
>
> This just sounds like a fairly basic reconfiguration of the CODEC, it's
> no different to any other rerouting.
>
>> Does this mean that those 3 jacks , 5 jacks and 6 jacks desktop need
>> to add the rear panel jack to use snd_jack_report ?
>
> It seems like a good idea to report any jacks we can do detection on....
>

But snd_jack API seem does not has any definition for "Line In" - Blue jacks ?

The jack retasking is performed by snd_hda_sequence_write_cache(codec,
chmode[mode].sequence) in snd_hda_ch_mode_put() for some HDA codecs

  reply	other threads:[~2011-05-23  5:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 17:48 ALSA and MediaController pl bossart
2011-05-17 18:02 ` Mark Brown
2011-05-17 18:06   ` Takashi Iwai
2011-05-17 18:43 ` Takashi Iwai
2011-05-17 20:57   ` Mark Brown
2011-05-21  2:43 ` Raymond Yau
2011-05-21 10:57   ` Mark Brown
2011-05-23  5:39     ` Raymond Yau [this message]
2011-05-23 15:00       ` 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=BANLkTinyHbZWHUwEK0D4w1xrmKyLXRH-2w@mail.gmail.com \
    --to=superquad.vortex2@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    /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;
as well as URLs for NNTP newsgroup(s).