From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Peter Mamonov <pmamonov@gmail.com>,
Yann Sionneau <ysionneau@kalrayinc.com>,
Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 3/4] mips: set DMA_ALIGNMENT instead of defining dma_alloc
Date: Mon, 8 Jan 2024 11:24:37 +0100 [thread overview]
Message-ID: <20240108102438.1318473-3-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20240108102438.1318473-1-a.fatoum@pengutronix.de>
<dma.h> will take care to define dma_alloc with DMA_ALIGNMENT as
alignment. As 32 is the default and may not be applicable to the used
processor, we define DMA_ALIGNMENT and drop the now duplicate code.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
arch/mips/include/asm/dma.h | 9 ++-------
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/arch/mips/include/asm/dma.h b/arch/mips/include/asm/dma.h
index d7570cce7109..5c5b6d5b3a58 100644
--- a/arch/mips/include/asm/dma.h
+++ b/arch/mips/include/asm/dma.h
@@ -14,13 +14,8 @@
#include <asm/io.h>
#include <asm/types.h>
-#define dma_alloc dma_alloc
-static inline void *dma_alloc(size_t size)
-{
- unsigned long max_linesz = max(current_cpu_data.dcache.linesz,
- current_cpu_data.scache.linesz);
- return xmemalign(max_linesz, ALIGN(size, max_linesz));
-}
+#define DMA_ALIGNMENT \
+ max(current_cpu_data.dcache.linesz, current_cpu_data.scache.linesz)
#define dma_alloc_coherent dma_alloc_coherent
static inline void *dma_alloc_coherent(size_t size, dma_addr_t *dma_handle)
--
2.39.2
next prev parent reply other threads:[~2024-01-08 10:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 10:24 [PATCH 1/4] sandbox: " Ahmad Fatoum
2024-01-08 10:24 ` [PATCH 2/4] kvx: " Ahmad Fatoum
2024-01-08 12:07 ` Yann Sionneau
2024-01-08 10:24 ` Ahmad Fatoum [this message]
2024-01-08 10:24 ` [PATCH 4/4] dma: don't allow override of dma_alloc/dma_free Ahmad Fatoum
2024-01-10 6:45 ` [PATCH 1/4] sandbox: set DMA_ALIGNMENT instead of defining dma_alloc Sascha Hauer
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=20240108102438.1318473-3-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=pmamonov@gmail.com \
--cc=ysionneau@kalrayinc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox