From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Boswell, Patrick" <Patrick.Boswell@Sypris.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: OMAP 3530 without a PMIC
Date: Wed, 23 Feb 2011 12:06:49 -0800 [thread overview]
Message-ID: <20110223200648.GA2534@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <0bfe01cbd363$e8ff6a91$cb0a10ac@sypris.com>
On Wed, Feb 23, 2011 at 09:14:10AM -0500, Boswell, Patrick wrote:
Don't top post and please fix your mail client to word wrap within
paragraphs.
> I will check that out Mark.
> I did notice that there was discussion a while back about "dummy
> regulators". I think that might work -- has anyone tried this
> approach?
That's implemented but isn't really relevant if you're not using
regulators on your system. It's also a bit of a stopgap solution - it
papers over the issue at runtime but ideally the code would make it
clear that everything is working correctly.
next prev parent reply other threads:[~2011-02-23 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 14:14 OMAP 3530 without a PMIC Boswell, Patrick
2011-02-23 20:06 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-22 20:41 Boswell, Patrick
2011-02-22 22:00 ` 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=20110223200648.GA2534@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Patrick.Boswell@Sypris.com \
--cc=linux-omap@vger.kernel.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