From: Gustavo Maciel Dias Vieira <gustavo@sagui.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: No jack sense on Intel 82801I / IDT 92HD71B7X in a HP dv4
Date: Tue, 02 Jun 2009 14:10:11 -0300 [thread overview]
Message-ID: <1243962611.3296.11.camel@hamlet.sagui> (raw)
In-Reply-To: <s5hbpqgq81y.wl%tiwai@suse.de>
Em Qua, 2009-04-29 às 08:37 +0200, Takashi Iwai escreveu:
> > > > When trying to get the output you requested I discovered that
> running
> > > > alsa-info with the headphones plugged made them work and
> silenced the
> > > > speakers. Then, removing the HP do not make the sound come back
> to the
> > > > speakers, but running alsa-info again does. That is, I can force
> the
> > > > jack sense by running alsa-info.
>
> OK, it means that the unsolicited event isn't processed properly
> at jack plugging. But still strange why alsa-info.sh can trigger it.
>
> Could you put some debug print to the unsol even handler to see
> whether you get any even when you plug the jack?
>
The stac92xx_unsol_event() isn't called when the jack is plugged. It is
called twice at kernel boot (HP_EVENT and then INSERT_EVENT), and it is
called three times when running alsa-info (all HP_EVENT, regardless if
the HP is plugged or not).
These results may not be entirely accurate as the current snapshot
isn't working correctly. It just plays the first second of audio and
keeps looping, locking the application (with and without pulseaudio).
If it would help you, I could try to debug stac92xx_unsol_event() in the
current Fedora kernel (2.6.29.4), as the sound works with it and the
jack sensing don't.
Abraços,
Gustavo
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2009-06-02 17:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 14:05 No jack sense on Intel 82801I / IDT 92HD71B7X in a HP dv4 Gustavo Vieira
2009-04-17 14:42 ` Takashi Iwai
2009-04-17 16:18 ` Gustavo Vieira
2009-04-17 16:22 ` Takashi Iwai
2009-04-17 16:31 ` Takashi Iwai
2009-04-17 17:42 ` Gustavo Vieira
2009-04-18 8:57 ` Takashi Iwai
2009-04-19 0:43 ` Gustavo Vieira
[not found] ` <1240101395.3333.9.camel@nick-beta.sagui>
2009-04-20 8:57 ` Takashi Iwai
2009-04-28 19:11 ` Gustavo Vieira
2009-04-29 6:37 ` Takashi Iwai
2009-05-18 20:20 ` Gustavo Maciel Dias Vieira
2009-05-19 5:33 ` Takashi Iwai
2009-06-02 17:10 ` Gustavo Maciel Dias Vieira [this message]
2009-06-05 17:48 ` Gustavo Maciel Dias Vieira
2009-06-05 19:40 ` Takashi Iwai
2009-06-05 20:13 ` Gustavo Maciel Dias Vieira
2009-06-06 9:04 ` Takashi Iwai
2009-06-11 17:57 ` Gustavo Vieira
2009-06-11 19:27 ` Takashi Iwai
2009-06-12 18:01 ` Gustavo Maciel Dias Vieira
2009-06-13 8:09 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2009-06-13 10:32 Jean-Pierre André
2009-06-14 8:05 ` Takashi Iwai
[not found] ` <d3328e7b0906130656w67e2046dqce261e9b83b4ea6b@mail.gmail.com>
[not found] ` <4A365A30.8070608@wanadoo.fr>
2009-06-15 14:31 ` Wael Nasreddine (a.k.a eMxyzptlk)
2009-06-15 19:35 ` Jean-Pierre André
2009-06-15 23:08 ` Wael Nasreddine (a.k.a eMxyzptlk)
2009-06-17 6:57 ` Jean-Pierre André
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=1243962611.3296.11.camel@hamlet.sagui \
--to=gustavo@sagui.org \
--cc=alsa-devel@alsa-project.org \
--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