From: Chenghai Huang <huangchenghai2@huawei.com>
To: <arnd@arndb.de>, <catalin.marinas@arm.com>, <will@kernel.org>,
<akpm@linux-foundation.org>, <anshuman.khandual@arm.com>,
<ryan.roberts@arm.com>, <andriy.shevchenko@linux.intel.com>,
<herbert@gondor.apana.org.au>, <linux-kernel@vger.kernel.org>,
<linux-arch@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-crypto@vger.kernel.org>, <linux-api@vger.kernel.org>
Cc: <fanghao11@huawei.com>, <shenyang39@huawei.com>,
<liulongfang@huawei.com>, <qianweili@huawei.com>
Subject: [PATCH RFC 0/4] Introduce 128-bit IO access
Date: Wed, 12 Nov 2025 09:58:42 +0800 [thread overview]
Message-ID: <20251112015846.1842207-1-huangchenghai2@huawei.com> (raw)
These patches introduce 128-bit IO access functionality. The reason
is that the current HiSilicon cryptographic devices need to
maintain atomic operations when accessing 128-bit MMIO across
physical and virtual functions.
Currently, 128-bit atomic writes have already been implemented in
the device driver, and the driver also depends on a 128-bit atomic
read access interface. Therefore, we have introduced a generic
128-bit IO access interface to replace the implementation of
128-bit read and write IO interfaces using instructions in the
device driver. When the architecture does not support 128-bit
atomic operations, non-atomic 128-bit read and write interfaces can
be used to make the driver functional.
Weili Qian (4):
UAPI: Introduce 128-bit types and byteswap operations
asm-generic/io.h: add io{read,write}128 accessors
io-128-nonatomic: introduce io{read|write}128_{lo_hi|hi_lo}
arm64/io: Add {__raw_read|__raw_write}128 support
arch/arm64/include/asm/io.h | 21 +++++++++
include/asm-generic/io.h | 48 ++++++++++++++++++++
include/linux/io-128-nonatomic-hi-lo.h | 35 ++++++++++++++
include/linux/io-128-nonatomic-lo-hi.h | 34 ++++++++++++++
include/uapi/linux/byteorder/big_endian.h | 6 +++
include/uapi/linux/byteorder/little_endian.h | 6 +++
include/uapi/linux/swab.h | 10 ++++
include/uapi/linux/types.h | 3 ++
8 files changed, 163 insertions(+)
create mode 100644 include/linux/io-128-nonatomic-hi-lo.h
create mode 100644 include/linux/io-128-nonatomic-lo-hi.h
--
2.33.0
next reply other threads:[~2025-11-12 1:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 1:58 Chenghai Huang [this message]
2025-11-12 1:58 ` [PATCH RFC 1/4] UAPI: Introduce 128-bit types and byteswap operations Chenghai Huang
2025-11-12 1:58 ` [PATCH RFC 2/4] asm-generic/io.h: add io{read,write}128 accessors Chenghai Huang
2025-11-12 1:58 ` [PATCH RFC 3/4] io-128-nonatomic: introduce io{read|write}128_{lo_hi|hi_lo} Chenghai Huang
2025-11-12 14:48 ` Ben Dooks
2025-11-13 11:10 ` huangchenghai
2025-11-12 1:58 ` [PATCH RFC 4/4] arm64/io: Add {__raw_read|__raw_write}128 support Chenghai Huang
2025-11-12 12:28 ` Mark Rutland
2025-11-12 14:01 ` David Laight
2025-11-12 14:17 ` Mark Rutland
2025-11-13 14:19 ` huangchenghai
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=20251112015846.1842207-1-huangchenghai2@huawei.com \
--to=huangchenghai2@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anshuman.khandual@arm.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=fanghao11@huawei.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liulongfang@huawei.com \
--cc=qianweili@huawei.com \
--cc=ryan.roberts@arm.com \
--cc=shenyang39@huawei.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).