alsa-devel.alsa-project.org archive mirror
 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 01:31:37 +0200	[thread overview]
Message-ID: <4C75A7D9.1030604@canonical.com> (raw)
In-Reply-To: <AANLkTin3DKSRuUZwARAadMTVPTrj17eHK8557bCsb3YM@mail.gmail.com>

2010-08-25 21:45, Keith Chew skrev:
> Hi
> 
> I have a small-form factor PC (KingYoung brand, model S645), which has
> 3 jacks connected to a Realtek ALC888 chipset. I have confirmed with
> the manufacturers the pin outs:
> 1) The front panel left side phone jack : Codec Line2-L & Line2-R (pin
> 14 & pin 15)
> 2) The front panel right side phone jack : Codec Mic2-L & Mic2-R (pin
> 16 & pin 17)
> 3) The back panel phone jack : Codec Front-L & Front-R (pin 35 & pin 36)
> 
> I would like to update patch_realtek.c in alsa-drivers, to output 5.1
> surround using these 3 jacks.
> 
> Can someone give me some guidance on how I can do this? I have looked
> and studied patch_realtek as much as I can, I just need some help in
> getting started.

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).

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

  reply	other threads:[~2010-08-25 23:31 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 [this message]
2010-08-26  6:35   ` Keith Chew
2010-08-26  6:56     ` David Henningsson
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=4C75A7D9.1030604@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 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).