From: Ben Dooks <ben.dooks@sifive.com>
To: u-boot@lists.denx.de
Cc: Rick Chen <rick@andestech.com>, Leo <ycliang@andestech.com>,
Ben Dooks <ben.dooks@sifive.com>
Subject: [PATCH 1/3] riscv: add generic link for <asm/atomic.h>
Date: Fri, 5 May 2023 09:02:05 +0100 [thread overview]
Message-ID: <20230505080207.11902-2-ben.dooks@sifive.com> (raw)
In-Reply-To: <20230505080207.11902-1-ben.dooks@sifive.com>
Add a link from <asm/atomic.h> to the generic one to allow
things like ubifs to be built. This can be extended with
riscv AMO ops at a later date.
Signed-off-by: Ben Dooks <ben.dooks@sifive.com>
---
arch/riscv/include/asm/atomic.h | 14 ++++++++++++++
1 file changed, 14 insertions(+)
create mode 100644 arch/riscv/include/asm/atomic.h
diff --git a/arch/riscv/include/asm/atomic.h b/arch/riscv/include/asm/atomic.h
new file mode 100644
index 0000000000..f541fb4daa
--- /dev/null
+++ b/arch/riscv/include/asm/atomic.h
@@ -0,0 +1,14 @@
+/* SPDX-License-Identifier: GPL-2.0+ */
+/*
+ * Copyright 2023 SiFive, Inc.
+ */
+
+#ifndef __RISCV_ATOMIC_H
+#define __RISCV_ATOMIC_H
+
+/* use the generic asm/atomic.h until we define a better one */
+
+#include <asm/system.h>
+#include <asm-generic/atomic.h>
+
+#endif
--
2.39.2
next prev parent reply other threads:[~2023-05-05 8:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 8:02 riscv: asm update for building ubifs Ben Dooks
2023-05-05 8:02 ` Ben Dooks [this message]
2023-06-12 7:31 ` [PATCH 1/3] riscv: add generic link for <asm/atomic.h> Leo Liang
2023-05-05 8:02 ` [PATCH 2/3] riscv: implement local_irq_{save,restore} macros Ben Dooks
2023-06-12 7:47 ` Leo Liang
2023-06-23 9:57 ` Ben Dooks
2023-05-05 8:02 ` [PATCH 3/3] riscv: define test_and_{set,clear}_bit in asm/bitops.h Ben Dooks
2023-06-12 7:48 ` Leo Liang
2023-05-11 11:56 ` riscv: asm update for building ubifs Conor Dooley
2023-05-25 11:01 ` Ben Dooks
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=20230505080207.11902-2-ben.dooks@sifive.com \
--to=ben.dooks@sifive.com \
--cc=rick@andestech.com \
--cc=u-boot@lists.denx.de \
--cc=ycliang@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