pcm: hw: do not reset tstamp_type in SND_PCM_APPEND mode by kgroeneveld · Pull Request #450 · alsa-project/alsa-lib · GitHub
Skip to content

pcm: hw: do not reset tstamp_type in SND_PCM_APPEND mode#450

Closed
kgroeneveld wants to merge 1 commit into
alsa-project:masterfrom
kgroeneveld:fix/dshare-tstamp-type
Closed

pcm: hw: do not reset tstamp_type in SND_PCM_APPEND mode#450
kgroeneveld wants to merge 1 commit into
alsa-project:masterfrom
kgroeneveld:fix/dshare-tstamp-type

Conversation

@kgroeneveld

Copy link
Copy Markdown

When the first client of plugins such as dshare open the hw device they set a default tstamp_type in snd_pcm_direct_initialize_slave based on tstamp_type from the config file. But when subsequent clients open the same plugin the snd_pcm_hw_open_fd function clobbers this default.

When the first client of plugins such as dshare open the hw device they set
a default tstamp_type in snd_pcm_direct_initialize_slave based on
tstamp_type from the config file. But when subsequent clients open the same
plugin the snd_pcm_hw_open_fd function clobbers this default.
Comment thread src/pcm/pcm_hw.c
@perexg perexg closed this in 7e01443 Apr 7, 2025
perexg added a commit that referenced this pull request Apr 7, 2025
Fixes: 7e01443 ("pcm: hw: do not reset tstamp_type in SND_PCM_APPEND mode")
Link: #450
Signed-off-by: Jaroslav Kysela <perex@perex.cz>
@perexg

perexg commented Apr 7, 2025

Copy link
Copy Markdown
Member

perexg added a commit that referenced this pull request Apr 8, 2025
This is basically redo of all changed and add appropriate conditions
to disable only ioctl calls, but preserve tstamp_type assignments.

Fixes: 15f2b27 ("pcm: hw: fix default timestamp type for O_APPPEND")
Fixes: 7e01443 ("pcm: hw: do not reset tstamp_type in SND_PCM_APPEND mode")
Link: #450
Suggested-by: Signed-off-by: Kevin Groeneveld <kgroeneveld@lenbrook.com>
Signed-off-by: Jaroslav Kysela <perex@perex.cz>
@kgroeneveld kgroeneveld deleted the fix/dshare-tstamp-type branch April 8, 2025 22:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants