linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Fu, Zhonghui" <zhonghui.fu@linux.intel.com>
To: wsa@the-dreams.de
Cc: linux-i2c@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] i2c: enable i2c device to suspend/resume asynchronously
Date: Thu, 24 Sep 2015 14:27:58 +0800	[thread overview]
Message-ID: <560397EE.1020308@linux.intel.com> (raw)
In-Reply-To: <55DB35AC.3080701@linux.intel.com>


Hi,

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


Thanks,
Zhonghui

On 2015/8/24 23:18, Fu, Zhonghui wrote:
> Hi,
>
> Any comments are welcome.
>
>
> Thanks,
> Zhonghui
>
>
>
> On 2015/8/18 0:07, Fu, Zhonghui wrote:
>> Enable i2c device to suspend/resume asynchronously. This can improve
>> system suspend/resume speed.
>>
>> Signed-off-by: Zhonghui Fu <zhonghui.fu@linux.intel.com>
>> ---
>>  drivers/i2c/i2c-core.c |    1 +
>>  1 files changed, 1 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/i2c/i2c-core.c b/drivers/i2c/i2c-core.c
>> index c83e4d1..6587681 100644
>> --- a/drivers/i2c/i2c-core.c
>> +++ b/drivers/i2c/i2c-core.c
>> @@ -987,6 +987,7 @@ i2c_new_device(struct i2c_adapter *adap, struct i2c_board_info const *info)
>>  	client->dev.of_node = info->of_node;
>>  	client->dev.fwnode = info->fwnode;
>>  
>> +	device_enable_async_suspend(&client->dev);
>>  	i2c_dev_set_name(adap, client);
>>  	status = device_register(&client->dev);
>>  	if (status)
>> -- 1.7.1
>>

      reply	other threads:[~2015-09-24  6:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-17 16:07 [PATCH] i2c: enable i2c device to suspend/resume asynchronously Fu, Zhonghui
2015-08-24 15:18 ` Fu, Zhonghui
2015-09-24  6:27   ` Fu, Zhonghui [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=560397EE.1020308@linux.intel.com \
    --to=zhonghui.fu@linux.intel.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wsa@the-dreams.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).