This patch is ported from linux stable 4.9, commit
3587c856675c45809010c2cee5b21096f6e8e938.
So I think I don't need to port on version 4.9.
On 9/8/2017 2:21 PM, Greg KH wrote:
On Fri, Sep 08, 2017 at 09:46:02AM +0700, Nhan Nguyen wrote:
commit 3587c856675c45809010c2cee5b21096f6e8e938 upstream
On Fri, Sep 08, 2017 at 06:22:02PM +0700, Nhan Ngoc. Nguyen wrote:
> This patch is ported from linux stable 4.9, commit
> 3587c856675c45809010c2cee5b21096f6e8e938.
No, commit 3587c856675c45809010c2cee5b21096f6e8e938 showed up in
4.11-rc1:
$ git describe --contains 3587c856675c45809010c2ce
commit 3587c856675c45809010c2cee5b21096f6e8e938 upstream.
I've found that by just turning the chip on and off via the
POWER_DOWN register, I end up getting i2c_transfer errors on
HiKey.
Investigating further, it turns out that some of the register
state in hardware is getting lost, as the device
On Fri, Sep 08, 2017 at 09:46:02AM +0700, Nhan Nguyen wrote:
> commit 3587c856675c45809010c2cee5b21096f6e8e938 upstream.
>
> I've found that by just turning the chip on and off via the
> POWER_DOWN register, I end up getting i2c_transfer errors on
> HiKey.
>
> Investigating further, it turns out