mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: Colin Cross <ccross@google.com>, Ben Dooks <ben-linux@fluff.org>,
	Dilan Lee <dilee@nvidia.com>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] i2c/tegra: I2C driver uses the suspend_noirq/resume_noirq
Date: Fri, 12 Aug 2011 09:18:16 +0900	[thread overview]
Message-ID: <1313108296.19990.10.camel@finisterre.wolfsonmicro.main> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF04AEA24D09@HQMAIL01.nvidia.com>

On Thu, 2011-08-11 at 14:09 -0700, Stephen Warren wrote:
> Colin Cross wrote at Thursday, August 11, 2011 2:51 PM:

> Mark Brown wrote:
> > Unfortunately it's the only tool Linux has for dealing with this sort of
> > issue right now.  We were supposed to be getting support for telling the
> > PM core about dependencies but Linus didn't like that,

> Mark, can you fill in a little more detail; did Linus not like the concept
> of drivers registering dependencies on each-other, or was there a problem
> with the specific implementation that was proposed? I assume we're still a

He didn't like either, I think - he felt that probe ordering should be
sufficient. Which is true within the device model, in that devices can't
probe until all their resources are ready. This is coming up for ASoC
because that mechanism just doesn't work at all for us an we have to
work around it.

> long way away from anything like that working. You also mentioned Grant's
> device registration retry stuff, but doesn't that only solve the initial
> probing, not shutdown/suspend dependencies, or do devices take locks on
> each-other to handle that too?

Our current mechanism is based entirely on the order in which things get
instantiated so depending on the implementation of deferred binding we
may be able to change the ordering of the dpm_list.


  parent reply	other threads:[~2011-08-12  0:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-05 23:15 Stephen Warren
2011-08-06  4:33 ` Colin Cross
2011-08-06  8:48   ` Mark Brown
2011-08-11 19:35     ` Stephen Warren
2011-08-11 20:51       ` Colin Cross
2011-08-11 21:09         ` Stephen Warren
2011-08-11 21:43           ` Colin Cross
2011-08-12  0:45             ` Mark Brown
2011-08-12  2:59               ` Colin Cross
2011-08-12  3:14                 ` Mark Brown
2011-08-24 21:28                   ` Stephen Warren
2011-08-24 21:33                     ` Colin Cross
2011-08-30 16:25                       ` Stephen Warren
2011-08-31 16:28                         ` Arnd Bergmann
2011-08-31 16:31                           ` Mark Brown
2011-09-20 16:51                         ` Stephen Warren
2011-09-22 15:28                           ` Arnd Bergmann
2011-08-25 10:36                     ` Mark Brown
2011-08-12  0:18           ` Mark Brown [this message]
2011-09-22 17:01 ` Mark Brown

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=1313108296.19990.10.camel@finisterre.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=ben-linux@fluff.org \
    --cc=ccross@google.com \
    --cc=dilee@nvidia.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=swarren@nvidia.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

all inboxes | Powered by JetHome®