From: "Manolo Díaz" <diaz.manolo@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: HD-audio generic parser merged to linux-next
Date: Wed, 23 Jan 2013 16:09:22 +0100 [thread overview]
Message-ID: <20130123160922.4becfc06@gmail.com> (raw)
In-Reply-To: <s5ha9s0f0bj.wl%tiwai@suse.de>
El mié, 23 ene 2013 a las 15:20 horas
Takashi Iwai escribió:
>At Wed, 23 Jan 2013 15:01:43 +0100,
>Manolo Díaz wrote:
>>
>> El mié, 23 ene 2013 a las 14:54 horas
>> Takashi Iwai escribió:
>>
>> >At Wed, 23 Jan 2013 14:49:32 +0100,
>> >Manolo Díaz wrote:
>> >>
>> >> El mié, 23 ene 2013 a las 9:30 horas
>> >> Takashi Iwai escribió:
>> >>
>> >> >Hi,
>> >> >
>> >> >as most of feedbacks about the new generic parser migration were
>> >> >positive, I decided to take a risk: now all commit that have been in
>> >> >test/hda-migrate branch in sound-unstable git tree are merged to
>> >> >for-next branch of sound git tree for better test coverage.
>> >> >It means that all changes are merged to linux-next, i.e. will be
>> >> >included in 3.9 kernel.
>> >> >
>> >> >For the early adapter people, I'm going to keep test/hda-migrate
>> >> >branch of sound-unstable git tree updated for a while, but the branch
>> >> >will be abandoned some time later.
>> >> >
>> >> >If you encounter any regression by the recent update, please let me
>> >> >know.
>> >> >
>> >> >
>> >> >thanks,
>> >> >
>> >> >Takashi
>> >> >_______________________________________________
>> >> >Alsa-devel mailing list
>> >> >Alsa-devel@alsa-project.org
>> >> >http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>> >>
>> >> Hi,
>> >>
>> >> Recording and (multi stream) playing seem to work fine, but auto-mute
>> >> doesn't. For example, front speakers may remain muted after
>> >> disconnecting the HP.
>> >>
>> >> cat /sys/kernel/debug/tracing/trace
>> >> # tracer: nop
>> >> #
>> >> # entries-in-buffer/entries-written: 0/0 #P:2
>> >> #
>> >> # _-----=> irqs-off
>> >> # / _----=> need-resched
>> >> # | / _---=> hardirq/softirq
>> >> # || / _--=> preempt-depth
>> >> # ||| / delay
>> >> # TASK-PID CPU# |||| TIMESTAMP FUNCTION
>> >> # | | | |||| | |
>> >>
>> >> I've connected and disconnected the HP jack several times before.
>> >
>> >If nothing appears in the tracing (suppose you enabled the events
>> >properly via /sys/kernel/debug/tracing/events/hda/enable), it's rather
>> >a hardware issue.
>>
>> Sorry, I've forgotten this step.
>>
>> >Did the auto-mute work reliably before the code change?
>> >
>> >
>> >Takashi
>>
>> Yes, it did.
>
>Did you mean when it worked? Was it before moving to the generic
>parser, or after it but before upgrading to the latest tree?
>In the latter case, try git bisection to figure out the culprit.
>
>But, it's anyway better to update the git branch. You are testing the
>too old version (there have been already 75 commits after your testing
>one).
>
>
>> New try, this time with hda events enabled.
>>
>> cat /sys/kernel/debug/tracing/trace
>> # tracer: nop
>> #
>> # entries-in-buffer/entries-written: 871/871 #P:2
>> #
>> # _-----=> irqs-off
>> # / _----=> need-resched
>> # | / _---=> hardirq/softirq
>> # || / _--=> preempt-depth
>> # ||| / delay
>> # TASK-PID CPU# |||| TIMESTAMP FUNCTION
>> # | | | |||| | |
>> <idle>-0 [001] d.h. 4509.450172: hda_unsol_event: [0] res=4000000, res_ex=10
>> <idle>-0 [001] d.h. 4513.991711: hda_unsol_event: [0] res=4000000, res_ex=10
>
>OK, so the unsol event is generated properly.
>
>Is the alsa-info.sh output you attached previously at the state after
>unplugging? If so, I see no problem in the code register. The path
>0x04 -> 0x29 -> 0x12 looks fine, all unmuted, power D0 and the pin set
>properly.
>
>If something doesn't work as expected, we need two alsa-info outputs
>for comparison: the working one and non-working one.
>
>
>Takashi
commit 28ebfa08e2945b38e08c537faf7f749125780cbe
branch: test/hda-migrate
Now everything's working fine (only tested 2 channels analog). Btw,
I can't hear what I'm recording, unlike the latest stable kernel. Is
that intentional?
Regards,
--
Manolo Díaz
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2013-01-23 15:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 8:30 HD-audio generic parser merged to linux-next Takashi Iwai
2013-01-23 8:55 ` Raymond Yau
2013-01-23 9:09 ` Takashi Iwai
2013-01-24 3:26 ` Raymond Yau
2013-01-24 6:31 ` Takashi Iwai
2013-01-23 13:49 ` Manolo Díaz
2013-01-23 13:54 ` Takashi Iwai
[not found] ` <20130123150143.6fe19b53@gmail.com>
2013-01-23 14:20 ` Takashi Iwai
2013-01-23 14:55 ` Takashi Iwai
2013-01-23 15:09 ` Takashi Iwai
2013-01-23 15:12 ` Manolo Díaz
2013-01-23 15:09 ` Manolo Díaz [this message]
2013-01-23 15:12 ` Takashi Iwai
2013-01-23 15:30 ` Manolo Díaz
2013-01-23 15:40 ` Manolo Díaz
2013-01-23 16:00 ` Takashi Iwai
2013-01-23 16:35 ` Manolo Díaz
2013-01-23 16:54 ` Takashi Iwai
2013-02-11 14:20 ` Raymond Yau
2013-02-11 14:27 ` Takashi Iwai
2013-02-11 15:12 ` Raymond Yau
2013-02-11 15:17 ` Takashi Iwai
2013-02-13 12:16 ` Raymond Yau
2013-02-13 13:02 ` Takashi Iwai
2013-02-13 13:17 ` Takashi Iwai
2013-02-13 13:48 ` 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=20130123160922.4becfc06@gmail.com \
--to=diaz.manolo@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).