make io{read|write}64 globally usable
Subsystems (10)
v7 cover make io{read|write}64 globally usable
This is just a resend seeing I've gotten no feedback in a couple weeks.
Changes since v6:
** none **
Changes since v5:
- Added a fix to the tilcdc driver to ensure it doesn't use the non-atomic operation. (This includes adding io{read|write}64[be]_is_nonatomic defines).
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 (6):
drm/tilcdc: ensure nonatomic iowrite64 is not used
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/gpu/drm/tilcdc/tilcdc_regs.h | 2 +- drivers/ntb/hw/intel/ntb_hw_intel.c | 30 +------- include/asm-generic/iomap.h | 26 +++++-- include/linux/io-64-nonatomic-hi-lo.h | 64 +++++++++++++++++ include/linux/io-64-nonatomic-lo-hi.h | 64 +++++++++++++++++ lib/iomap.c | 132 ++++++++++++++++++++++++++++++++++ 9 files changed, 331 insertions(+), 68 deletions(-)
--
2.11.0
PATCH v7 1/7 drm/tilcdc: ensure nonatomic iowrite64 is not used
Add a check to ensure iowrite64 is only used if it is atomic.
It was decided in [1] that the tilcdc driver should not be using an atomic operation (so it was left out of this patchset). However, it turns out that through the drm code, a nonatomic header is actually included:
include/linux/io-64-nonatomic-lo-hi.h
is included from include/drm/drm_os_linux.h:9:0,
from include/drm/drmP.h:74,
from include/drm/drm_modeset_helper.h:26,
from include/drm/drm_atomic_helper.h:33,
from drivers/gpu/drm/tilcdc/tilcdc_crtc.c:19:And thus, without this change, this patchset would inadvertantly change the behaviour of the tilcdc driver.
[1] lkml.kernel.org/r/CAK8P3a2HhO_zCnsTzq7hmWSz5La5Thu19FWZpun16iMnyyNreQ@mail.gmail.com
--- drivers/gpu/drm/tilcdc/tilcdc_regs.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/tilcdc/tilcdc_regs.h +1 -1
@@ -133,7 +133,7 @@ static inline void tilcdc_write64(struct drm_device *dev, u32 reg, u64 data)struct tilcdc_drm_private *priv = dev->dev_private;volatile void __iomem *addr = priv->mmio + reg; -#ifdef iowrite64 +#if defined(iowrite64) && !defined(iowrite64_is_nonatomic)iowrite64 (data, addr);#else __iowmb ();
Signature · 1 line
2.11.0
PATCH v7 2/7 powerpc: io.h: move iomap.h include so that it can use readq/writeq defs
In reply to Logan GunthorpeSubsequent patches in this series makes use of the readq and writeq defines in iomap.h. However, as is, they get missed on the powerpc platform seeing the include comes before the define. This patch moves the include down to fix this.
--- arch/powerpc/include/asm/io.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
arch/powerpc/include/asm/io.h +2 -2
@@ -33,8 +33,6 @@ extern struct pci_dev *isa_bridge_pcidev;#include <asm/mmu.h> #include <asm/ppc_asm.h> -#include <asm-generic/iomap.h> -#ifdef CONFIG_PPC64 #include <asm/paca.h> #endif
@@ -663,6 +661,8 @@ static inline void name at \#define writel_relaxed (v, addr) writel(v, addr)#define writeq_relaxed (v, addr) writeq(v, addr) +#include <asm-generic/iomap.h> +#ifdef CONFIG_PPC32 #define mmiowb ()#else
Signature · 1 line
2.11.0
PATCH v7 3/7 powerpc: iomap.c: introduce io{read|write}64_{lo_hi|hi_lo}
In reply to Logan GunthorpeThese functions will be introduced into the generic iomap.c so they can deal with PIO accesses in hi-lo/lo-hi variants. Thus, the powerpc version of iomap.c will need to provide the same functions even though, in this arch, they are identical to the regular io{read|write}64 functions.
--- arch/powerpc/kernel/iomap.c | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+)
arch/powerpc/kernel/iomap.c +40 -0
@@ -44,12 +44,32 @@ u64 ioread64(void __iomem *addr) {return readq (addr); } +u64 ioread64_lo_hi (void __iomem *addr) +{ +return readq (addr); +} +u64 ioread64_hi_lo (void __iomem *addr) +{ +return readq (addr); +}u64 ioread64be (void __iomem *addr) {return readq_be (addr); } +u64 ioread64be_lo_hi (void __iomem *addr) +{ +return readq_be (addr); +} +u64 ioread64be_hi_lo (void __iomem *addr) +{ +return readq_be (addr); +}EXPORT_SYMBOL (ioread64); +EXPORT_SYMBOL (ioread64_lo_hi); +EXPORT_SYMBOL (ioread64_hi_lo);EXPORT_SYMBOL (ioread64be); +EXPORT_SYMBOL (ioread64be_lo_hi); +EXPORT_SYMBOL (ioread64be_hi_lo);#endif /* __powerpc64__ */ void iowrite8 (u8 val,void __iomem *addr)
@@ -82,12 +102,32 @@ void iowrite64(u64 val, void __iomem *addr) {writeq (val, addr); } +void iowrite64_lo_hi (u64 val,void __iomem *addr) +{ +writeq (val, addr); +} +void iowrite64_hi_lo (u64 val,void __iomem *addr) +{ +writeq (val, addr); +}void iowrite64be (u64 val,void __iomem *addr) {writeq_be (val, addr); } +void iowrite64be_lo_hi (u64 val,void __iomem *addr) +{ +writeq_be (val, addr); +} +void iowrite64be_hi_lo (u64 val,void __iomem *addr) +{ +writeq_be (val, addr); +}EXPORT_SYMBOL (iowrite64); +EXPORT_SYMBOL (iowrite64_lo_hi); +EXPORT_SYMBOL (iowrite64_hi_lo);EXPORT_SYMBOL (iowrite64be); +EXPORT_SYMBOL (iowrite64be_lo_hi); +EXPORT_SYMBOL (iowrite64be_hi_lo);#endif /* __powerpc64__ */ /*
Signature · 1 line
2.11.0
PATCH v7 4/7 iomap: introduce io{read|write}64_{lo_hi|hi_lo}
In reply to Logan GunthorpeIn order to provide non-atomic functions for io{read|write}64 that will use readq and writeq when appropriate. We define a number of variants of these functions in the generic iomap that will do non-atomic operations on pio but atomic operations on mmio.
These functions are only defined if readq and writeq are defined. If they are not, then the wrappers that always use non-atomic operations from include/linux/io-64-nonatomic*.h will be used.
--- arch/powerpc/include/asm/io.h | 2 + include/asm-generic/iomap.h | 26 +++++++-- lib/iomap.c | 132 ++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 154 insertions(+), 6 deletions(-)
arch/powerpc/include/asm/io.h +2 -0
@@ -788,8 +788,10 @@ extern void __iounmap_at(void *ea, unsigned long size);#define mmio_read16be (addr) readw_be(addr)#define mmio_read32be (addr) readl_be(addr) +#define mmio_read64be (addr) readq_be(addr)#define mmio_write16be (val, addr) writew_be(val, addr)#define mmio_write32be (val, addr) writel_be(val, addr) +#define mmio_write64be (val, addr) writeq_be(val, addr)#define mmio_insb (addr, dst, count) readsb(addr, dst, count)#define mmio_insw (addr, dst, count) readsw(addr, dst, count)#define mmio_insl (addr, dst, count) readsl(addr, dst, count)
include/asm-generic/iomap.h +20 -6
@@ -30,9 +30,16 @@ extern unsigned int ioread16(void __iomem *);extern unsigned int ioread16be (void __iomem *);extern unsigned int ioread32 (void __iomem *);extern unsigned int ioread32be (void __iomem *); -#ifdef CONFIG_64BIT -extern u64 ioread64 (void __iomem *); -extern u64 ioread64be (void __iomem *); + +#ifdef readq +#define ioread64_lo_hi ioread64_lo_hi +#define ioread64_hi_lo ioread64_hi_lo +#define ioread64be_lo_hi ioread64be_lo_hi +#define ioread64be_hi_lo ioread64be_hi_lo +extern u64 ioread64_lo_hi (void __iomem *addr); +extern u64 ioread64_hi_lo (void __iomem *addr); +extern u64 ioread64be_lo_hi (void __iomem *addr); +extern u64 ioread64be_hi_lo (void __iomem *addr);#endif extern void iowrite8 (u8 ,void __iomem *);
@@ -40,9 +47,16 @@ extern void iowrite16(u16, void __iomem *);extern void iowrite16be (u16 ,void __iomem *);extern void iowrite32 (u32 ,void __iomem *);extern void iowrite32be (u32 ,void __iomem *); -#ifdef CONFIG_64BIT -extern void iowrite64 (u64 ,void __iomem *); -extern void iowrite64be (u64 ,void __iomem *); + +#ifdef writeq +#define iowrite64_lo_hi iowrite64_lo_hi +#define iowrite64_hi_lo iowrite64_hi_lo +#define iowrite64be_lo_hi iowrite64be_lo_hi +#define iowrite64be_hi_lo iowrite64be_hi_lo +extern void iowrite64_lo_hi (u64 val,void __iomem *addr); +extern void iowrite64_hi_lo (u64 val,void __iomem *addr); +extern void iowrite64be_lo_hi (u64 val,void __iomem *addr); +extern void iowrite64be_hi_lo (u64 val,void __iomem *addr);#endif /*
lib/iomap.c +132 -0
156 lines not on this page · raw message
Signature · 1 line
2.11.0
PATCH v7 5/7 io-64-nonatomic: add io{read|write}64[be]{_lo_hi|_hi_lo} macros
In reply to Logan GunthorpeThis patch adds generic io{read|write}64[be]{_lo_hi|_hi_lo} macros if they are not already defined by the architecture. (As they are provided by the generic iomap library).
The patch also points io{read|write}64[be] to the variant specified by the header name.
This is because new drivers are encouraged to use ioreadXX, et al instead of readX[1], et al -- and mixing ioreadXX with readq is pretty ugly.
[1] ldd3: section 9.4.2
--- include/linux/io-64-nonatomic-hi-lo.h | 64 +++++++++++++++++++++++++++++++++++ include/linux/io-64-nonatomic-lo-hi.h | 64 +++++++++++++++++++++++++++++++++++ 2 files changed, 128 insertions(+)
include/linux/io-64-nonatomic-hi-lo.h +64 -0
@@ -54,4 +54,68 @@ static inline void hi_lo_writeq_relaxed(__u64 val, volatile void __iomem *addr)#define writeq_relaxed hi_lo_writeq_relaxed#endif +#ifndef ioread64_hi_lo +#define ioread64_hi_lo ioread64_hi_lo +static inline u64 ioread64_hi_lo (void __iomem *addr) +{ +u32 low, high; + + high =ioread32 (addr +sizeof (u32)); + low =ioread32 (addr); + +return low + ((u64 )high <<32 ); +} +#endif + +#ifndef iowrite64_hi_lo +#define iowrite64_hi_lo iowrite64_hi_lo +static inline void iowrite64_hi_lo (u64 val,void __iomem *addr) +{ +iowrite32 (val >>32 , addr +sizeof (u32)); +iowrite32 (val, addr); +} +#endif + +#ifndef ioread64be_hi_lo +#define ioread64be_hi_lo ioread64be_hi_lo +static inline u64 ioread64be_hi_lo (void __iomem *addr) +{ +u32 low, high; + + high =ioread32be (addr); + low =ioread32be (addr +sizeof (u32)); + +return low + ((u64 )high <<32 ); +} +#endif + +#ifndef iowrite64be_hi_lo +#define iowrite64be_hi_lo iowrite64be_hi_lo +static inline void iowrite64be_hi_lo (u64 val,void __iomem *addr) +{ +iowrite32be (val >>32 , addr); +iowrite32be (val, addr +sizeof (u32)); +} +#endif + +#ifndef ioread64 +#define ioread64_is_nonatomic +#define ioread64 ioread64_hi_lo +#endif + +#ifndef iowrite64 +#define iowrite64_is_nonatomic +#define iowrite64 iowrite64_hi_lo +#endif + +#ifndef ioread64be +#define ioread64be_is_nonatomic +#define ioread64be ioread64be_hi_lo +#endif + +#ifndef iowrite64be +#define iowrite64be_is_nonatomic +#define iowrite64be iowrite64be_hi_lo +#endif +#endif /* _LINUX_IO_64_NONATOMIC_HI_LO_H_ */
include/linux/io-64-nonatomic-lo-hi.h +64 -0
68 lines not on this page · raw message
Signature · 1 line
2.11.0
Re: [PATCH v7 5/7] io-64-nonatomic: add io{read|write}64[be]{_lo_hi|_hi_lo} macros
Quoted 11 lines · Logan Gunthorpe
This patch adds generic io{read|write}64[be]{_lo_hi|_hi_lo} macros if they are not already defined by the architecture. (As they are provided by the generic iomap library).
The patch also points io{read|write}64[be] to the variant specified by the header name.
This is because new drivers are encouraged to use ioreadXX, et al instead of readX[1], et al -- and mixing ioreadXX with readq is pretty ugly.
[1] ldd3: section 9.4.2
ldd -> LDD
It's a pretty outdated book, though quite many chapters are actual for these days.
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?
Quoted 4 lines
cc Christoph Hellwig <[email protected]>cc Arnd Bergmann <[email protected]>cc Alan Cox <[email protected]>cc Greg Kroah-Hartman <[email protected]>
cc -> Cc ?
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v7 5/7] io-64-nonatomic: add io{read|write}64[be]{_lo_hi|_hi_lo} macros
Quoted 1 line · Andy Shevchenko
ldd -> LDD
Ok.
Quoted 4 lines
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.
Quoted 1 line
cc -> Cc ?
Fixed.
Logan
Re: [PATCH v7 5/7] io-64-nonatomic: add io{read|write}64[be]{_lo_hi|_hi_lo} macros
Quoted 7 lines · Logan Gunthorpe
Quoted 4 lines · Andy Shevchenko
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.
Yes, the difference is in signaling. The question is if it's still in use. Looks like yes...
Quoted 4 lines
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.
Mixing is ugly, totally agree.
Signature · 2 lines
With Best Regards, Andy Shevchenko
PATCH v7 6/7 ntb: ntb_hw_intel: use io-64-nonatomic instead of in-driver hacks
In reply to Logan GunthorpeNow that ioread64 and iowrite64 are available in io-64-nonatomic, we can remove the hack at the top of ntb_hw_intel.c and replace it with an include.
--- drivers/ntb/hw/intel/ntb_hw_intel.c | 30 +----------------------------- 1 file changed, 1 insertion(+), 29 deletions(-)
drivers/ntb/hw/intel/ntb_hw_intel.c +1 -29
@@ -59,6 +59,7 @@#include <linux/random.h> #include <linux/slab.h> #include <linux/ntb.h> +#include <linux/io-64-nonatomic-lo-hi.h> #include "ntb_hw_intel.h"
@@ -155,35 +156,6 @@ MODULE_PARM_DESC(xeon_b2b_dsd_bar5_addr32,static inline enum ntb_topo xeon_ppd_topo (struct intel_ntb_dev *ndev,u8 ppd);static int xeon_init_isr (struct intel_ntb_dev *ndev); -#ifndef ioread64 -#ifdef readq -#define ioread64 readq -#else -#define ioread64 _ioread64 -static inline u64 _ioread64 (void __iomem *mmio) -{ -u64 low, high; - - low =ioread32 (mmio); - high =ioread32 (mmio +sizeof (u32)); -return low | (high <<32 ); -} -#endif -#endif - -#ifndef iowrite64 -#ifdef writeq -#define iowrite64 writeq -#else -#define iowrite64 _iowrite64 -static inline void _iowrite64 (u64 val,void __iomem *mmio) -{ -iowrite32 (val, mmio); -iowrite32 (val >>32 , mmio +sizeof (u32)); -} -#endif -#endif -static inline int pdev_is_atom (struct pci_dev *pdev) {switch (pdev->device) {
Signature · 1 line
2.11.0
Re: [PATCH v7 6/7] ntb: ntb_hw_intel: use io-64-nonatomic instead of in-driver hacks
drivers/ntb/hw/intel/ntb_hw_intel.c line 62
Quoted 9 lines · Logan Gunthorpe
Now that ioread64 and iowrite64 are available in io-64-nonatomic, we can remove the hack at the top of
ntb_hw_intel.cand replace it with an include.drivers/ntb/hw/intel/ntb_hw_intel.c +1
-0@@ -59,6 +59,7 @@#include <linux/random.h> #include <linux/slab.h> #include <linux/ntb.h> +#include <linux/io-64-nonatomic-lo-hi.h>
I would rather try to squeeze to most alpabetiacelly ordered part of this block. Otherwise it's a pretty nice clean up!
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v7 6/7] ntb: ntb_hw_intel: use io-64-nonatomic instead of in-driver hacks
Quoted 9 lines · Andy Shevchenko
drivers/ntb/hw/intel/ntb_hw_intel.c line 62
Quoted 5 lines
drivers/ntb/hw/intel/ntb_hw_intel.c +1
-0@@ -59,6 +59,7 @@#include <linux/random.h> #include <linux/slab.h> #include <linux/ntb.h> +#include <linux/io-64-nonatomic-lo-hi.h> I would rather try to squeeze to most alpabetiacelly ordered part of this block. Otherwise it's a pretty nice clean up!
I don't understand. The includes were not alphabetically in any order originally and I'd rather not reorder them in my patch.
Logan
Re: [PATCH v7 6/7] ntb: ntb_hw_intel: use io-64-nonatomic instead of in-driver hacks
Quoted 16 lines · Logan Gunthorpe
Quoted 12 lines · Andy Shevchenko
drivers/ntb/hw/intel/ntb_hw_intel.c line 62
Quoted 6 lines
drivers/ntb/hw/intel/ntb_hw_intel.c +1
-0@@ -59,6 +59,7 @@#include <linux/random.h> #include <linux/slab.h> #include <linux/ntb.h> +#include <linux/io-64-nonatomic-lo-hi.h> I would rather try to squeeze to most alpabetiacelly ordered part of this block.
Otherwise it's a pretty nice clean up!
Quoted 2 lines
I don't understand. The includes were not alphabetically in any order originally and I'd rather not reorder them in my patch.
In excerpt I see if you put your include before random.h you will get 3 headers in order.
There may be even better sequence, I didn't check.
Signature · 2 lines
With Best Regards, Andy Shevchenko
PATCH v7 7/7 crypto: caam: cleanup CONFIG_64BIT ifdefs when using io{read|write}64
In reply to Logan GunthorpeFrom: Horia Geantă <[email protected]>
We can now make use of the io-64-nonatomic-lo-hi header to always provide 64 bit IO operations. So this patch cleans up the extra CONFIG_64BIT ifdefs.
To be consistent with CAAM engine HW spec: in case of 64-bit registers, irrespective of device endianness, the lower address should be read from / written to first, followed by the upper address. Indeed the I/O accessors in CAAM driver currently don't follow the spec, however this is a good opportunity to fix the code.
--- drivers/crypto/caam/regs.h | 35 +++++------------------------------ 1 file changed, 5 insertions(+), 30 deletions(-)
drivers/crypto/caam/regs.h +5 -30
@@ -9,7 +9,7 @@#include <linux/types.h> #include <linux/bitops.h> -#include <linux/io.h> +#include <linux/io-64-nonatomic-lo-hi.h> /* * Architecture-specific register access methods
@@ -134,50 +134,25 @@ static inline void clrsetbits_32(void __iomem *reg, u32 clear, u32 set)* base + 0x0000 : least-significant 32 bits * base + 0x0004 : most-significant 32 bits */ -#ifdef CONFIG_64BIT static inline void wr_reg64 (void __iomem *reg,u64 data) { +#ifndef CONFIG_CRYPTO_DEV_FSL_CAAM_IMX if (caam_little_end)iowrite64 (data, reg); else -iowrite64be (data, reg); -} - -static inline u64 rd_reg64 (void __iomem *reg) -{ -if (caam_little_end) -return ioread64 (reg); -else -return ioread64be (reg); -} - -#else /* CONFIG_64BIT */ -static inline void wr_reg64 (void __iomem *reg,u64 data) -{ -#ifndef CONFIG_CRYPTO_DEV_FSL_CAAM_IMX -if (caam_little_end) { -wr_reg32 ((u32 __iomem *)(reg) +1 , data >>32 ); -wr_reg32 ((u32 __iomem *)(reg), data); - } else#endif - { -wr_reg32 ((u32 __iomem *)(reg), data >>32 ); -wr_reg32 ((u32 __iomem *)(reg) +1 , data); - } +iowrite64be (data, reg); }static inline u64 rd_reg64 (void __iomem *reg) {#ifndef CONFIG_CRYPTO_DEV_FSL_CAAM_IMX if (caam_little_end) -return ((u64 )rd_reg32 ((u32 __iomem *)(reg) +1 ) <<32 | - (u64 )rd_reg32 ((u32 __iomem *)(reg))); +return ioread64 (reg); else#endif -return ((u64 )rd_reg32 ((u32 __iomem *)(reg)) <<32 | - (u64 )rd_reg32 ((u32 __iomem *)(reg) +1 )); +return ioread64be (reg); } -#endif /* CONFIG_64BIT */ #ifdef CONFIG_ARCH_DMA_ADDR_T_64BIT #ifdef CONFIG_SOC_IMX7D
Signature · 1 line
2.11.0
Quoted 1 line · Logan Gunthorpe
This is just a resend seeing I've gotten no feedback in a couple weeks.
Overall quite a good clean up! Thanks!
After addressing my comments you may take my
Quoted 48 lines
Changes since v6:
** none **Changes since v5:
- Added a fix to the tilcdc driver to ensure it doesn't use the non-atomic operation. (This includes adding io{read|write}64[be]_is_nonatomic defines).Changes since v4:
- Add functions so the powerpc implementation ofiomap.ccompiles. (As noticed by Horia)Changes since v3:
- I noticed powerpc didn't use the appropriate functions seeing readq/writeq were not defined when
iomap.hwas 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: cleanupCONFIG_64BITifdefs when using io{read|write}64Logan Gunthorpe (6):
drm/tilcdc: ensure nonatomic iowrite64 is not used
powerpc:io.h: moveiomap.hinclude 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 hacksarch/powerpc/include/asm/io.h | 6 +- arch/powerpc/kernel/iomap.c | 40 +++++++++++ drivers/crypto/caam/regs.h | 35 ++------- drivers/gpu/drm/tilcdc/tilcdc_regs.h | 2 +- drivers/ntb/hw/intel/ntb_hw_intel.c | 30 +------- include/asm-generic/iomap.h | 26 +++++-- include/linux/io-64-nonatomic-hi-lo.h | 64 +++++++++++++++++ include/linux/io-64-nonatomic-lo-hi.h | 64 +++++++++++++++++ lib/iomap.c | 132 ++++++++++++++++++++++++++++++++++ 9 files changed, 331 insertions(+), 68 deletions(-)--
2.11.0
Signature · 2 lines
With Best Regards, Andy Shevchenko
Quoted 3 lines · Andy Shevchenko
Overall quite a good clean up! Thanks!
After addressing my comments you may take myReviewed-by Andy Shevchenko <[email protected]>
Great, Thanks!
Logan