linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] S3C2443: add power domain for usb phy
Date: Tue, 24 Jan 2012 12:12:46 +0200	[thread overview]
Message-ID: <20120124101245.GG27414@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <201201241109.48749.heiko@sntech.de>

On Tue, Jan 24, 2012 at 11:09:48AM +0100, Heiko St?bner wrote:
> Am Dienstag, 24. Januar 2012, 10:51:31 schrieb Felipe Balbi:
> > On Tue, Jan 24, 2012 at 10:50:14AM +0100, Heiko St?bner wrote:
> > > Hi Felipe,
> > > 
> > > Am Dienstag, 24. Januar 2012, 10:38:32 schrieb Felipe Balbi:
> > > > Hi,
> > > > 
> > > > On Sun, Jan 08, 2012 at 09:59:02PM +0100, Heiko St?bner wrote:
> > > > > The phy-power-handling is common to S3C2443/2416/2450, so introduce a
> > > > > s3c2443-pm-common.c to handle this for all of them.
> > > > > 
> > > > > This makes it possible to remove the raw write to the PWRCFG-register
> > > > > from the s3c-hsudc driver.
> > > > > 
> > > > > Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> > > > 
> > > > I believe this doesn't really depend on previous patches (??) In that
> > > 
> > > > case, it can be carried with s3c's tree:
> > > it does depend on the previous patch [2/3], as the device power domain is
> > > controlled through the runtime-pm subsystem whose calls were added in it.
> > 
> > then I will need proper acks to carry this patch.
> 
> ok, I will pester Kukjin Kim more about it to get the needed ack :-) .
> 
> If changes are requested to this third patch should I only resubmit this one 
> or all of them again - i.e. will you still keep the first two patches?

first two are already applied so no need to resend them :-)

-- 
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120124/ca419423/attachment.sig>

  reply	other threads:[~2012-01-24 10:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-08 20:56 [PATCH 0/3] s3c-hsudc powerdomain using generic power domains Heiko Stübner
2012-01-08 20:57 ` [PATCH 1/3] s3c-hsudc: Use helper functions instead of generic container_of Heiko Stübner
2012-01-24  9:36   ` Felipe Balbi
2012-01-08 20:58 ` [PATCH 2/3] s3c-hsudc: add basic runtime_pm calls Heiko Stübner
2012-01-24  9:37   ` Felipe Balbi
2012-01-08 20:59 ` [PATCH 3/3] S3C2443: add power domain for usb phy Heiko Stübner
2012-01-24  9:38   ` Felipe Balbi
2012-01-24  9:50     ` Heiko Stübner
2012-01-24  9:51       ` Felipe Balbi
2012-01-24 10:09         ` Heiko Stübner
2012-01-24 10:12           ` Felipe Balbi [this message]
2012-01-24 10:13         ` Heiko Stübner
2012-01-24 10:15           ` Felipe Balbi
2012-01-24 10:31             ` Heiko Stübner
2012-01-24 13:01               ` Kukjin Kim
2012-01-24 13:07                 ` Felipe Balbi
2012-01-24 13:27                   ` Heiko Stübner
2012-01-24 13:30                     ` Felipe Balbi
2012-02-01 16:35                 ` Heiko Stübner

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=20120124101245.GG27414@legolas.emea.dhcp.ti.com \
    --to=balbi@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).