On Wed, 18 Apr 2012, Cousson, Benoit wrote: > But the model is already different for OMAP4. We're running both models at the same time in mainline for OMAP4, effectively. > Yeah, I'm just reluctant to add some more data in an already big file, > knowing that this information will be useless, just because a couple of > broken drivers does need that. > > What we plan to do with the migration to CCF is to keep these specific > nodes only for the broken drivers to highlight that these ones need to > be fixed. And thus only these nodes will need the clkdm information. Sounds like after your series, we'll only take both approaches for the broken drivers, and then just do the hwmod clockdomain sequence for the majority? That sounds reasonable to me. We should probably log a warning for those cases too. regards, - 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
