All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Fu, Zhonghui" <zhonghui.fu@linux.intel.com>
To: Wolfram Sang <wsa@the-dreams.de>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Jarkko Nikula <jarkko.nikula@linux.intel.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	linux-i2c@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] i2c/designware: enable i2c controller to suspend/resume asynchronously
Date: Tue, 8 Mar 2016 16:05:43 +0800	[thread overview]
Message-ID: <56DE87D7.7060205@linux.intel.com> (raw)
In-Reply-To: <20160201155422.GC10607@tetsubishi>



On 2/1/2016 11:54 PM, Wolfram Sang wrote:
>>>> device may be completed in separate kernel thread. PM core ensures
>>>> all power state transition dependency between devices. This patch
> I'd like an Ack on that from a PM maintainer, because I think chips like
> PMICs are special and might not be covered by the generic case...
>
>> Besides that we have to be really aware about DMA power related fix
>> introduced in v4.5-rc1 in acpi_lpss.c [1]. So, I would like to see a
>> wide testing especially on Intel Baytrail / Braswell platforms before
>> enabling it.
> And this one, too.
Because of long leave, so sorry for very late reply.

I agree with you. Need more investigation and test for this patch before enabling it.


Thanks,
Zhonghui
>

  reply	other threads:[~2016-03-08  8:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-15  6:38 [PATCH v2] i2c/designware: enable i2c controller to suspend/resume asynchronously Fu, Zhonghui
2016-02-01 15:04 ` Jarkko Nikula
2016-02-01 15:16   ` Andy Shevchenko
2016-02-01 15:54     ` Wolfram Sang
2016-03-08  8:05       ` Fu, Zhonghui [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-09-24  7:10 Fu, Zhonghui
2015-11-16 15:42 ` 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=56DE87D7.7060205@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.