linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Balaji T K <balajitk@ti.com>,
	lrg@slimlogic.co.uk, sameo@linux.intel.com,
	linux-omap@vger.kernel.org
Subject: Re: [PATCH v2 1/2] regulator: twl: add clk32kg to twl-regulator
Date: Mon, 14 Feb 2011 16:01:43 -0800	[thread overview]
Message-ID: <20110215000143.GV20795@atomide.com> (raw)
In-Reply-To: <20110214211558.GL20795@atomide.com>

* Tony Lindgren <tony@atomide.com> [110214 13:14]:
> * Mark Brown <broonie@opensource.wolfsonmicro.com> [110211 03:17]:
> > On Thu, Feb 10, 2011 at 06:44:50PM +0530, Balaji T K wrote:
> > > In OMAP4 Blaze and Panda, 32KHz clock to WLAN is supplied from Phoenix TWL6030.
> > > The 32KHz clock state (ON/OFF) is configured in CLK32KG_CFG_[GRP, TRANS, STATE]
> > > register. This follows the same register programming model as other regulators
> > > in TWL6030. So add CLK32KG as pseudo regulator.
> > > 
> > > Signed-off-by: Balaji T K <balajitk@ti.com>
> > 
> > Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> > 
> > Though I can see someone wanting an adaption to the clock API on top of
> > this at some point.
> 
> Samuel should queue this one, I'll queue 2/2 of this series. These
> can be queued separately.

Oops no they can't, the second patch depends on clk32kg. Samuel, can
you please queue both? Will reply to the second one with my ack.

Tony

  reply	other threads:[~2011-02-15  0:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-10 13:14 [PATCH v2 1/2] regulator: twl: add clk32kg to twl-regulator Balaji T K
2011-02-11 11:19 ` Mark Brown
2011-02-14 21:15   ` Tony Lindgren
2011-02-15  0:01     ` Tony Lindgren [this message]
2011-02-21 12:34       ` Samuel Ortiz

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=20110215000143.GV20795@atomide.com \
    --to=tony@atomide.com \
    --cc=balajitk@ti.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=sameo@linux.intel.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;
as well as URLs for NNTP newsgroup(s).