| 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
| ||
|
Message-ID: <5652B13E.6010706@linux.intel.com> Date: Mon, 23 Nov 2015 14:25:02 +0800 From: "Fu, Zhonghui" <zhonghui.fu@...ux.intel.com> To: Wolfram Sang <wsa@...-dreams.de> CC: linux-i2c@...r.kernel.org, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH v2] i2c: enable i2c device to suspend/resume asynchronously 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@...ux.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 > -- 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/
Powered by blists - more mailing lists