From: David Brownell <david-b@pacbell.net>
To: Mark Brown <broonie@sirena.org.uk>
Cc: Tony Lindgren <tony@atomide.com>,
Steve Sakoman <sakoman@gmail.com>,
linux-omap <linux-omap@vger.kernel.org>
Subject: Re: Overo broken after recent mainline merge
Date: Sat, 14 Mar 2009 20:18:55 -0700 [thread overview]
Message-ID: <200903142018.55337.david-b@pacbell.net> (raw)
In-Reply-To: <20090314223435.GA6523@sirena.org.uk>
On Saturday 14 March 2009, Mark Brown wrote:
> > A third approach (after applying that one patch that's
> > in the regulator-next tree) would be
>
> > if (rdev->is_enabled() > 0)
> > rdev->use_count = 1;
>
> That won't work with consumers that can share their supply - they can't
> tell if the regulator was enabled because it was left on at startup or
> if it was enabled by some other consumer.
It works *exactly* like it would if the bootloader were
able to poke the "boot_on" flag for each regulator it
left enabled.
It also helps that the typical scenario I need to care
about is where there's only one consumer ... but in any
case, the change sketched above can't add new problems.
- Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-03-15 3:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-14 13:24 Overo broken after recent mainline merge Steve Sakoman
2009-03-14 16:12 ` Tony Lindgren
2009-03-14 19:08 ` David Brownell
2009-03-14 20:22 ` Mark Brown
2009-03-14 21:14 ` David Brownell
2009-03-14 22:34 ` Mark Brown
2009-03-15 3:18 ` David Brownell [this message]
2009-03-15 3:36 ` David Brownell
2009-03-14 23:47 ` Steve Sakoman
2009-03-15 2:00 ` David Brownell
2009-03-15 3:56 ` Steve Sakoman
2009-03-15 19:56 ` Steve Sakoman
2009-03-15 22:15 ` Steve Sakoman
2009-03-15 22:32 ` Steve Sakoman
2009-03-15 23:16 ` David Brownell
2009-03-20 19:18 ` [APPLIED] " Tony Lindgren
2009-03-20 22:33 ` David Brownell
2009-03-23 16:00 ` Mark Brown
2009-03-23 19:27 ` [APPLIED] " Tony Lindgren
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=200903142018.55337.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=broonie@sirena.org.uk \
--cc=linux-omap@vger.kernel.org \
--cc=sakoman@gmail.com \
--cc=tony@atomide.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).