On Thu, Apr 4, 2019 at 7:05 PM Maxime Ripard <maxime.ripard@xxxxxxxxxxx> wrote: > > On Thu, Apr 04, 2019 at 11:59:44AM +0100, Srinivas Kandagatla wrote: > > > > > > On 02/04/2019 16:45, Yangtao Li wrote: > > > Because there was an endianness issue. It seems that reg_read > > > function which the nvmem the driver currently exposes is wrong. > > > So add the new read function, the new function is used when the > > > native_endian flag is set. > > > > > > Signed-off-by: Yangtao Li <tiny.windzz@xxxxxxxxx> > > > > This patch and 5/5 does not apply cleanly on nvmem-next. > > Also I would need an ack from Maxime to be able to apply it. > > Chen-Yu has mostly been taking care of this recently, so I'd like his > feedback on this. As you previously requested, my patches already switch everything to native endianess. There's no need to differentiate between the old and the new now. So this patch and the native_endian flag is not needed. ChenYu
