From: Takashi Iwai <tiwai@suse.de>
To: David Henningsson <david.henningsson@canonical.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ALSA: HDA: Use LPIB position fix for Macbook Pro 7, 1
Date: Fri, 13 Jan 2012 10:01:05 +0100 [thread overview]
Message-ID: <s5hlipcht7y.wl%tiwai@suse.de> (raw)
In-Reply-To: <4F0FF19C.10304@canonical.com>
At Fri, 13 Jan 2012 09:55:56 +0100,
David Henningsson wrote:
>
> On 2012-01-13 09:50, Takashi Iwai wrote:
> > At Thu, 12 Jan 2012 16:31:14 +0100,
> > David Henningsson wrote:
> >>
> >> Several users have reported "choppy" audio under the 3.2 kernel,
> >> and that changing position_fix to 1 has resolved their problem.
> >> The chip is an nVidia Corporation MCP89 High Definition Audio,
> >> [10de:0d94] (rev a2).
> >>
> >> Cc: stable@kernel.org (v3.2+)
> >> BugLink: https://bugs.launchpad.net/bugs/909419
> >> Signed-off-by: David Henningsson<david.henningsson@canonical.com>
> >
> > Applied now. Thanks.
>
> Thanks.
>
> Just a thought...this was reported as working better under the previous
> Ubuntu release, which run kernel 3.0 (and not too many changes in
> PulseAudio), i e, a regression. While I haven't done any serious kernel
> bisection of this, I know you've being doing some work with the
> snoop/non-snoop stuff lately, which I haven't followed closely. Do you
> think this can be related to why we're seeing broken position values
> when we're using the DMA position buffer map on some machines?
Honestly I have no idea. The possibility can't be excluded, though,
since Windows seems using the non-cached pages as default.
The position-buffer is used primarily just because this was more
robust on old hardware. OTOH, LPIB seems more robust on modern chips,
so we may think of switching to LPIB, too.
Takashi
prev parent reply other threads:[~2012-01-13 9:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 15:31 [PATCH] ALSA: HDA: Use LPIB position fix for Macbook Pro 7, 1 David Henningsson
2012-01-13 8:50 ` Takashi Iwai
2012-01-13 8:55 ` David Henningsson
2012-01-13 9:01 ` Takashi Iwai [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=s5hlipcht7y.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.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 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.