mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Jiri Slaby <jirislaby@gmail.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [sound] mpd loops on current -next
Date: Sat, 06 Jun 2009 18:37:11 +0200	[thread overview]
Message-ID: <s5heitx8gjs.wl%tiwai@suse.de> (raw)
In-Reply-To: <alpine.LNX.2.00.0906061752040.4067@eeebox2.perex-int.cz>

At Sat, 6 Jun 2009 17:52:44 +0200 (CEST),
Jaroslav Kysela wrote:
> 
> On Sat, 6 Jun 2009, Jiri Slaby wrote:
> 
> > Hi,
> >
> > I found a regression in current -next caused by
> > c44941e05900fe85f6091456f9e313b446a97ae9
> > (PCM midlevel: Do not update hw_ptr_jiffies when hw_ptr is not changed)
> 
> Oops. It seems like typo. Could you try this patch, please?

Ah, that's the cause of the bug with PA on the recent driver.
I didn't experience the problem because I myself don't use PA :)

Now merged to sound git tree.


thanks,

Takashi

> 
> diff --git a/sound/core/pcm_lib.c b/sound/core/pcm_lib.c
> index dd9126b..bf34603 100644
> --- a/sound/core/pcm_lib.c
> +++ b/sound/core/pcm_lib.c
> @@ -371,7 +371,7 @@ int snd_pcm_update_hw_ptr(struct snd_pcm_substream *substream)
>   	    runtime->silence_size > 0)
>   		snd_pcm_playback_silence(substream, new_hw_ptr);
> 
> -	if (runtime->status->hw_ptr != new_hw_ptr)
> +	if (runtime->status->hw_ptr == new_hw_ptr)
>   		return 0;
> 
>   	runtime->hw_ptr_base = hw_base;
> 
>  					Thanks,
>  						Jaroslav
> 
> -----
> Jaroslav Kysela <perex@perex.cz>
> Linux Kernel Sound Maintainer
> ALSA Project, Red Hat, Inc.
> 

  parent reply	other threads:[~2009-06-06 16:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-06 15:46 Jiri Slaby
2009-06-06 15:52 ` Jaroslav Kysela
2009-06-06 15:58   ` Jiri Slaby
2009-06-06 16:37   ` Takashi Iwai [this message]
2009-06-06 16:56     ` Jiri Slaby
2009-06-07 10:28     ` 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=s5heitx8gjs.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    /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

all inboxes | Powered by JetHome®