Re: [RFC PATCH] mmc: tmio: use ioread* for repeated access to a register

2017-12-19 Thread Wolfram Sang
Yamada-san, > BTW, is ioread* preferred to read*? Technically, yes. In reality, mostly not. > We need to eliminate the root cause. > Other drivers using reads* cannot enable COMPILE_TEST for the same reason. Sure, I understand this. There are not many left, however. I'd assume most switched to

Re: [RFC PATCH] mmc: tmio: use ioread* for repeated access to a register

2017-12-18 Thread Masahiro Yamada
2017-12-18 22:01 GMT+09:00 Ulf Hansson : > On 18 December 2017 at 01:00, Wolfram Sang > wrote: >> Not all archs define reads* and writes*. Switch to ioread*_rep and >> friends which is defined everywhere, so we can enable COMPILE_TEST

Re: [RFC PATCH] mmc: tmio: use ioread* for repeated access to a register

2017-12-18 Thread Ulf Hansson
On 18 December 2017 at 01:00, Wolfram Sang wrote: > Not all archs define reads* and writes*. Switch to ioread*_rep and > friends which is defined everywhere, so we can enable COMPILE_TEST after > that. > > Signed-off-by: Wolfram Sang

Re: [RFC PATCH] mmc: tmio: use ioread* for repeated access to a register

2017-12-17 Thread Ian Molton
On 18/12/17 00:00, Wolfram Sang wrote: > Not all archs define reads* and writes*. Switch to ioread*_rep and > friends which is defined everywhere, so we can enable COMPILE_TEST after > that. > > Signed-off-by: Wolfram Sang > --- > > So, I pushed this to

[RFC PATCH] mmc: tmio: use ioread* for repeated access to a register

2017-12-17 Thread Wolfram Sang
Not all archs define reads* and writes*. Switch to ioread*_rep and friends which is defined everywhere, so we can enable COMPILE_TEST after that. Signed-off-by: Wolfram Sang --- So, I pushed this to buildbot on top of Yamada-san's patch series and there were no