linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Logan Gunthorpe <logang@deltatee.com>
To: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
	linux-ntb@googlegroups.com, linux-crypto@vger.kernel.org
Cc: "Arnd Bergmann" <arnd@arndb.de>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Horia Geantă" <horia.geanta@nxp.com>,
	"Stephen Bates" <sbates@raithlin.com>,
	"Logan Gunthorpe" <logang@deltatee.com>
Subject: [PATCH v5 0/6] make io{read|write}64 globally usable
Date: Wed, 26 Jul 2017 17:19:11 -0600	[thread overview]
Message-ID: <20170726231917.6073-1-logang@deltatee.com> (raw)

Changes since v4:
- Add functions so the powerpc implementation of iomap.c compiles. (As
noticed by Horia)

Changes since v3:

- I noticed powerpc didn't use the appropriate functions seeing
readq/writeq were not defined when iomap.h was included. Thus I've
included a patch to adjust this
- Fixed some mistakes with a couple of the defines in io-64-nonatomic*
headers
- Fixed a typo noticed by Horia.

(earlier versions were drastically different)


Horia Geantă (1):
  crypto: caam: cleanup CONFIG_64BIT ifdefs when using io{read|write}64

Logan Gunthorpe (5):
  powerpc: io.h: move iomap.h include so that it can use readq/writeq
    defs
  powerpc: iomap.c: introduce io{read|write}64_{lo_hi|hi_lo}
  iomap: introduce io{read|write}64_{lo_hi|hi_lo}
  io-64-nonatomic: add io{read|write}64[be]{_lo_hi|_hi_lo} macros
  ntb: ntb_hw_intel: use io-64-nonatomic instead of in-driver hacks

 arch/powerpc/include/asm/io.h         |   6 +-
 arch/powerpc/kernel/iomap.c           |  40 +++++++++++
 drivers/crypto/caam/regs.h            |  35 ++-------
 drivers/ntb/hw/intel/ntb_hw_intel.c   |  30 +-------
 include/asm-generic/iomap.h           |  26 +++++--
 include/linux/io-64-nonatomic-hi-lo.h |  60 ++++++++++++++++
 include/linux/io-64-nonatomic-lo-hi.h |  60 ++++++++++++++++
 lib/iomap.c                           | 132 ++++++++++++++++++++++++++++++++++
 8 files changed, 322 insertions(+), 67 deletions(-)

--
2.11.0

             reply	other threads:[~2017-07-26 23:19 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-26 23:19 Logan Gunthorpe [this message]
2017-07-26 23:19 ` [PATCH v5 0/6] make io{read|write}64 globally usable Logan Gunthorpe
2017-07-26 23:19 ` [PATCH v5 1/6] powerpc: io.h: move iomap.h include so that it can use readq/writeq defs Logan Gunthorpe
2017-07-26 23:19   ` Logan Gunthorpe
2017-07-26 23:19 ` [PATCH v5 2/6] powerpc: iomap.c: introduce io{read|write}64_{lo_hi|hi_lo} Logan Gunthorpe
2017-07-26 23:19   ` Logan Gunthorpe
2017-07-26 23:19 ` [PATCH v5 3/6] iomap: " Logan Gunthorpe
2017-07-30 16:03   ` Andy Shevchenko
2017-07-30 16:03     ` Andy Shevchenko
2017-07-31 15:55     ` Logan Gunthorpe
2017-07-31 15:55       ` Logan Gunthorpe
2017-07-31 16:10       ` Andy Shevchenko
2017-07-31 16:10         ` Andy Shevchenko
2017-07-31 16:31         ` Logan Gunthorpe
2017-07-31 16:31           ` Logan Gunthorpe
2017-07-31 17:58           ` Andy Shevchenko
2017-07-31 17:58             ` Andy Shevchenko
2017-07-31 18:00             ` Logan Gunthorpe
2017-07-31 18:00               ` Logan Gunthorpe
2017-07-31 18:03               ` Andy Shevchenko
2017-07-31 18:03                 ` Andy Shevchenko
2017-07-31 18:04                 ` Logan Gunthorpe
2017-07-31 18:04                   ` Logan Gunthorpe
2017-07-31 18:11                   ` Andy Shevchenko
2017-07-31 18:11                     ` Andy Shevchenko
2017-07-26 23:19 ` [PATCH v5 4/6] io-64-nonatomic: add io{read|write}64[be]{_lo_hi|_hi_lo} macros Logan Gunthorpe
2017-07-26 23:19 ` [PATCH v5 5/6] ntb: ntb_hw_intel: use io-64-nonatomic instead of in-driver hacks Logan Gunthorpe
2017-08-01 17:47   ` Jon Mason
2017-08-01 17:47     ` Jon Mason
2017-07-26 23:19 ` [PATCH v5 6/6] crypto: caam: cleanup CONFIG_64BIT ifdefs when using io{read|write}64 Logan Gunthorpe
2017-07-26 23:19   ` Logan Gunthorpe
2017-07-31 10:29 ` [PATCH v5 0/6] make io{read|write}64 globally usable Horia Geantă

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=20170726231917.6073-1-logang@deltatee.com \
    --to=logang@deltatee.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=horia.geanta@nxp.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-ntb@googlegroups.com \
    --cc=sbates@raithlin.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).