From: Zong Li <zongbox@gmail.com>
To: palmer@sifive.com, aou@eecs.berkeley.edu
Cc: hch@infradead.org, zong@andestech.com,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Zong Li <zongbox@gmail.com>
Subject: [PATCH v4 2/5] RISC-V: Add preprocessor directive for swiotlb
Date: Wed, 3 Oct 2018 11:09:59 +0800 [thread overview]
Message-ID: <0aaabb05426a360f71cbc7a910e2c613d3a3891c.1538535528.git.zongbox@gmail.com> (raw)
In-Reply-To: <cover.1538535527.git.zongbox@gmail.com>
On RV32, it doesn't select the SWIOTLB, only RV64 support swiotlb now.
Signed-off-by: Zong Li <zong@andestech.com>
---
arch/riscv/kernel/setup.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/riscv/kernel/setup.c b/arch/riscv/kernel/setup.c
index aee6031..6de6584 100644
--- a/arch/riscv/kernel/setup.c
+++ b/arch/riscv/kernel/setup.c
@@ -227,7 +227,10 @@ void __init setup_arch(char **cmdline_p)
setup_bootmem();
paging_init();
unflatten_device_tree();
+
+#ifdef CONFIG_SWIOTLB
swiotlb_init(1);
+#endif
#ifdef CONFIG_SMP
setup_smp();
--
2.7.4
next prev parent reply other threads:[~2018-10-03 3:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 3:09 [PATCH v4 0/5] Fix some bugs on RV32 build fail and issue Zong Li
2018-10-03 3:09 ` [PATCH v4 1/5] RISC-V: Build tishift only on 64-bit Zong Li
2018-10-03 3:09 ` Zong Li [this message]
2018-10-03 3:10 ` [PATCH v4 3/5] lib: Add umoddi3 and udivmoddi4 of GCC library routines Zong Li
2018-10-03 3:10 ` [PATCH v4 4/5] RISC-V: Select GENERIC_LIB_UMODDI3 on RV32 Zong Li
2018-10-03 3:10 ` [PATCH v4 5/5] RISC-V: Avoid corrupting the upper 32-bit of phys_addr_t in ioremap Zong Li
2018-10-15 12:33 ` [PATCH v4 0/5] Fix some bugs on RV32 build fail and issue Zong Li
2018-10-15 23:16 ` Palmer Dabbelt
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=0aaabb05426a360f71cbc7a910e2c613d3a3891c.1538535528.git.zongbox@gmail.com \
--to=zongbox@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=zong@andestech.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;
as well as URLs for NNTP newsgroup(s).