Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@perex.cz>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] ALSA: uapi: pcm: control the filling of the silence samples for drain
Date: Tue, 02 May 2023 16:05:49 +0200	[thread overview]
Message-ID: <87ttwuomki.wl-tiwai@suse.de> (raw)
In-Reply-To: <20230502115536.986900-1-perex@perex.cz>

On Tue, 02 May 2023 13:55:36 +0200,
Jaroslav Kysela wrote:
> 
> Introduce SNDRV_PCM_INFO_PERFECT_DRAIN and SNDRV_PCM_HW_PARAMS_NO_DRAIN_SILENCE
> flags to fully control the filling of the silence samples in the drain ioctl.
> Actually, the configurable silencing is going to be implemented in the user
> space [1], but drivers (hardware) may not require this operation. Those flags
> do the bidirectional setup for this operation:
> 
> 1) driver may notify the presence of the perfect drain
> 2) user space may not require the filling of the silence samples to inhibit clicks
> 
> If we decide to move this operation to the kernel space in future, the
> SNDRV_PCM_INFO_PERFECT_DRAIN flag may handle this situation without
> double "silence" processing (user + kernel space).
> 
> The ALSA API should be universal, so forcing the behaviour (modifying of
> the ring buffer with any samples) for the drain operation is not ideal.
> 
> [1] https://lore.kernel.org/alsa-devel/20230502115010.986325-1-perex@perex.cz/
> 
> Signed-off-by: Jaroslav Kysela <perex@perex.cz>

Looks good to me.

Will apply once after 6.5 devel branch is opened.


thanks,

Takashi

  reply	other threads:[~2023-05-02 14:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-02 11:55 [PATCH] ALSA: uapi: pcm: control the filling of the silence samples for drain Jaroslav Kysela
2023-05-02 14:05 ` Takashi Iwai [this message]
2023-05-08 13:24 ` 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=87ttwuomki.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.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