linux-kernel - Re: [PATCH] i2c: enable i2c adapter to suspend/resume asynchronously

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <56039D69.1040602@linux.intel.com>
Date:	Thu, 24 Sep 2015 14:51:21 +0800
From:	"Fu, Zhonghui" <zhonghui.fu@...ux.intel.com>
To:	wsa@...-dreams.de
CC:	linux-i2c@...r.kernel.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] i2c: enable i2c adapter to suspend/resume asynchronously


Hi,

I have resent this patch with updated commit message - "[PATCH v2] i2c: enable i2c adapter to suspend/resume asynchronously".


Thanks,
Zhonghui

On 2015/8/24 23:22, Fu, Zhonghui wrote:
> Hi,
>
> Any comments are welcome.
>
>
> Thanks,
> Zhonghui
>
>
>
> On 2015/8/18 0:17, Fu, Zhonghui wrote:
>> Enable i2c adapter to suspend/resume asynchronously. This can improve
>> system suspend/resume speed.
>>
>> Signed-off-by: Zhonghui Fu <zhonghui.fu@...ux.intel.com>
>> ---
>>  drivers/i2c/i2c-core.c |    2 ++
>>  1 files changed, 2 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/i2c/i2c-core.c b/drivers/i2c/i2c-core.c
>> index c83e4d1..90251be 100644
>> --- a/drivers/i2c/i2c-core.c
>> +++ b/drivers/i2c/i2c-core.c
>> @@ -1439,6 +1439,8 @@ static int i2c_register_adapter(struct i2c_adapter *adap)
>>  
>>  	pm_runtime_no_callbacks(&adap->dev);
>>  
>> +	device_enable_async_suspend(&adap->dev);
>> +
>>  #ifdef CONFIG_I2C_COMPAT
>>  	res = class_compat_create_link(i2c_adapter_compat_class, &adap->dev,
>>  				       adap->dev.parent);
>> -- 1.7.1
>>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/