All of lore.kernel.org
 help / color / mirror / Atom feed
From: alsa@scripple.org
To: Pavel Hofman <pavel.hofman@ivitera.com>, alsa-devel@alsa-project.org
Subject: Re: Loopback device respond to changing parameters on the other end.
Date: Mon, 5 Oct 2020 08:21:38 -0700	[thread overview]
Message-ID: <3b12f1e6-4689-1cb7-c658-455bea99eccd@schells.com> (raw)
In-Reply-To: <691bd7f1-cf08-014a-6d8d-da7c50fdab91@ivitera.com>

On 10/5/20 12:12 AM, Pavel Hofman wrote:> There used to be a 
notification module parameter (pcm_notify) which
> closed the other loopback side if params changed 
> https://mailman.alsa-project.org/pipermail/alsa-devel/2020-March/165454.html 
> 
> 
> I am afraid it remains to be fixed.
Thanks for the info. That does seem to be what should be the solution. 
It doesn't seem to be being worked though.

I'd still like to know if there's a way to get the new hw_params inside 
the hw_params modify hook.  Certainly that seems like information that 
should be available in the call back.

scripple

      reply	other threads:[~2020-10-05 15:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-05  2:38 Loopback device respond to changing parameters on the other end alsa
2020-10-05  7:12 ` Pavel Hofman
2020-10-05 15:21   ` alsa [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=3b12f1e6-4689-1cb7-c658-455bea99eccd@schells.com \
    --to=alsa@scripple.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=pavel.hofman@ivitera.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.