[PATCH v2] ARM: S3C64XX: Implement basic power domain support

[Rafael J. Wysocki]

On Friday, December 09, 2011, Kukjin Kim wrote:
> 
> > -----Original Message-----
> > From: Rafael J. Wysocki [mailto:rjw at sisk.pl]
> > Sent: Friday, December 09, 2011 7:55 AM
> > To: Mark Brown
> > Cc: Kukjin Kim; linux-arm-kernel at lists.infradead.org; linux-samsung-
> > soc at vger.kernel.org
> > Subject: Re: [PATCH v2] ARM: S3C64XX: Implement basic power domain support
> > 
> > On Thursday, December 08, 2011, Mark Brown wrote:
> > > The S3C64xx SoCs contain a set of gateable power domains which can be
> > > enabled and disabled at runtime in order to save power.  Use the generic
> > > power domain code to implement support for these in software, enabling
> > > runtime control of most domains:
> > >
> > >  - ETM (not supported in mainline).
> > >  - Domain G: 3D acceleration (no mainline support).
> > >  - Domain V: MFC (no mainline support).
> > >  - Domain I: JPEG and camera interface (no mainline support).
> > >  - Domain P: 2D acceleration, TV encoder and scaler (no mainline
> support)
> > >  - Domain S: Security (no mainline support).
> > >  - Domain F: LCD (driver already uses runtime PM), post processing and
> > >    rotation (no mainline support).
> > >
> > > The IROM domain is marked as always enabled as we should arrange for it
> > > to be enabled when we suspend which will need a bit more work.
> > >
> > > Due to all the conditional device registration that the platform does
> > > wrap s3c_pm_init() with s3c64xx_pm_init() which actually puts the device
> > > into the power domain after the machines have registered, looking for
> > > platform data to tell if the device was registered. Since currently only
> > > Cragganmore actually sets up PM that is the only machine updated.
> > >
> > > Signed-off-by: Mark Brown <broonie at opensource.wolfsonmicro.com>
> > > Acked-by: Kukjin Kim <kgene.kim at samsung.com>
> > 
> > Applied to linux-pm/linux-next.
> > 
> Hi Rafael,
> 
> As I said, I need topic branch for merging into my tree to avoid conflicts,
> but I couldn't find any branch for this.

And as I said, I'll put those patches into the pm-domains branch of my tree
shortly (most likely later today), which I think is the topic branch you need.

Thanks,
Rafael