All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raymond Yau <superquad.vortex2@gmail.com>
To: Takashi Iwai <tiwai@suse.de>,
	ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] ALSA - HDA - Add period time constraint to hda-intel
Date: Thu, 23 Jun 2011 09:14:57 +0800	[thread overview]
Message-ID: <BANLkTin_oEtObPi5n1JFJrs_V25eu7_1OQ@mail.gmail.com> (raw)
In-Reply-To: <s5hboyq2dib.wl%tiwai@suse.de>

2011/5/26 Takashi Iwai <tiwai@suse.de>:
> At Thu, 26 May 2011 10:01:14 +0800,
>
> Yeah, this was overlooked.  The patch below fixes both issues.
> Also it checks no_period_wakeup flag just to be sure (although setting
> this for normal read/write/drain operations doesn't make sense).
>
>

Since aplay does not support no period wakeup mode

I can only confirm that your patch fix the read/write and drain when
aplay using maximum period size/time of HDA codec (e.g. 11 seconds
period time for 44100Hz when prealloc is 4096)

Not sure whether  pulseaudio server still use maximum buffer size or not

but in pulsecore/sink.c and pulsecore/source.c

#define ABSOLUTE_MIN_LATENCY (500)
#define ABSOLUTE_MAX_LATENCY (10*PA_USEC_PER_SEC)
#define DEFAULT_FIXED_LATENCY (250*PA_USEC_PER_MSEC)

CPU usage jump from 2% to 12% when using

aplay -Dpulse --period-time=500 --buffer-time=1500 /usr/share/sounds/alsa/*.wav

although the sound is still good but PA server generate a huge amount
of messages

      reply	other threads:[~2011-06-23  1:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24  4:15 [PATCH] ALSA - HDA - Add period time constraint to hda-intel Raymond Yau
2011-05-24  6:09 ` Takashi Iwai
2011-05-26  2:01   ` Raymond Yau
2011-05-26  6:15     ` Takashi Iwai
2011-06-23  1:14       ` Raymond Yau [this message]

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=BANLkTin_oEtObPi5n1JFJrs_V25eu7_1OQ@mail.gmail.com \
    --to=superquad.vortex2@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.