From: Wolfram Sang <wsa@the-dreams.de>
To: Shubhrajyoti Datta <shubhrajyoti.datta@gmail.com>
Cc: linux-i2c@vger.kernel.org, linux-sh@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
Simon Horman <horms@verge.net.au>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-pm@vger.kernel.org,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Subject: Re: [PATCH 0/2] i2c: proper RuntimePM for the adapter device
Date: Thu, 24 Dec 2015 09:41:06 +0100 [thread overview]
Message-ID: <20151224084105.GA1548@katana> (raw)
In-Reply-To: <CAKfKVtHt8BpakkffRp=_2GUxqK5JO0WCsizCrjtwH5hv+TWvWg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 504 bytes --]
> > RuntimePM for the logical adapter device should be handled in a central place
> > by the core, and not by drivers. This series does exactly that.
>
> This is good idea.
Thanks!
> Also maybe we can add a flag that the driver enables.
> that way for a short period till the driver removes the call
> the double call is not there.
The only driver I found was the s3c2410 and I fixed it. Is there another
one? Then, I'd update my series because I want a consistent state in one
go.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-12-24 8:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 17:19 [PATCH 0/2] i2c: proper RuntimePM for the adapter device Wolfram Sang
2015-12-23 17:19 ` [PATCH 1/2] i2c: always enable " Wolfram Sang
2016-01-10 8:27 ` Wolfram Sang
2015-12-23 17:19 ` [PATCH 2/2] i2c: s3c2410: remove superfluous runtime PM calls Wolfram Sang
2016-01-10 8:27 ` Wolfram Sang
2015-12-24 5:54 ` [PATCH 0/2] i2c: proper RuntimePM for the adapter device Shubhrajyoti Datta
2015-12-24 8:41 ` Wolfram Sang [this message]
2015-12-24 17:04 ` Shubhrajyoti Datta
2015-12-24 22:25 ` Wolfram Sang
2015-12-25 5:53 ` Shubhrajyoti Datta
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=20151224084105.GA1548@katana \
--to=wsa@the-dreams.de \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=s.nawrocki@samsung.com \
--cc=shubhrajyoti.datta@gmail.com \
/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).