All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-i2c@vger.kernel.org, linux-pm@vger.kernel.org,
	Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Krzysztof Kozlowski <k.kozlowski@samsung.com>
Subject: Re: [PATCH] i2c: s3c2410: remove superfluous runtime PM calls
Date: Wed, 16 Dec 2015 14:53:07 +0100	[thread overview]
Message-ID: <56716CC3.50309@samsung.com> (raw)
In-Reply-To: <1450203249-4873-1-git-send-email-wsa@the-dreams.de>

On 15/12/15 19:14, Wolfram Sang wrote:
> Since commit 6ada5c1e1b077a ("i2c: Mark adapter devices with
> pm_runtime_no_callbacks"), runtime PM on adapters turned into a no-op.
> So, we can remove these calls.

Won't this break i2c client devices that use runtime PM? Not sure
if any cases of such client exist now, I'll try to find some time
to test this change.

IIRC client's pm_runtime* calls return error if their parent device's
runtime PM is not enabled. Also enabling runtime PM on the i2c adapter
allows propagating runtime PM calls up to its parent - the i2c
controller platform device.

So perhaps in your patch we should only remove pm_runtime_get_sync,
pm_runtime_put calls, leaving runtime PM on the adapter enabled.
For any future cases where the Exynos I2C controller is not in an
always on power domain the runtime PM handling in this driver would
need to be further reworked anyway.

Perhaps we could just enable/disable adapter's runtime PM in i2c core.

--
Thanks,
Sylwester



  reply	other threads:[~2015-12-16 13:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-15 18:14 [PATCH] i2c: s3c2410: remove superfluous runtime PM calls Wolfram Sang
2015-12-16 13:53 ` Sylwester Nawrocki [this message]
2015-12-17  9:46   ` Charles Keepax
2015-12-19 10:52     ` Wolfram Sang
2015-12-19 10:50   ` Wolfram Sang
2015-12-19 17:05     ` Alan Stern
2015-12-19 21:57       ` Wolfram Sang

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=56716CC3.50309@samsung.com \
    --to=s.nawrocki@samsung.com \
    --cc=ckeepax@opensource.wolfsonmicro.com \
    --cc=k.kozlowski@samsung.com \
    --cc=lars@metafoo.de \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-pm@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 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.