Re: [PATCH RFC 0/3] API for 128-bit IO access

2018-01-29 Thread Yury Norov
On Fri, Jan 26, 2018 at 06:11:49PM +, Will Deacon wrote: > On Fri, Jan 26, 2018 at 12:05:42PM +0300, Yury Norov wrote: > > On Wed, Jan 24, 2018 at 10:22:13AM +, Will Deacon wrote: > > > On Wed, Jan 24, 2018 at 12:05:16PM +0300, Yury Norov wrote: > > > > This series adds API for 128-bit

Re: [PATCH RFC 0/3] API for 128-bit IO access

2018-01-26 Thread Will Deacon
On Fri, Jan 26, 2018 at 12:05:42PM +0300, Yury Norov wrote: > On Wed, Jan 24, 2018 at 10:22:13AM +, Will Deacon wrote: > > On Wed, Jan 24, 2018 at 12:05:16PM +0300, Yury Norov wrote: > > > This series adds API for 128-bit memory IO access and enables it for > > > ARM64. > > > The original

Re: [PATCH RFC 0/3] API for 128-bit IO access

2018-01-26 Thread Yury Norov
On Wed, Jan 24, 2018 at 10:22:13AM +, Will Deacon wrote: > On Wed, Jan 24, 2018 at 12:05:16PM +0300, Yury Norov wrote: > > This series adds API for 128-bit memory IO access and enables it for ARM64. > > The original motivation for 128-bit API came from new Cavium network device > > driver. The

Re: [PATCH RFC 0/3] API for 128-bit IO access

2018-01-25 Thread Arnd Bergmann
On Thu, Jan 25, 2018 at 12:38 PM, Yury Norov wrote: > On Wed, Jan 24, 2018 at 11:28:55AM +0100, Arnd Bergmann wrote: >> On Wed, Jan 24, 2018 at 10:05 AM, Yury Norov >> wrote: > Thanks for doing this test. Looking at this I realize that this

Re: [PATCH RFC 0/3] API for 128-bit IO access

2018-01-25 Thread Robin Murphy
On 25/01/18 11:38, Yury Norov wrote: On Wed, Jan 24, 2018 at 11:28:55AM +0100, Arnd Bergmann wrote: On Wed, Jan 24, 2018 at 10:05 AM, Yury Norov wrote: This series adds API for 128-bit memory IO access and enables it for ARM64. The original motivation for 128-bit

Re: [PATCH RFC 0/3] API for 128-bit IO access

2018-01-25 Thread Yury Norov
On Wed, Jan 24, 2018 at 11:28:55AM +0100, Arnd Bergmann wrote: > On Wed, Jan 24, 2018 at 10:05 AM, Yury Norov > wrote: > > This series adds API for 128-bit memory IO access and enables it for ARM64. > > The original motivation for 128-bit API came from new Cavium

Re: [PATCH RFC 0/3] API for 128-bit IO access

2018-01-24 Thread Jeffrey Walton
On Wed, Jan 24, 2018 at 4:05 AM, Yury Norov wrote: > > ... > With all that, this example code: > > static int __init 128bit_test(void) > { > __uint128_t v; > __uint128_t addr; > __uint128_t val = (__uint128_t) 0x1234567890abc; > ... In case it

Re: [PATCH RFC 0/3] API for 128-bit IO access

2018-01-24 Thread Andy Shevchenko
On Wed, Jan 24, 2018 at 12:28 PM, Arnd Bergmann wrote: > On Wed, Jan 24, 2018 at 10:05 AM, Yury Norov > wrote: >> * For 128-bit read/write functions I take suffix 'o', which means read/write >> the octet of bytes. Is this name OK? > > Can't think of

Re: [PATCH RFC 0/3] API for 128-bit IO access

2018-01-24 Thread Arnd Bergmann
On Wed, Jan 24, 2018 at 10:05 AM, Yury Norov wrote: > This series adds API for 128-bit memory IO access and enables it for ARM64. > The original motivation for 128-bit API came from new Cavium network device > driver. The hardware requires 128-bit access to make things

Re: [PATCH RFC 0/3] API for 128-bit IO access

2018-01-24 Thread Will Deacon
On Wed, Jan 24, 2018 at 12:05:16PM +0300, Yury Norov wrote: > This series adds API for 128-bit memory IO access and enables it for ARM64. > The original motivation for 128-bit API came from new Cavium network device > driver. The hardware requires 128-bit access to make things work. See >

[PATCH RFC 0/3] API for 128-bit IO access

2018-01-24 Thread Yury Norov
Hi all, This series adds API for 128-bit memory IO access and enables it for ARM64. The original motivation for 128-bit API came from new Cavium network device driver. The hardware requires 128-bit access to make things work. See description in patch 3 for details. Also, starting from ARMv8.4,