RE: [PATCH] PM: Fixed clockdomain state control for OMAP3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello Tero,

On Tue, 23 Sep 2008, Tero.Kristo@xxxxxxxxx wrote:

> The access of element 0 only is not because we have only 1 clockdomain
> for each powerdomain, but because we only want to wake up some
> clockdomain
> to make the powerdomain come up. It does not matter which clockdomain is
> awakened, as long as one is, and I don't think it makes sense to wake
> all
> of them up because this would cause additional overhead.

Okay, that sounds fine.


- Paul
--
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

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux