Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1700295
| From | Logan Gunthorpe <logang@deltatee.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v5 3/6] iomap: introduce io{read|write}64_{lo_hi|hi_lo} |
| Date | 2017-07-31 20:10 +0200 |
| Message-ID | <u9niG-167-5@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <u8YX0-2wy-5@gated-at.bofh.it> <u9lgR-85O-1@gated-at.bofh.it> <u9lAd-8rv-1@gated-at.bofh.it> <u9lTA-6F-35@gated-at.bofh.it> <u9n90-NK-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 31/07/17 11:58 AM, Andy Shevchenko wrote: > On Mon, Jul 31, 2017 at 7:31 PM, Logan Gunthorpe <logang@deltatee.com> wrote: >> On 31/07/17 10:10 AM, Andy Shevchenko wrote: >>> Some drivers (hardware) would like to have non-atomic MMIO accesses >>> when readq() defined >> >> Huh? But that's the whole point of the io64-nonatomic header. If a >> driver wants a specific non-atomic access they should just code two 32 >> bit accesses. > You mean to call them directly as lo_hi_XXX() or hi_lo_XXX() ? > Yes it would work. I suppose you could do that too but I really meant just using two io32 calls. That's the most explicit way to indicate you want a non-atomic access. Logan
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH v5 0/6] make io{read|write}64 globally usable Logan Gunthorpe <logang@deltatee.com> - 2017-07-27 01:20 +0200
[PATCH v5 1/6] powerpc: io.h: move iomap.h include so that it can use readq/writeq defs Logan Gunthorpe <logang@deltatee.com> - 2017-07-27 01:20 +0200
[PATCH v5 2/6] powerpc: iomap.c: introduce io{read|write}64_{lo_hi|hi_lo} Logan Gunthorpe <logang@deltatee.com> - 2017-07-27 01:30 +0200
[PATCH v5 5/6] ntb: ntb_hw_intel: use io-64-nonatomic instead of in-driver hacks Logan Gunthorpe <logang@deltatee.com> - 2017-07-27 01:30 +0200
Re: [PATCH v5 5/6] ntb: ntb_hw_intel: use io-64-nonatomic instead of in-driver hacks Jon Mason <jdmason@kudzu.us> - 2017-08-01 19:50 +0200
[PATCH v5 3/6] iomap: introduce io{read|write}64_{lo_hi|hi_lo} Logan Gunthorpe <logang@deltatee.com> - 2017-07-27 01:30 +0200
Re: [PATCH v5 3/6] iomap: introduce io{read|write}64_{lo_hi|hi_lo} Andy Shevchenko <andy.shevchenko@gmail.com> - 2017-07-30 18:10 +0200
Re: [PATCH v5 3/6] iomap: introduce io{read|write}64_{lo_hi|hi_lo} Logan Gunthorpe <logang@deltatee.com> - 2017-07-31 18:00 +0200
Re: [PATCH v5 3/6] iomap: introduce io{read|write}64_{lo_hi|hi_lo} Andy Shevchenko <andy.shevchenko@gmail.com> - 2017-07-31 18:20 +0200
Re: [PATCH v5 3/6] iomap: introduce io{read|write}64_{lo_hi|hi_lo} Logan Gunthorpe <logang@deltatee.com> - 2017-07-31 18:40 +0200
Re: [PATCH v5 3/6] iomap: introduce io{read|write}64_{lo_hi|hi_lo} Andy Shevchenko <andy.shevchenko@gmail.com> - 2017-07-31 20:00 +0200
Re: [PATCH v5 3/6] iomap: introduce io{read|write}64_{lo_hi|hi_lo} Logan Gunthorpe <logang@deltatee.com> - 2017-07-31 20:10 +0200
Re: [PATCH v5 3/6] iomap: introduce io{read|write}64_{lo_hi|hi_lo} Logan Gunthorpe <logang@deltatee.com> - 2017-07-31 20:10 +0200
Re: [PATCH v5 3/6] iomap: introduce io{read|write}64_{lo_hi|hi_lo} Andy Shevchenko <andy.shevchenko@gmail.com> - 2017-07-31 20:20 +0200
Re: [PATCH v5 3/6] iomap: introduce io{read|write}64_{lo_hi|hi_lo} Andy Shevchenko <andy.shevchenko@gmail.com> - 2017-07-31 20:10 +0200
[PATCH v5 4/6] io-64-nonatomic: add io{read|write}64[be]{_lo_hi|_hi_lo} macros Logan Gunthorpe <logang@deltatee.com> - 2017-07-27 01:30 +0200
[PATCH v5 6/6] crypto: caam: cleanup CONFIG_64BIT ifdefs when using io{read|write}64 Logan Gunthorpe <logang@deltatee.com> - 2017-07-27 01:30 +0200
Re: [PATCH v5 0/6] make io{read|write}64 globally usable Horia Geantă <horia.geanta@nxp.com> - 2017-07-31 12:30 +0200
csiph-web