From: Takashi Iwai <tiwai@suse.de>
To: "Raphaël Dingé" <raphael.dinge@ohmforce.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Can't detect "XRUNs"
Date: Wed, 04 Jul 2018 17:56:50 +0200 [thread overview]
Message-ID: <s5hsh4zuh8d.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAL-i0qGsRX3ToRgox3KBExqF3e351r-ZH5auRPpx0xFdfX3FJg@mail.gmail.com>
On Wed, 04 Jul 2018 17:49:34 +0200,
Raphaël Dingé wrote:
>
> >> You applied my patch, right? Otherwise the xrun injection won't
> >> trigger the xrun tracing event by itself, just calling
> >> snd_pcm_stop().
>
> So with your patch, echo 1 > xrun_injection will output one xrun event
> in /sys/kernel/debug/tracing/trace
> So at least this is working!
>
> But no other events are generated.
It means that it's no system-wide XRUN handling.
Which hardware? If it's Intel LPE HDMI thing, -EPIPE report doesn't
mean always an XRUN, but may imply just an unconnected device.
Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2018-07-04 15:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 10:26 Can't detect "XRUNs" Raphaël Dingé
2018-07-04 10:33 ` Takashi Iwai
2018-07-04 10:38 ` Raphaël Dingé
2018-07-04 12:11 ` Raphaël Dingé
2018-07-04 13:16 ` Takashi Iwai
2018-07-04 13:49 ` Raphaël Dingé
2018-07-04 14:02 ` Takashi Iwai
2018-07-04 14:16 ` Raphaël Dingé
2018-07-04 15:11 ` Raphaël Dingé
2018-07-04 15:14 ` Takashi Iwai
2018-07-04 15:16 ` Raphaël Dingé
2018-07-04 15:49 ` Raphaël Dingé
2018-07-04 15:56 ` Takashi Iwai [this message]
2018-07-04 16:06 ` Raphaël Dingé
2018-07-05 9:10 ` Raphaël Dingé
2018-07-05 10:05 ` Takashi Iwai
2018-07-05 10:59 ` Raphaël Dingé
2018-07-05 12:34 ` Raphaël Dingé
2018-07-05 15:02 ` 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=s5hsh4zuh8d.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=raphael.dinge@ohmforce.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