All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Henningsson <david.henningsson@canonical.com>
To: Keith Chew <keith.chew@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: 5.1 surround on 3 jacks (retasking)
Date: Thu, 26 Aug 2010 08:56:12 +0200	[thread overview]
Message-ID: <4C76100C.3040205@canonical.com> (raw)
In-Reply-To: <AANLkTinE8sjRWWsHYJYq1w_rLJu9Y91J4gs7k-Q_M3j-@mail.gmail.com>

2010-08-26 08:35, Keith Chew skrev:
>> My first approach to that problem would be to try to tweak
>> user_pin_configs, assuming that the generic parser (model=auto) is used.
>> See sections 4.3 and 4.4 on this document for how to do that:
>>
>> http://mirror.leaseweb.com/kernel/people/tiwai/docs/HD-Audio.html
>>
>> That way you won't have to update the kernel code at all.
>>
>> To figure out the values of user_pin_configs, you'll need to know the
>> pin widget NIDs (see your /proc/asound/card*/codec* file for that) and
>> pin values (see official Intel HDA documentation, or read hda_proc.c).
>>
> Hi David
> 
> Thank you very much for your guidance, I have gotten a bit further,
> and this is very exciting!
> 
> After reading HD-Audio.html, I used the hda-analyzer to configure NIDs
> 0x14, 0x19 and 0x1b to become outputs, and when I execute:
> 
> speaker-test -Dplug:surround51 -c6
> 
> I can hear sound on all 3 jacks, but only for Front left/right
> channels. In other words, all 3 jacks are being treated as Front. To
> confirm this, in alsamixer, the mute on Front (0x14) does mute all 3
> jacks.
> 
> I guess I am missing the relationship between alsamixer and the codec.
> How can I get aplay and speaker-test (with plug:surround51) to map to
> Front/Mic2/Line2, now that I have configured them as outputs?

I'm not 100% sure, but I think that HDA-analyzer approach will probably
not work here as you'll need a complete codec reconfig. After the
reconfig, you shouldn't even have a "Line in" in alsamixer, instead you
should have volume controls for "rear" and "center/lfe".
Also make sure that the pin configs are configured as "front", "rear",
and "center/lfe".


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

  reply	other threads:[~2010-08-26  6:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-25 19:45 5.1 surround on 3 jacks (retasking) Keith Chew
2010-08-25 23:31 ` David Henningsson
2010-08-26  6:35   ` Keith Chew
2010-08-26  6:56     ` David Henningsson [this message]
2010-08-26  7:16       ` Keith Chew
2010-08-26 23:19       ` Keith Chew
2010-08-28 14:11         ` Keith Chew
2010-08-28 14:55           ` David Henningsson
2010-08-28 15:08             ` Keith Chew
2010-08-30  7:51               ` Takashi Iwai
2010-08-30 19:45                 ` Keith Chew
2010-08-30 20:23                   ` Takashi Iwai
2010-08-30 20:58                     ` Keith Chew
2010-08-26  7:03 ` Raymond Yau
2010-08-26  7:22   ` Keith Chew

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=4C76100C.3040205@canonical.com \
    --to=david.henningsson@canonical.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=keith.chew@gmail.com \
    /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.