linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: Unable to boot mainline on snow chromebook since 3.15
Date: Thu, 11 Sep 2014 10:22:32 +0100	[thread overview]
Message-ID: <20140911092233.CBC5CC40738@trevor.secretlab.ca> (raw)
In-Reply-To: <20140910165723.GK7960@sirena.org.uk>

On Wed, 10 Sep 2014 17:57:23 +0100, Mark Brown <broonie@kernel.org> wrote:
> On Wed, Sep 10, 2014 at 05:29:32PM +0100, Grant Likely wrote:
> 
> > What we can do is have an inhibit flag for
> > simplefb/simpleuart/simplewhatever that holds off PM. When a real
> > driver, or a stub that understands parsing the resource dependencies,
> > takes ownership of the device (or userspace tells the kernel to stop
> > caring) it can clear the inhibit.
> 
> It's not quite as simple as just disabling PM - for example in the
> clocks case we've also got to worry about what happens with rate changes
> (which is going to get more and more risky as we get smarter about being
> able to push configuration changes back up the tree), regulators have a
> similar thing with voltage changes.  With simple enables and disables we
> have to worry about things like handling users who actively want to
> power things on and and off but may potentially be sharing a resource
> with an undeclared dependency.

I think we can be okay with the above. This is a best-effort situation
where we don't want to tear down how firmware has set up the board if
it can be reasonably assumed that something depends on it (simplefb).
However, if clocks or regulators are shared with other devices and those
drivers ask for other settings, then there is simply no recourse. In
that situation there must be a driver for the video device that takes
care of any constraints.

g.

  reply	other threads:[~2014-09-11  9:22 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140905115704.GO13515@arm.com>
2014-09-05 12:22 ` Unable to boot mainline on snow chromebook since 3.15 Will Deacon
2014-09-05 13:46   ` Ajay kumar
2014-09-05 13:56     ` Vivek Gautam
2014-09-08 11:17       ` Will Deacon
2014-09-05 14:12     ` Marc Zyngier
2014-09-05 20:25   ` Doug Anderson
2014-09-07  9:06     ` Javier Martinez Canillas
2014-09-07 15:01       ` Mark Brown
2014-09-07 15:51         ` Javier Martinez Canillas
2014-09-07 15:52       ` Tomasz Figa
2014-09-07 16:12         ` Javier Martinez Canillas
2014-09-07 16:19           ` Tomasz Figa
2014-09-07 16:40             ` Javier Martinez Canillas
2014-09-08 11:21             ` Will Deacon
2014-09-08 11:55               ` Javier Martinez Canillas
2014-09-08 12:46                 ` Will Deacon
2014-09-08 12:20               ` Grant Likely
2014-09-08 13:49                 ` Mark Brown
2014-09-08 14:05                   ` Javier Martinez Canillas
2014-09-10 11:17                     ` Will Deacon
2014-09-10 16:03                       ` Doug Anderson
2014-09-10 16:23                         ` Will Deacon
2014-09-08 15:58                 ` Doug Anderson
2014-09-08 19:40                   ` Grant Likely
2014-09-10 13:06                     ` Olof Johansson
2014-09-10 14:31                       ` Mark Brown
2014-09-10 14:56                         ` Grant Likely
2014-09-10 15:39                           ` Mark Brown
2014-09-10 16:29                             ` Grant Likely
2014-09-10 16:45                               ` Doug Anderson
2014-09-10 19:45                                 ` Mark Brown
2014-09-10 19:51                                   ` Doug Anderson
2014-09-10 16:57                               ` Mark Brown
2014-09-11  9:22                                 ` Grant Likely [this message]
2014-09-11 18:03                                   ` Mark Brown
2014-09-11 22:54                                     ` Doug Anderson
2014-09-29 12:57                           ` Thierry Reding
2014-09-29 13:12                             ` Grant Likely
2014-09-29 16:37                               ` Mark Brown
2014-09-30  6:12                               ` Thierry Reding
2014-09-29 20:46                             ` Maxime Ripard
2014-09-10 16:36                         ` Olof Johansson
2014-09-10 18:17                           ` Mark Brown
2014-09-11  9:06                         ` Grant Likely
2014-09-11 16:16                           ` Mark Brown
2014-09-08  4:36         ` Doug Anderson
2014-09-08  6:09           ` Javier Martinez Canillas
2014-09-08 15:55             ` Doug Anderson
2014-09-08 16:07               ` Will Deacon
2014-09-08 16:12                 ` Doug Anderson
2014-09-08 10:20           ` Mark Brown
2014-09-08  4:43         ` Doug Anderson
2015-01-30  4:56 bruce m beach

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=20140911092233.CBC5CC40738@trevor.secretlab.ca \
    --to=grant.likely@secretlab.ca \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).