[lkml]   [2018]   [May]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 1/2] i2c: sprd: Prevent i2c accesses after suspend is called

On 05/02/2018 12:48 AM, Baolin Wang wrote:
> On 2 May 2018 at 13:23, Wolfram Sang <> wrote:
>>>> We should maybe handle this in the core somewhen, though. Or?
>>> Thanks. Yes, It will more helpful if we can handle this in the i2c core.
>> To understand the issue better: which kind of devices in your system
>> still send I2C transfers when the system is going to suspend? Do you
>> know?
> Now we found the touch screen device will trigger I2C transfers when
> the system is going to suspend.

And you have to fix it (touch screen) - not your i2c driver. Otherwise, you can get
situation when set of I2C transfers (executed from some kthread/work/threaded_irq/..)
will be just interrupted in the middle - usual behavior after this is (I2C timeout) [and/or
not-functional I2C client device [and/or I2C bus stuck (worst case)].

In case, somebody is trying to access I2C after .suspend_noirq() stage I2C bus driver
should produce big fat warning and, most probably, abort suspend.
Above, in general, can be part of I2C core functionality.


 \ /
  Last update: 2018-05-03 18:27    [W:0.130 / U:4.164 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site