From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/3] x86: Add dma-mapping.h to architectural code
Date: Wed, 5 Jul 2017 23:56:26 +0300 [thread overview]
Message-ID: <20170705205628.52620-2-andriy.shevchenko@linux.intel.com> (raw)
In-Reply-To: <20170705205628.52620-1-andriy.shevchenko@linux.intel.com>
Some cross-platform drivers rely on this header present.
Make it so for x86.
It's just a copy'n'paste of arch/arm/include/asm/dma-mapping.h.
Suggested-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
arch/x86/include/asm/dma-mapping.h | 41 ++++++++++++++++++++++++++++++++++++++
1 file changed, 41 insertions(+)
create mode 100644 arch/x86/include/asm/dma-mapping.h
diff --git a/arch/x86/include/asm/dma-mapping.h b/arch/x86/include/asm/dma-mapping.h
new file mode 100644
index 0000000000..7de4c08e36
--- /dev/null
+++ b/arch/x86/include/asm/dma-mapping.h
@@ -0,0 +1,41 @@
+/*
+ * (C) Copyright 2007
+ * Stelian Pop <stelian@popies.net>
+ * Lead Tech Design <www.leadtechdesign.com>
+ *
+ * SPDX-License-Identifier: GPL-2.0+
+ */
+#ifndef __ASM_X86_DMA_MAPPING_H
+#define __ASM_X86_DMA_MAPPING_H
+
+#define dma_mapping_error(x, y) 0
+
+enum dma_data_direction {
+ DMA_BIDIRECTIONAL = 0,
+ DMA_TO_DEVICE = 1,
+ DMA_FROM_DEVICE = 2,
+};
+
+static inline void *dma_alloc_coherent(size_t len, unsigned long *handle)
+{
+ *handle = (unsigned long)memalign(ARCH_DMA_MINALIGN, len);
+ return (void *)*handle;
+}
+
+static inline void dma_free_coherent(void *addr)
+{
+ free(addr);
+}
+
+static inline unsigned long dma_map_single(volatile void *vaddr, size_t len,
+ enum dma_data_direction dir)
+{
+ return (unsigned long)vaddr;
+}
+
+static inline void dma_unmap_single(volatile void *vaddr, size_t len,
+ unsigned long paddr)
+{
+}
+
+#endif /* __ASM_X86_DMA_MAPPING_H */
--
2.11.0
next prev parent reply other threads:[~2017-07-05 20:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 20:56 [U-Boot] [PATCH v2 0/3] x86: Introduce Intel Tangier SoC and Edison board Andy Shevchenko
2017-07-05 20:56 ` Andy Shevchenko [this message]
2017-07-06 4:07 ` [U-Boot] [PATCH v2 1/3] x86: Add dma-mapping.h to architectural code Bin Meng
2017-07-07 3:59 ` Simon Glass
2017-07-22 5:16 ` Bin Meng
2017-07-05 20:56 ` [U-Boot] [PATCH v2 2/3] x86: Add Intel Tangier support Andy Shevchenko
2017-07-06 4:07 ` Bin Meng
2017-07-05 20:56 ` [U-Boot] [PATCH v2 3/3] x86: Add Intel Edison board files Andy Shevchenko
2017-07-06 4:07 ` Bin Meng
2017-07-06 9:44 ` Andy Shevchenko
2017-07-06 11:28 ` Andy Shevchenko
2017-07-06 11:33 ` Felipe Balbi
2017-07-06 12:08 ` Bin Meng
2017-07-06 12:07 ` Bin Meng
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=20170705205628.52620-2-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=u-boot@lists.denx.de \
/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