From: "Fu, Zhonghui" <zhonghui.fu@linux.intel.com>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Wolfram Sang <wsa@the-dreams.de>
Cc: linux-i2c@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
srinivas.kowtal@intel.com
Subject: Re: [PATCH] i2c/designware: enable i2c controller to suspend/resume asynchronously
Date: Fri, 15 Jan 2016 14:42:42 +0800 [thread overview]
Message-ID: <569894E2.208@linux.intel.com> (raw)
In-Reply-To: <568B848F.1070801@linux.intel.com>
On 1/5/2016 4:53 PM, Jarkko Nikula wrote:
> Hi
>
> On 12/24/2015 04:30 PM, 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 dependency between devices. This patch
>> enables designware i2c controllers to suspend/resume asynchronously.
>> This will take advantage of multicore and improve system suspend/resume
>> speed. After enabling all i2c devices, i2c adapters and i2c controllers
>> on ASUS T100TA tablet, the system suspend-to-idle time is reduced to
>> about 510ms from 750ms, and the system resume time is reduced to about
>> 790ms from 900ms.
>>
> Nice reduction :-)
>
>> diff --git a/drivers/i2c/busses/i2c-designware-platdrv.c b/drivers/i2c/busses/i2c-designware-platdrv.c
>> index 6b00061..395130b 100644
>> --- a/drivers/i2c/busses/i2c-designware-platdrv.c
>> +++ b/drivers/i2c/busses/i2c-designware-platdrv.c
>> @@ -230,6 +230,7 @@ static int dw_i2c_plat_probe(struct platform_device *pdev)
>> }
>>
>> adap = &dev->adapter;
>> + device_enable_async_suspend(&pdev->dev);
>> adap->owner = THIS_MODULE;
>> adap->class = I2C_CLASS_DEPRECATED;
>> ACPI_COMPANION_SET(&adap->dev, ACPI_COMPANION(&pdev->dev));
>
> Does device_enable_async_suspend() need to be called before enabling runtime PM? I suppose not since there appears to have also related sysfs node for toggling it runtime.
>
> I'm thinking if you could move the device_enable_async_suspend() call into drivers/i2c/busses/i2c-designware-core.c: i2c_dw_probe() and then also PCI enumerated adapter could take advantage of it.
Because of long leave, so sorry for late reply.
Your proposal is right. I have submitted a new patch according to your comments - "[PATCH v2] i2c/designware: enable i2c controller to suspend/resume asynchronously".
Thanks,
Zhonghui
next prev parent reply other threads:[~2016-01-15 6:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 14:30 [PATCH] i2c/designware: enable i2c controller to suspend/resume asynchronously Fu, Zhonghui
2016-01-05 8:53 ` Jarkko Nikula
2016-01-05 12:14 ` Andy Shevchenko
2016-01-15 7:01 ` Fu, Zhonghui
2016-01-15 6:42 ` Fu, Zhonghui [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-17 16:36 Fu, Zhonghui
[not found] ` <55D20D79.3090308-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2015-08-24 15:23 ` Fu, Zhonghui
2015-09-24 7:12 ` 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=569894E2.208@linux.intel.com \
--to=zhonghui.fu@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=srinivas.kowtal@intel.com \
--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).