Hi, The following patch fixes a wrong container_of usage for omap3630. All sub clock of dpll4 that do not use a reset value as divider are affected.
For instance CAM_MCLK is 216 MHz instead of the asked 172,8 MHz Any user of this clock is affected. This is the case for instance if CAM_XCLKA is used to provide clock for an external camera. Beyond wrong frequency setting, this is also a potential oops waiting to bite any omap3isp user, since a wrong pointer is dereferenced, and content of this pointer is used to do __raw_writel / __raw_readl. v2 : Follow Mike Turquette's comment and use clock framework instead of directly accessing register. Regards, Jean-Philippe François -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
