From: Takashi Iwai <tiwai@suse.de>
To: linux-sound@vger.kernel.org
Subject: [PATCH 0/2] ALSA: memalloc: Use proper DMA mapping API
Date: Thu, 12 Sep 2024 17:52:23 +0200 [thread overview]
Message-ID: <20240912155227.4078-1-tiwai@suse.de> (raw)
This is a further cleanup of memalloc core stuff to do behave
more correctly regarding DMA API. Formerly some x86-specific code
relied on the address from the page allocators, but rather we should
map correctly the pages with DMA mapping API. With those fixes, the
fallback allocation should work more properly, so we can drop the
hackish check, too.
Takashi
===
Takashi Iwai (2):
ALSA: memalloc: Use proper DMA mapping API for x86 WC buffer
allocations
ALSA: memalloc: Use proper DMA mapping API for x86 S/G buffer
allocations
sound/core/memalloc.c | 127 ++++++++++++++++++++++--------------------
1 file changed, 67 insertions(+), 60 deletions(-)
--
2.43.0
next reply other threads:[~2024-09-12 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 15:52 Takashi Iwai [this message]
2024-09-12 15:52 ` [PATCH 1/2] ALSA: memalloc: Use proper DMA mapping API for x86 WC buffer allocations Takashi Iwai
2024-09-12 15:52 ` [PATCH 2/2] ALSA: memalloc: Use proper DMA mapping API for x86 S/G " 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=20240912155227.4078-1-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-sound@vger.kernel.org \
/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