All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Rafael Espíndola" <rafael.espindola@gmail.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Fwd: [PATCH] sound working on the macbook pro
Date: Tue, 20 Feb 2007 13:05:59 +0100	[thread overview]
Message-ID: <s5hhcthrq3c.wl%tiwai@suse.de> (raw)
In-Reply-To: <564d96fb0702200140u7aee7dfbt271ed3818ed92366@mail.gmail.com>

At Tue, 20 Feb 2007 09:40:35 +0000,
=?UTF-8?Q?Rafael_Esp=C3=ADndola?= wrote:
> 
> > How (and what) does it fail exactly?
> a "diff" of the trace without and with the fix-up is:
> 
> 1) snd_hda_parse_pin_def_config moves the speaker to the line_out
> 2) stac92xx_add_dyn_out_pins adds two line_outs
> 3) stac92xx_auto_create_multi_out_ctls creates the controls "Front",
> "Surround", Center, LFE

OK, this is basically the problem of stac92xx_add_dyn_out_pins() that
it adds surrounds unconditionally.
(BTW, just a curisotiy - would these surround and/or CLFE work as
 outputs?  Or does it have no [mic/line] input jack?)

> 4) stac92xx_auto_create_hp_ctls doesn't run add_spec_dacs or
> create_controls for the speaker. It then creates a control name Master
> instead of Headphone.

Hm, I don't get this yet.  The current auto-config code in
patch_sigmatel isn't 100% suitable for the laptop-style configurations
but rather for the desktop machines.  So, we need a slight redesign of
the configurator at first.  Let's get things straight now.

Please write down the pins you have on your device and what controls
should appear.  I suppose you have

- a HP pin
- a speaker pin
- a mic-in pin

What else?  And, for these controls, we'll have

- Speaker volume/switch
- Headphone volume/switch
- Captuer volume/switch
- Input Mux

but no Master (as STAC codec controls these outputs individually).


> > I'm sure that this would break many other devices.  So, the patch is
> > unacceptable as it is, unfortunately.
> >
> > The line_outs are actually primary outputs, not exactly "line-out".
> > You can find pretty many codes that refer to this as the primary
> > output.
> Do you consider changing this a long term goal? I agree that we should
> first try to get the sound working on the mac book, but the current
> implementation is strange IMHO.

Yes, there is certainly a room for improvements.
For example, we can add another field to indicate what is the primary
output type (line-out, speaker, HP) and stop moving the pin
information itself, so that the check of primary output is kept as
simple as now, and the original information won't be lost.


Takashi

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  reply	other threads:[~2007-02-20 12:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-18 17:06 [PATCH] sound working on the macbook pro Rafael Espíndola
     [not found] ` <564d96fb0702180924y32118e7esf81e5ec2514d3af9@mail.gmail.com>
2007-02-19 11:52   ` Fwd: " Takashi Iwai
2007-02-20  9:40     ` Rafael Espíndola
2007-02-20 12:05       ` Takashi Iwai [this message]
2007-02-20 20:05         ` Rafael Espíndola
2007-02-22 15:46           ` Takashi Iwai
2007-02-22 20:01             ` Rafael Espíndola
2007-02-23 14:32               ` Takashi Iwai
     [not found]                 ` <564d96fb0702262134t438dd480t45c83e556f315e2e@mail.gmail.com>
2007-03-07 23:01                   ` Takashi Iwai
2007-03-10  5:57                     ` Rafael Espíndola
2007-03-12 15:00                       ` Takashi Iwai
2007-03-13  7:14                         ` Rafael Espíndola
2007-03-13  9:41                           ` Takashi Iwai

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=s5hhcthrq3c.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=rafael.espindola@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.