From: Logan Gunthorpe <logang@deltatee.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux-Arch <linux-arch@vger.kernel.org>,
linux-ntb@googlegroups.com,
linux-crypto <linux-crypto@vger.kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Horia Geantă" <horia.geanta@nxp.com>,
"Stephen Bates" <sbates@raithlin.com>,
"Christoph Hellwig" <hch@lst.de>,
"Alan Cox" <gnomes@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH v7 5/7] io-64-nonatomic: add io{read|write}64[be]{_lo_hi|_hi_lo} macros
Date: Tue, 22 Aug 2017 11:55:43 -0600 [thread overview]
Message-ID: <ac32fc61-8a54-faf9-55ad-cd2da5fd6503@deltatee.com> (raw)
In-Reply-To: <CAHp75Ve3gG6KdjVBmJZAw25uXRmzfCMUv1kFvg0TbhN7ebTqdw@mail.gmail.com>
On 22/08/17 11:40 AM, Andy Shevchenko wrote:
> ldd -> LDD
Ok.
> Recomendation is kinda arguable. I doubt modern architectures make
> difference between IO operations and MMIO.
> Does, for example, PCI requires some special signal (message / wire)
> handling when pio_*() accessors used vs. mmio_*() ones?
Sort of. There is a difference between the two in x86. But really if
it's not a valid recommendation someone should just go through and
deprecate one of them or document better when one should be used over
the other. In any case it's still really ugly to mix the two types in
the same driver.
> cc -> Cc ?
Fixed.
Logan
next prev parent reply other threads:[~2017-08-22 17:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 17:02 [PATCH v7 0/7] make io{read|write}64 globally usable Logan Gunthorpe
2017-08-22 17:02 ` [PATCH v7 1/7] drm/tilcdc: ensure nonatomic iowrite64 is not used Logan Gunthorpe
2017-08-22 17:02 ` [PATCH v7 2/7] powerpc: io.h: move iomap.h include so that it can use readq/writeq defs Logan Gunthorpe
2017-08-22 17:02 ` [PATCH v7 3/7] powerpc: iomap.c: introduce io{read|write}64_{lo_hi|hi_lo} Logan Gunthorpe
2017-08-22 17:02 ` [PATCH v7 4/7] iomap: " Logan Gunthorpe
2017-08-22 17:02 ` [PATCH v7 5/7] io-64-nonatomic: add io{read|write}64[be]{_lo_hi|_hi_lo} macros Logan Gunthorpe
2017-08-22 17:40 ` Andy Shevchenko
2017-08-22 17:55 ` Logan Gunthorpe [this message]
2017-08-22 21:07 ` Andy Shevchenko
2017-08-22 17:02 ` [PATCH v7 6/7] ntb: ntb_hw_intel: use io-64-nonatomic instead of in-driver hacks Logan Gunthorpe
2017-08-22 17:41 ` Andy Shevchenko
2017-08-22 17:56 ` Logan Gunthorpe
2017-08-22 20:14 ` Andy Shevchenko
2017-08-22 17:02 ` [PATCH v7 7/7] crypto: caam: cleanup CONFIG_64BIT ifdefs when using io{read|write}64 Logan Gunthorpe
2017-08-22 17:43 ` [PATCH v7 0/7] make io{read|write}64 globally usable Andy Shevchenko
2017-08-22 17:58 ` Logan Gunthorpe
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=ac32fc61-8a54-faf9-55ad-cd2da5fd6503@deltatee.com \
--to=logang@deltatee.com \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--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