All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Wolfram Sang <wsa@the-dreams.de>, linux-i2c@vger.kernel.org
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	"David E. Box" <david.e.box@linux.intel.com>
Subject: Re: designware platdrv and runtime pm?
Date: Tue, 10 Nov 2015 10:42:11 +0200	[thread overview]
Message-ID: <5641ADE3.6060704@linux.intel.com> (raw)
In-Reply-To: <20151109211503.GA3793@katana>

On 09.11.2015 23:15, Wolfram Sang wrote:
> Hi guys,
>
> while handling the merge conflict for the designware-platdrv, I noticed
> an asymmetry in the runtime PM handling. Currently, code looks like
> this:
>
> 	if (dev->pm_runtime_disabled) {
> 		pm_runtime_forbid(&pdev->dev);
> 	} else {
> 		pm_runtime_set_autosuspend_delay(&pdev->dev, 1000);
> 		pm_runtime_use_autosuspend(&pdev->dev);
> 		pm_runtime_set_active(&pdev->dev);
> 		pm_runtime_enable(&pdev->dev);
> 	}
>
> 	r = i2c_dw_probe(dev);
> 	if (r) {
> 		pm_runtime_disable(&pdev->dev);
> 		return r;
> 	}
>
> But shouldn't the above error path (and the remove path) also take
> dev->pm_runtime_disabled into account and act accordingly?
>
I think you are right. Which brings another question to my mind do we 
need to have a patch to linux-stable too?

David: Your original commit 894acb2f823b ("i2c: designware: Add Intel 
Baytrail PMIC I2C bus support") doesn't add pm_runtime_disabled test to 
dw_i2c_remove(). I guess there is possibility power down the shared 
controller by having CONFIG_I2C_DESIGNWARE_PLATFORM=m and then unloading 
the driver?

-- 
Jarkko

      reply	other threads:[~2015-11-10  8:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-09 21:15 designware platdrv and runtime pm? Wolfram Sang
2015-11-10  8:42 ` Jarkko Nikula [this message]

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=5641ADE3.6060704@linux.intel.com \
    --to=jarkko.nikula@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=david.e.box@linux.intel.com \
    --cc=linux-i2c@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.