linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Fu, Zhonghui" <zhonghui.fu@linux.intel.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-i2c@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] i2c: enable i2c device to suspend/resume asynchronously
Date: Mon, 23 Nov 2015 14:25:02 +0800	[thread overview]
Message-ID: <5652B13E.6010706@linux.intel.com> (raw)
In-Reply-To: <20151020150200.GE5379@katana>



On 10/20/2015 11:02 PM, Wolfram Sang wrote:
> On Thu, Sep 24, 2015 at 02:26:23PM +0800, Fu, Zhonghui wrote:
>> Now, PM core supports asynchronous suspend/resume mode for devices
>> during system suspend/resume, and the power state transition of one
>> device may be completed in separate kernel thread. PM core ensures
>> all power state transition timing dependency between devices. This
>> patch enables i2c device to suspend/resume asynchronously. This will
>> take advantage of multicore and improve system suspend/resume speed.
>>
>> Signed-off-by: Zhonghui Fu <zhonghui.fu@linux.intel.com>
> Does it always work when say a PMIC or clock controller is connected to
> the I2C bus?
Sorry for missing this mail.

Yes, it does not care about what device. The sole difference of asynchronous suspend/resume mode is that the suspend/resume operation of one device is carried out in a separate kernel thread, and PM core ensures all related dependency.


Thanks,
Zhonghui


>

  reply	other threads:[~2015-11-23  6:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24  6:26 [PATCH v2] i2c: enable i2c device to suspend/resume asynchronously Fu, Zhonghui
2015-10-20 15:02 ` Wolfram Sang
2015-11-23  6:25   ` Fu, Zhonghui [this message]
2015-11-16 15:26 ` Fu, Zhonghui

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=5652B13E.6010706@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).