Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jeffery Miller <jmiller@neverware.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ALSA: pcm: Return negative delays from	SNDRV_PCM_IOCTL_DELAY.
Date: Mon, 23 Apr 2018 08:45:55 +0200	[thread overview]
Message-ID: <s5hin8imndo.wl-tiwai@suse.de> (raw)
In-Reply-To: <20180421042046.33408-1-jmiller@neverware.com>

On Sat, 21 Apr 2018 06:20:46 +0200,
Jeffery Miller wrote:
> 
> The commit c2c86a97175f ("ALSA: pcm: Remove set_fs() in PCM core code")
> changed SNDRV_PCM_IOCTL_DELAY to return an inconsistent error instead of a
> negative delay.  Originally the call would succeed and return the negative
> delay.  The Chromium OS Audio Server (CRAS) gets confused and hangs when
> the error is returned instead of the negative delay.
> 
> Help CRAS avoid the issue by rolling back the behavior to return a
> negative delay instead of an error.
> 
> Fixes: c2c86a97175f ("ALSA: pcm: Remove set_fs() in PCM core code")
> Signed-off-by: Jeffery Miller <jmiller@neverware.com>
> ---
> 
> This patch changes the SNDRV_PCM_IOCTL_DELAY ioctl return behavior to
> be similar to what it was in an earlier kernel.
> I encountered this when upgrading from the 4.4 kernel to 4.14. Chrome
> Audio Server (cras) does not handle the error return as gracefully
> as it was handling the successful but negative delays.
> 
> The intent of this patch is to simply revert the behavior of the call
> to match what it was previously.
> 
> It has been applied and tested with the 4.14 kernel. I did confirm this
> is still an issue and is resolved with the patch on the tiwai/sound.git
> master branch.

This is an oversight, indeed.  Applied now.


thanks,

Takashi

      reply	other threads:[~2018-04-23  6:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-21  4:20 [PATCH] ALSA: pcm: Return negative delays from SNDRV_PCM_IOCTL_DELAY Jeffery Miller
2018-04-23  6:45 ` 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=s5hin8imndo.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=jmiller@neverware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox