Re: [PATCH v7 5/7] io-64-nonatomic: add io{read|write}64[be]{_lo_hi|_hi_lo} macros

2017-08-22 Thread Andy Shevchenko
On Tue, Aug 22, 2017 at 8:55 PM, Logan Gunthorpe wrote: > On 22/08/17 11:40 AM, Andy Shevchenko wrote: >> 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) >> hand

Re: [PATCH v7 5/7] io-64-nonatomic: add io{read|write}64[be]{_lo_hi|_hi_lo} macros

2017-08-22 Thread Logan Gunthorpe
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_*() on

Re: [PATCH v7 5/7] io-64-nonatomic: add io{read|write}64[be]{_lo_hi|_hi_lo} macros

2017-08-22 Thread Andy Shevchenko
On Tue, Aug 22, 2017 at 8:02 PM, Logan Gunthorpe wrote: > 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 s

[PATCH v7 5/7] io-64-nonatomic: add io{read|write}64[be]{_lo_hi|_hi_lo} macros

2017-08-22 Thread 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 enco