diff options
author | Takashi Iwai <tiwai@suse.de> | 2021-08-09 09:18:27 +0200 |
---|---|---|
committer | Takashi Iwai <tiwai@suse.de> | 2021-08-09 10:04:03 +0200 |
commit | cbea6e5a7772b7a5b80baa8f98fd77853487fd2a (patch) | |
tree | 4daea31e89ebe33e32afa4d160d12bef23b55c14 /scripts/cc-version.sh | |
parent | 2c86446f8e0428cd5c9bb37f9c6727bd4830967d (diff) | |
download | linux-cbea6e5a7772b7a5b80baa8f98fd77853487fd2a.tar.gz linux-cbea6e5a7772b7a5b80baa8f98fd77853487fd2a.tar.bz2 linux-cbea6e5a7772b7a5b80baa8f98fd77853487fd2a.zip |
ALSA: pcm: Check mmap capability of runtime dma buffer at first
Currently we check only the substream->dma_buffer as the preset of the
buffer configuration for verifying the availability of mmap. But a
few drivers rather set up the buffer in the own way without the
standard buffer preallocation using substream->dma_buffer, and they
miss the proper checks. (Now it's working more or less fine as most
of them are running only on x86).
Actually, they may set up the runtime dma_buffer (referred via
snd_pcm_get_dma_buf()) at the open callback, though. That is, this
could have been used as the primary source.
This patch changes the hw_support_mmap() function to check the runtime
dma buffer at first. It's usually NULL with the standard buffer
preallocation, and in that case, we continue checking
substream->dma_buffer as fallback.
Link: https://lore.kernel.org/r/20210809071829.22238-2-tiwai@suse.de
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Diffstat (limited to 'scripts/cc-version.sh')
0 files changed, 0 insertions, 0 deletions