From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 0/3] API for 128-bit IO access
Date: Wed, 24 Jan 2018 10:22:13 +0000 [thread overview]
Message-ID: <20180124102212.GC20586@arm.com> (raw)
In-Reply-To: <20180124090519.6680-1-ynorov@caviumnetworks.com>
On Wed, Jan 24, 2018 at 12:05:16PM +0300, Yury Norov wrote:
> This series adds API for 128-bit memory IO access and enables it for ARM64.
> The original motivation for 128-bit API came from new Cavium network device
> driver. The hardware requires 128-bit access to make things work. See
> description in patch 3 for details.
>
> Also, starting from ARMv8.4, stp and ldp instructions become atomic, and
> API for 128-bit access would be helpful in core arm64 code.
Only for normal, cacheable memory, so they're not suitable for IO accesses
as you're proposing here.
Will
next prev parent reply other threads:[~2018-01-24 10:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 9:05 [PATCH RFC 0/3] API for 128-bit IO access Yury Norov
2018-01-24 9:05 ` [PATCH 1/3] UAPI: Introduce 128-bit types and byteswap operations Yury Norov
2018-01-24 9:05 ` [PATCH 2/3] asm-generic/io.h: API for 128-bit memory accessors Yury Norov
2018-01-24 9:05 ` [PATCH 3/3] arm64: enable 128-bit memory read/write support Yury Norov
2018-01-24 13:00 ` Geert Uytterhoeven
2018-01-24 18:19 ` Yury Norov
2018-01-24 10:22 ` Will Deacon [this message]
2018-01-26 9:05 ` [PATCH RFC 0/3] API for 128-bit IO access Yury Norov
2018-01-26 18:11 ` Will Deacon
2018-01-29 10:25 ` Yury Norov
2018-01-24 10:28 ` Arnd Bergmann
2018-01-24 15:48 ` Andy Shevchenko
2018-01-25 11:38 ` Yury Norov
2018-01-25 12:11 ` Robin Murphy
2018-01-25 13:59 ` Arnd Bergmann
2018-01-24 16:38 ` Jeffrey Walton
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=20180124102212.GC20586@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).