alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: David Henningsson <david.henningsson@canonical.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: [PATCH] hda_intel: Add Oaktrail identifiers
Date: Mon, 02 Jan 2012 21:17:18 +0100	[thread overview]
Message-ID: <4F0210CE.1020007@canonical.com> (raw)
In-Reply-To: <20111231170001.22cdabdd@pyramind.ukuu.org.uk>

On 12/31/2011 06:00 PM, Alan Cox wrote:
>> Thanks, applied.
>>
>> Meanwhile, could you double-check whether AZX_DCAPS_POSFIX_LPIB isn't
>> needed?  We have enabled this bit for Poulsbo recently for working
>> around problems regarding the playback positions.

That was my thought as well, but Takashi was quicker, as usual :-)

> Is there a good way to test this and I'll run the test and see.

I wouldn't say we have a really good way to test it; but PulseAudio is 
relying heavily on this to be correct. So in short - test both playback 
and recording through PulseAudio, and also test making volume changes 
while playing back (or recording). If one position fix method is broken, 
it usually manifests itself by glitches, audio breaking up, or maybe 
stops completely. (There is actually a test tool called alsa-time-test 
written by Lennart Poettering, but AFAIK it only tests playback, and I 
don't exactly know how to use it.)

A quick way to test different position fix methods is to add this module 
parameter:

# This will read from LPIB
options snd-hda-intel position_fix=1

# This will read from DMA Position buffer (the default as specified in 
your patch)
options snd-hda-intel position_fix=2

Btw, you seem to be employed by Intel these days? [1] Any chance you can 
talk to your firmware developers of this chip? I assume somebody at 
Intel should know what method to prefer. That would be the safest/best 
option IMHO.

-- 
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic

[1] https://secure.wikimedia.org/wikipedia/en/wiki/Alan_Cox

  parent reply	other threads:[~2012-01-02 20:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-28 15:17 [PATCH] hda_intel: Add Oaktrail identifiers Alan Cox
2011-12-31 16:52 ` Takashi Iwai
2011-12-31 17:00   ` Alan Cox
2011-12-31 17:04     ` Takashi Iwai
2012-01-02 20:17     ` David Henningsson [this message]
2012-01-03 23:06       ` Alan Cox
2012-01-04  9:22         ` David Henningsson
2012-01-08  9:02           ` Takashi Iwai
2012-01-04 11:55         ` David Henningsson

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=4F0210CE.1020007@canonical.com \
    --to=david.henningsson@canonical.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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).