From: Samuel Ortiz <sameo@linux.intel.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: linux-kernel@vger.kernel.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
linux-omap@vger.kernel.org, Tero Kristo <t-kristo@ti.com>
Subject: Re: [PATCH] MFD: twl6040: Add regulator support for VIO, V2V1 supplies
Date: Wed, 9 May 2012 22:02:06 +0200 [thread overview]
Message-ID: <20120509200206.GA17206@sortiz-mobl> (raw)
In-Reply-To: <1335966882-19897-1-git-send-email-peter.ujfalusi@ti.com>
Hi Peter,
On Wed, May 02, 2012 at 04:54:42PM +0300, Peter Ujfalusi wrote:
> twl6040 has three power supply source:
> VBAT needs to be connected to VBAT, VIO, and V2V1.
> Add regulator support for the VIO, V2V1 supplies.
> Initially handle the two supply together with bulk commands.
>
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> Reviewed-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> drivers/mfd/twl6040-core.c | 33 +++++++++++++++++++++++++++++----
> include/linux/mfd/twl6040.h | 2 ++
> 2 files changed, 31 insertions(+), 4 deletions(-)
>
> Hi Samuel,
>
> The runtime dependencies for this patch has been sent to linux-omap list:
> http://marc.info/?l=linux-omap&m=133596645010228&w=2
> http://marc.info/?l=linux-omap&m=133596645610232&w=2
> http://marc.info/?l=linux-omap&m=133596644310224&w=2
> http://marc.info/?l=linux-omap&m=133596643310220&w=2
>
> Alone this patch does not cause compile time regression but in runtime it needs
> the arch/arm/mach-omap2 patches.
> I try to avoid cross tree issues as much as I can and I'm happy if these will
> come together in linux-next (and finally in 3.5).
I applied this one to my nfc-next branch, thanks.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2012-05-09 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 13:54 [PATCH] MFD: twl6040: Add regulator support for VIO, V2V1 supplies Peter Ujfalusi
2012-05-09 20:02 ` Samuel Ortiz [this message]
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=20120509200206.GA17206@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=t-kristo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox