All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: Kalle Jokiniemi <kalle.jokiniemi@digia.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"felipe.balbi@nokia.com" <felipe.balbi@nokia.com>
Subject: Re: [PATCH 0/1] TWL: USB: disable VUSB regulators
Date: Wed, 21 Jan 2009 13:47:05 -0800	[thread overview]
Message-ID: <200901211347.05694.david-b@pacbell.net> (raw)
In-Reply-To: <13B9B4C6EF24D648824FF11BE896716203751D487F@dlee02.ent.ti.com>

On Wednesday 21 January 2009, Woodruff, Richard wrote:
> A simple but impacting point is a LDO when left on, wastes a lot of system power.

So I guess I'll poke a bit harder at finding ways to
make sure the LDOs on the twl4030 get turned off..
this patch looks like a good start (since the VUSB
regulators are completely set up).

VAUX3 seems to be inappropriately enabled on a lot
of OMAP3 boards; short of fixing u-boot, that'd be
another bit of low-hanging fruit.


> Didn't know Dave was such a poet :)

Well, I dunno about the rhyme or scansion, but I
do sort of like the "feral code" imagery.  It seems
to highlight some key behaviors better than many
more familiar terms!

- Dave

  reply	other threads:[~2009-01-21 21:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21 13:15 [PATCH 0/1] TWL: USB: disable VUSB regulators Kalle Jokiniemi
2009-01-21 13:15 ` [PATCH 1/1] TWL: USB: disable VUSB regulators when cable unplugged Kalle Jokiniemi
2009-01-22 17:55   ` David Brownell
2009-01-27  9:50     ` Kalle Jokiniemi
2009-01-28  2:02       ` David Brownell
2009-01-28  6:36         ` Kalle Jokiniemi
2009-01-21 20:38 ` [PATCH 0/1] TWL: USB: disable VUSB regulators David Brownell
2009-01-21 21:19   ` Woodruff, Richard
2009-01-21 21:47     ` David Brownell [this message]
2009-01-23 10:55   ` Kalle Jokiniemi

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=200901211347.05694.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=felipe.balbi@nokia.com \
    --cc=kalle.jokiniemi@digia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=r-woodruff2@ti.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 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.