From: Takashi Iwai Subject: Re: Question about surround default pin config Date: Thu, 09 Aug 2012 15:01:39 +0200 Message-ID: References: <5023B25C.2070204@canonical.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (cantor2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id EAC502652BF for ; Thu, 9 Aug 2012 14:31:53 +0200 (CEST) In-Reply-To: <5023B25C.2070204@canonical.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: David Henningsson Cc: "alsa-devel@alsa-project.org" List-Id: alsa-devel@alsa-project.org At Thu, 09 Aug 2012 14:51:40 +0200, David Henningsson wrote: > > Hi, > > Sometimes it's better to just ask than getting confused trying to figure > it out yourself. > > When you have 2 stereo pairs of line-out or speaker, they are meant as > either 4.0 (front left, front right, rear left, rear right), and > sometimes they are meant as 2.1 (front left, front right, unused, lfe). > > We should support both variations, I assume. > > What is really the way to write my pin fixups to specify either 4.0 or > 2.1? Are there any de-facto standards? > > If I look at e g check_output_sfx (in hda_auto_parser.c), it looks like > it would be impossible to have 2.1, i e, impossible to have LFE without > also having rear left and rear right. But I might be missing something? Right, as of now, 2.1 configuration isn't supported by the parser. It's a bit messy. We can check the associated number whether it's 4.0 or 2.1, but I don't think there is a strict definition to differentiate between them. So, it'd end up with a guess work. Of course, we can add some special flag beforehand and let auto-parser handle 4.0 as 2.1. Takashi