alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Reimundo Heluani <rheluani@gmail.com>
To: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: Macbook Air 2,1 - no mic nor main speakers
Date: Mon, 22 Feb 2010 00:02:13 -0800	[thread overview]
Message-ID: <1266825733.3074.19.camel@vino> (raw)
In-Reply-To: <s5h7hq54sd8.wl%tiwai@suse.de>

On Mon, 2010-02-22 at 08:55 +0100, Takashi Iwai wrote:
> At Sun, 21 Feb 2010 22:30:58 -0800,
> Reimundo Heluani wrote:
> > 
> > On Sat, 2010-02-06 at 10:27 -0800, Reimundo Heluani wrote:
> > > Hello list, this came up a year ago and Takashi's answer was "a broken
> > > bios". I was hoping someone here could point me to documentation to read
> > > in order to diagnose the problem if indeed is a broken bios. I don't
> > > want to start randombly reading the driver's code.
> > > 
> > > Macbook Air 2,1
> > > 2.6.32-gentoo-r3 SMP x86_64
> > > Alsa Driver 1.0.21 libs 1.0.22
> > > nVidia Corporation MCP79 High Definition Audio (rev b1)
> > > HDA NVidia at 0x93380000 irq 19
> > > 00:08.0 0403: 10de:0ac0 (rev b1)  Subsystem: 10de:cb79
> > > Codec: Realtek ALC889A
> > > 
> > > Booting with snd_hda_intel.model=mbp3 get sound on headphones, but not on mainspeakers. The mic never worked.
> > > 
> > 
> > Hello again, I found out that puting the pin in 0x18 as a PIN_OUT I get
> > sound in the internal speaker. Currently I can change patch_realtek.c to
> > load the driver using an "mba21" model and I get sound on the main
> > speaker. One of the (many) problems I have is that I need to use
> > something like
> > 
> > {0x18, AC_VERB_SET_PIN_WIDGET_CONTROL, (PIN_OUT | AC_PINCTL_VREF_50) } 
> > 
> > otherwise it goes into HiZ and I get no audio. Looking at that
> > patch_realtek.c I don't see anything similar. Anyway, I don't have a
> > clue about ALSA, I just started reading the HDA specification and looked
> > over patch_realtek.c and came up with the small change below to have a
> > working main speaker. I'd appreciate if you had any suggestion for the
> > mic or to point me towards the right documentation.
> 
> The change looks almost good -- except for one place.
> 
> >   
> > + /* Macbook Air don't know how this works */
> > + static void alc885_mba21_setup (struct hda_codec *codec)
> > + {
> > + 	struct alc_spec *spec = codec->spec;
> > + 
> > + 	spec->autocfg.speaker_pins[0] = 0x18;
> 
> Does this device have no dedicated headphone output pin?
> Usually it's either 0x14 or 0x15.

The headphones are in 0x14 but I couldn't get them to shut the main
speakers off yet when the hp jack is connected. As soon as I understand
how the other examples in patch_realtek.c work and get this working I'll
send you a working patch.

R.
> 
> Also, please make a patch in a unified diff format.
> 
> If the patch is ready for merge, please post it (and add me to Cc)
> with a proper changelog and your sign-off.
> 
> 
> thanks,
> 
> Takashi

  reply	other threads:[~2010-02-22  8:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-06 18:27 Macbook Air 2,1 - no mic nor main speakers Reimundo Heluani
2010-02-22  6:30 ` Reimundo Heluani
2010-02-22  7:55   ` Takashi Iwai
2010-02-22  8:02     ` Reimundo Heluani [this message]
2010-02-22  8:05       ` Takashi Iwai
2010-02-22 17:58         ` Reimundo Heluani
2010-02-23  2:12     ` Reimundo Heluani
2010-02-23  7:18       ` 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=1266825733.3074.19.camel@vino \
    --to=rheluani@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    /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).