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

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

The control status with the FIX-UP (and the new pin config) is:
Master: controls the hp volume
Front: dummy
Surround: dummy
Center: dummy
LFE: dummy

> > 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 speaker was moved to line_out, so cfg->speaker_outs == 0.

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

the mac book pro has a built in speaker, a built in microphone and two
jacks. One is a spdif output and headphone. The other one is a spdif
in and a line in.

The controls should be:
Speaker, Microphone, select builtin mic/line-in . I am not sure if
there should be two different controls or one control and one select
switch for the mic/line-in. Currently I also have IEC958 to turn on
the spdif output.

I don't have any spdif equipment. I also don't have an external
microphone, but I am sure I can get one for testing.

> but no Master (as STAC codec controls these outputs individually).
Right. I love that :-)

> 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.
I will give it a try latter on.

> Takashi
>

Rafael

-------------------------------------------------------------------------
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 20: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
2007-02-20 20:05         ` Rafael Espíndola [this message]
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=564d96fb0702201205i11beca64g11ca9602a53ad433@mail.gmail.com \
    --to=rafael.espindola@gmail.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=tiwai@suse.de \
    /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