From: Ben Whitten <ben.whitten@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: No sound from internal speaker on 2013 Macbook Air 6, 1
Date: Mon, 16 Sep 2013 10:44:27 +0100 [thread overview]
Message-ID: <CAF3==iuP_7_gQece7yNVDOGPmwFSKPF-3n4VjknmHPMtrLJygA@mail.gmail.com> (raw)
> > > OK, then the normal jack detection doesn't work with this machine, as
> > > it seems. You can try the above to all pins for checking if any of
> > > other pins reacts to the headphone jack.
> >
> > No luck I'm afraid - none of the other pins seem to react to the
> > headphones. Is there anything else you can think of that I can try
> > tomorrow?
>
> Well, it might be notified via GPIO. Try to read GPIO pins except for
> GPIO0. That is, set the all unmasked, the direction to READ.
We have found that jack sense comes in on the headphone pin in a windows
bootcamp install. However this bit isn't set in linux using either the
default chip, bootloader, or windows pin configs. No other GPIO's are
enabled in windows.
Ben
next reply other threads:[~2013-09-16 9:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 9:44 Ben Whitten [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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
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='CAF3==iuP_7_gQece7yNVDOGPmwFSKPF-3n4VjknmHPMtrLJygA@mail.gmail.com' \
--to=ben.whitten@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).