On Thu, Dec 8, 2011 at 9:26 PM, Paul Walmsley <paul@xxxxxxxxx> wrote: > On Sun, 14 Aug 2011, Felipe Contreras wrote: >> On Wed, Mar 25, 2009 at 7:54 PM, Kevin Hilman >> <khilman@xxxxxxxxxxxxxxxxxxx> wrote: >> > Paul Walmsley <paul@xxxxxxxxx> writes: >> >> This series allows core code and driver code to register for >> >> notification when a clock's rate or parent changes. This is currently >> >> used by driver code that must be notified whenever power management >> >> code (e.g., CPUFreq) causes system rate changes that affect the driver's >> >> clock. >> > >> > I will be re-basing the PM branch onto today's linux-omap HEAD which >> > is v2.6.29 based. As I do this, I'll be dropping all the previous >> > notifier patches and replacing them with this series. >> >> What happened to this series? I don't see it anywhere. > > Unforunately It got postponed for a long time for a variety of reasons. > The good news is that it seems that others are starting to realize that > something like this is needed, so hopefully it will finally go in as > part of the common clock stuff. Cool. > Just out of curiosity: you are interested in them from the DSPBridge > perspective? Or do you have another use-case in mind? I ported the latest tidspbridge to the N9 kernel, and I was hit by a bug, but it was only triggered in that kernel because of this patch. So I was wondering why it never made it to mainline. That's all :) -- Felipe Contreras -- 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
