From: Tony Lindgren <tony@atomide.com>
To: David Brownell <david-b@pacbell.net>
Cc: OMAP <linux-omap@vger.kernel.org>
Subject: Re: [patch 2.6.29-rc2-omap1-git 0/7] regulator and MMC updates...
Date: Wed, 4 Feb 2009 11:27:26 -0800 [thread overview]
Message-ID: <20090204192725.GN7215@atomide.com> (raw)
In-Reply-To: <200901200244.36238.david-b@pacbell.net>
* David Brownell <david-b@pacbell.net> [090120 03:01]:
> Several patches here:
>
> - New interface in regulator core ... in the regulator queue
> (presumably for 2.6.30 merge)
>
> - twl4030 regulator updates to use that interface
>
> Given that second part, I think the twl4030 regulator code can
> be submitted upstream.
>
> - Init updates for OMAP 3430 SDP ... regulators, MMC switches,
> and a bit more.
>
> - Minor Overo init update: set up VMMC1
>
> - HSMMC init update: pass device back so regulator setup can
> use it. (Not as invasive as a cleaner fix would be...)
>
> - Beagle init update: hook up the regulators used by MMC-1
> (relies on that init update)
>
> - SDP init update: hook up regulators used by MMC-1 and MMC-2
> (also relies on that init update)
>
> These go on top of patches I sent previously, to work around
> a lockdep issue in the hsmmc driver (that might go to mainline
> as a bugfix, assuming that driver goes to mainline for 2.6.29)
> and correct the mach-omap2/mmc-twl4030.c power switching.
>
> Once that's merged, it'll be ready to start using the regulator
> calls to switch power for MMC on at least those platforms.
Pushing this series to l-o tree. Again, let me know what to add to the
upstream queues (and when).
Regards,
Tony
next prev parent reply other threads:[~2009-02-04 19:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 10:44 [patch 2.6.29-rc2-omap1-git 0/7] regulator and MMC updates David Brownell
2009-01-20 10:45 ` [patch 2.6.29-rc2-omap1-git 1/7] regulator get_status() David Brownell
2009-01-20 10:48 ` [patch 2.6.29-rc2-omap1-git 2/7] twl4030 regulator uses new get_status() op David Brownell
2009-01-20 10:49 ` [patch 2.6.29-rc2-omap1-git 3/7] 3430SDP init updates David Brownell
2009-01-20 10:51 ` [patch 2.6.29-rc2-omap1-git 4/7] minor overo init update David Brownell
2009-01-20 10:52 ` [patch 2.6.29-rc2-omap1-git 5/7] hsmmc init passes device nodes back David Brownell
2009-01-20 10:53 ` [patch 2.6.29-rc2-omap1-git 6/7] beagle regulator updates David Brownell
2009-01-20 10:54 ` [patch 2.6.29-rc2-omap1-git 7/7] 3430SDP " David Brownell
2009-02-04 19:27 ` Tony Lindgren [this message]
2009-02-04 23:20 ` [patch 2.6.29-rc2-omap1-git 0/7] regulator and MMC updates David Brownell
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=20090204192725.GN7215@atomide.com \
--to=tony@atomide.com \
--cc=david-b@pacbell.net \
--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