From: Takashi Iwai <tiwai@suse.de>
To: Ian Munsie <darkstarsword@gmail.com>
Cc: Raymond Yau <superquad.vortex2@gmail.com>,
ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: No sound from internal speaker on 2013 Macbook Air 6, 1
Date: Mon, 09 Sep 2013 11:03:22 +0200 [thread overview]
Message-ID: <s5h61uabc4l.wl%tiwai@suse.de> (raw)
In-Reply-To: <CAH4=b6Km5E5v18bvKqV661kudaKkpfnHGUWNEeGEY7ngXVARnw@mail.gmail.com>
At Mon, 9 Sep 2013 18:01:41 +1000,
Ian Munsie wrote:
>
> Hi Raymond,
>
> On 26 August 2013 11:55, Raymond Yau <superquad.vortex2@gmail.com> wrote:
> > https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/plain/Documentation/sound/alsa/HD-Audio.txt
> >
> > have you try those gpio ?
>
> Thanks for the pointer - I finally got around to trying this (it's not
> my primary box) and was able to get the speaker to work by enabling
> GPIO 0 as an output with data=1 (i.e. I selected out-dir, enable and
> data in hda-analyzer).
>
> I noticed that the GPIO settings would clear when I stopped playing
> sound though, so I currently have to run the python script generated
> by hda-analyzer every time I want to play a sound through the speaker.
> I also noticed that I had to manually set data=0 to turn the speaker
> off if I plugged in the headphones.
>
> What is the next step in fixing this properly? I've been meaning to
> look through the hda code to figure out how these kind of quirks are
> supposed to be handled, but haven't got around to that yet.
Please give alsa-info.sh output, then we'll provide some trivial test
patches. At best, run alsa-info.sh with --no-upload option and attach
the output.
> > or specify hints primary_hp = false
>
> That did nothing by itself, though come to think of it I didn't try it
> in combination with the GPIO settings.
>
>
> > it is strange that driver select amp at pin complex of headphone as
> > headphone volume control instead of amp at audio output ( the number of step
> > and dB range of headphone and speaker is different )
> >
> > you may need to change the logic of look_for_out_vol_nid() in hda_generic.c
>
> Hmm, the volume control seemed to be working for me with both speakers
> & headphones, but I didn't check which control it was actually
> changing.
>
>
> > you may need cs4208 datasheet if the codec need vendor coefff
> >
> > why virtual master did not warn when the dB range and number of step in
> > slaves controls are different ?
>
> Is that something I need to be concerned about? Where should that
> warning have appeared?
If GPIO does fix the issue, that's all what we need.
Takashi
next prev parent reply other threads:[~2013-09-09 9:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-24 13:25 No sound from internal speaker on 2013 Macbook Air 6, 1 Ian Munsie
2013-08-26 1:55 ` Raymond Yau
2013-09-09 8:01 ` Ian Munsie
2013-09-09 9:03 ` Takashi Iwai [this message]
2013-09-09 9:44 ` Ian Munsie
2013-09-09 9:48 ` Takashi Iwai
2013-09-09 13:26 ` Ian Munsie
2013-09-09 14:08 ` Takashi Iwai
2013-09-09 14:48 ` Ian Munsie
2013-09-09 14:58 ` Takashi Iwai
2013-09-09 15:48 ` Ian Munsie
2013-09-09 16:05 ` Takashi Iwai
2013-09-09 16:30 ` Ian Munsie
2013-09-13 13:00 ` Takashi Iwai
2013-09-09 16:24 ` Raymond Yau
2013-09-09 16:32 ` Ian Munsie
-- strict thread matches above, loose matches on Subject: below --
2013-09-16 9:44 Ben Whitten
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=s5h61uabc4l.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=darkstarsword@gmail.com \
--cc=superquad.vortex2@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).