From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>,
Arun Raghavan <arun@arunraghavan.net>,
Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, pulseaudio-discuss@lists.freedesktop.org
Subject: Re: [alsa-devel] pulseaudio fails to start with kernel 4.11, caused by new snd_hdmi_lpe_audio module)
Date: Wed, 22 Mar 2017 21:16:52 -0600 [thread overview]
Message-ID: <b693d927-229e-e00a-ada5-29d12154547b@linux.intel.com> (raw)
In-Reply-To: <bba100b1-5e74-093a-7625-a7feaba1a065@redhat.com>
On 3/21/17 2:56 AM, Hans de Goede wrote:
> I: [pulseaudio] alsa-sink.c: Using 1.0 fragments of size 352832 bytes
> (2000.18ms), buffer size is 352832 bytes (2000.18ms)
> I: [pulseaudio] alsa-sink.c: Time scheduling watermark is 20.00ms
> I: [pulseaudio] alsa-sink.c: Driver does not support hardware volume
> control, falling back to software volume control.
> I: [pulseaudio] alsa-sink.c: Driver does not support hardware mute
> control, falling back to software mute control.
> I: [alsa-sink-HdmiLpeAudio] core-util.c: Successfully enabled SCHED_RR
> scheduling for thread, with priority 5.
> I: [alsa-sink-HdmiLpeAudio] alsa-sink.c: Starting playback.
> I: [alsa-sink-HdmiLpeAudio] (alsa-lib)pcm_hw.c: SNDRV_PCM_IOCTL_HWSYNC
> failed (-32)
Humm, single period and hw_sync failed, this could be testing the
robustness of the single-period code and its mapping on multiple DMA
descriptors? I haven't looked at the alsa module in eons but can't the
number of periods be forced to two with module parameters while keeping
the timer-based schedulng?
_______________________________________________
pulseaudio-discuss mailing list
pulseaudio-discuss@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
next prev parent reply other threads:[~2017-03-23 3:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 11:42 pulseaudio fails to start with kernel 4.11, caused by new snd_hdmi_lpe_audio module) Hans de Goede
2017-03-20 11:52 ` Takashi Iwai
2017-03-20 23:09 ` Pierre-Louis Bossart
2017-03-21 5:40 ` Takashi Iwai
2017-03-21 7:54 ` Arun Raghavan
2017-03-21 8:56 ` [pulseaudio-discuss] " Hans de Goede
2017-03-21 9:04 ` Arun Raghavan
2017-03-21 14:49 ` [pulseaudio-discuss] " Hans de Goede
2017-03-21 15:05 ` Arun Raghavan
2017-03-23 3:16 ` Pierre-Louis Bossart [this message]
2017-03-23 8:57 ` [pulseaudio-discuss] " Takashi Iwai
2017-03-24 18:18 ` [alsa-devel] " Tanu Kaskinen
2017-03-24 22:01 ` [pulseaudio-discuss] " Hans de Goede
2017-03-28 20:10 ` [alsa-devel] " Tanu Kaskinen
2017-03-29 5:21 ` Takashi Iwai
2017-03-29 12:59 ` Tanu Kaskinen
2017-03-29 13:06 ` Takashi Iwai
2017-03-29 13:14 ` [pulseaudio-discuss] " Tanu Kaskinen
2017-03-29 13:26 ` Takashi Iwai
2017-03-29 14:40 ` [alsa-devel] " Tanu Kaskinen
2017-03-29 14:51 ` Takashi Iwai
2017-03-30 16:06 ` Tanu Kaskinen
2017-03-30 19:26 ` Takashi Iwai
2017-03-29 13:27 ` Tanu Kaskinen
2017-03-29 13:30 ` [pulseaudio-discuss] " 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=b693d927-229e-e00a-ada5-29d12154547b@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=arun@arunraghavan.net \
--cc=hdegoede@redhat.com \
--cc=pulseaudio-discuss@lists.freedesktop.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).