* eric miao <eric.y.miao@xxxxxxxxx> [080724 05:41]: > On Wed, Jul 16, 2008 at 11:22 PM, Tony Lindgren <tony@xxxxxxxxxxx> wrote: > > * Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx> [080716 12:41]: > >> On Wed, Jul 16, 2008 at 11:53:20AM +0300, Tony Lindgren wrote: > >> > This series contains the refreshed omap2 clock and powerdomain > >> > patches as some of the patches in this series have been already > >> > integrated. > >> > >> I think the clock and power domain patches need much more review. > >> They're introducing a couple of new management subsystems which may > >> be of interest to other SoCs, maybe even different architectures. > > > > Sure the power domain and clock domain code can be worked into > > something more generic once we've figured out what can be shared. > > > > This is, unfortunately, not so useful to PXA likely. Although there's > power domain and clock domain concepts in PXA silicon, the power > states of those domains are controlled in a integrated way along with > the power state of the whole chip, perhaps to reduce the software > complexity in software domain management, and mimics the ACPI > concepts to some extent. OK, thanks for looking through it. > I don't want to give an early conclusion, but I may look more into the > usage of these power domains and clock domains ( it's not merely > to setup the PRCM registers correctly, no? ) Well lots of it deals with the omap PRCM registers yeah. But maybe some of the domain manamgent code could be shared. Tony > > > I've posted these patches to LKML and linux-pm for other arch people to > > look at too. > > > > Regards, > > > > Tony > > > > ------------------------------------------------------------------- > > List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel > > FAQ: http://www.arm.linux.org.uk/mailinglists/faq.php > > Etiquette: http://www.arm.linux.org.uk/mailinglists/etiquette.php > > > > > > -- > Cheers > - eric -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
