From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@perex.cz>
Cc: <linux-sound@vger.kernel.org>, Takashi Iwai <tiwai@suse.de>
Subject: Re: [PATCH v3 0/2] ALSA: pcm: reinvent the stream synchronization ID API
Date: Tue, 07 May 2024 14:40:10 +0200 [thread overview]
Message-ID: <87jzk5eqxh.wl-tiwai@suse.de> (raw)
In-Reply-To: <20240507083142.557299-1-perex@perex.cz>
On Tue, 07 May 2024 10:26:17 +0200,
Jaroslav Kysela wrote:
>
> Until the commit e11f0f90a626 ("ALSA: pcm: remove SNDRV_PCM_IOCTL1_INFO
> internal command"), there was a possibility to pass information
> about the synchronized streams to the user space. The mentioned
> commit removed blindly the appropriate code with an irrelevant comment.
>
> The revert may be appropriate, but since this API was lost for several
> years without any complains, it's time to improve it. The hardware
> parameters may change the used stream clock source (e.g. USB hardware)
> so move this synchronization ID to hw_params as read-only field.
>
> It seems that pipewire can benefit from this API (disable adaptive
> resampling for perfectly synchronized PCM streams) now.
I find the idea is fine. But as Sakamoto-san suggested in the
previous thread, it's no urgent issue, and I'm inclined to postpone
the merge after 6.10 merge window. So let's brew the stuff well for
now.
thanks,
Takashi
prev parent reply other threads:[~2024-05-07 12:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 8:26 [PATCH v3 0/2] ALSA: pcm: reinvent the stream synchronization ID API Jaroslav Kysela
2024-05-07 8:26 ` [PATCH v3 1/2] " Jaroslav Kysela
2024-05-07 12:33 ` Takashi Iwai
2024-05-07 8:26 ` [PATCH v3 2/2] ALSA: pcm: optimize and clarify stream sychronization " Jaroslav Kysela
2024-05-07 12:38 ` Takashi Iwai
2024-05-07 12:40 ` 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=87jzk5eqxh.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-sound@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