All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <felipe.balbi@nokia.com>
To: "ext Krishnamoorthy, Balaji T" <balajitk@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"tony@atomide.com" <tony@atomide.com>,
	"khilman@deeprootsystems.com" <khilman@deeprootsystems.com>,
	"david-b@pacbell.net" <david-b@pacbell.net>,
	"Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
	"Nayak, Rajendra" <rnayak@ti.com>
Subject: Re: [RFC][PATCH 0/4] TWL6030 patch series
Date: Mon, 20 Jul 2009 15:11:57 +0300	[thread overview]
Message-ID: <20090720121157.GA13867@nokia.com> (raw)
In-Reply-To: <19F8576C6E063C45BE387C64729E739404329D66BE@dbde02.ent.ti.com>

Hi,

On Mon, Jul 20, 2009 at 01:59:41PM +0200, ext Krishnamoorthy, Balaji T wrote:
> The upcoming TWL6030 is companion chip for OMAP4 like the current TWL4030
> for OMAP3. This patch series adds support for TWL6030 irq framework, and 
> driver support for RTC and regulator.
> 
> 	drivers/mfd/twl6030-irq.c  files is newly added as INTERRUPT status 
> 		registers, ack and clear mechanism has changed from twl4030,5030.
> 	drivers/rtc/rtc-twl.c will support twl4030,twl5030, and also twl6030 rtc
> 	drivers/regulator/twl-regulator.c will support twl regulators.
> 	include/linux/i2c/twl.h  will have TWL4030 and TWL6030 offsets selected 
> 		at compile time by CONFIG_TWL4030_CORE / CONFIG_TWL6030_CORE
> 
> These patches are generated against mainline 2.6.31-rc1 and dependancy on my
> 1st series[1].
> Patch list:
> 	[RFC][PATCH 1/4] OMAP4: PMIC: Add support for twl6030 irq framework
> 	[RFC][PATCH 2/4] OMAP4: PMIC: Add support for twl6030 RTC
> 	[RFC][PATCH 3/4] OMAP4: PMIC: Add support for twl6030 regulators
> 	[RFC][PATCH 4/4] OMAP4: PMIC: Update TWL mfd driver to create twl6030 regulators
> 
> Needed board-* changes and defconfig chages will be done later.Please let me 
> know your feedback/suggestion on this patch series.

send these to lkml and Cc linux-omap. Also add to Cc:

Samuel Ortiz <sameo@openedhand.com>
Wim Van Sebroeck <wim@iguana.be>
Timo Kokkonen <timo.t.kokkonen@nokia.com>
Ben Dooks <ben-linux@fluff.org>
linux-i2c@vger.kernel.org
linux-kernel@vger.kernel.org

-- 
balbi

  reply	other threads:[~2009-07-20 12:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-20 11:59 [RFC][PATCH 0/4] TWL6030 patch series Krishnamoorthy, Balaji T
2009-07-20 12:11 ` Felipe Balbi [this message]
2009-07-20 12:15   ` Mark Brown
2009-07-20 13:00     ` Krishnamoorthy, Balaji T
2009-07-24  4:16     ` Shilimkar, Santosh
2009-07-24  9:20       ` Mark Brown
2009-08-03  6:15         ` Shilimkar, Santosh
2009-08-03 14:25           ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2009-07-20 13:34 Krishnamoorthy, Balaji T
2009-08-06  8:58 ` Krishnamoorthy, Balaji T
2009-08-11 13:00   ` Krishnamoorthy, Balaji T
2009-08-17  0:00     ` Samuel Ortiz
2009-08-17  5:16       ` Krishnamoorthy, Balaji T
2009-08-17  9:14         ` Samuel Ortiz
2009-08-17  9:42           ` Krishnamoorthy, Balaji T

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=20090720121157.GA13867@nokia.com \
    --to=felipe.balbi@nokia.com \
    --cc=balajitk@ti.com \
    --cc=david-b@pacbell.net \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=rnayak@ti.com \
    --cc=santosh.shilimkar@ti.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 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.