Hi Tony, On Monday 21 January 2013 09:18:12 Tony Lindgren wrote: > * Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx> [130121 05:37]: > > On Monday 14 January 2013 17:10:15 Mike Turquette wrote: > > > Quoting Laurent Pinchart (2013-01-08 05:43:52) > > > > > > > Hello, > > > > > > > > Now that the OMAP3 supports the common clock framework, clock rate > > > > back-propagation is available for the ISP clocks. Instead of setting > > > > the cam_mclk parent clock rate to control the cam_mclk clock rate, we > > > > can mark the dpll4_m5x2_ck_3630 and cam_mclk clocks as supporting > > > > back-propagation, and set the cam_mclk rate directly. This simplifies > > > > the ISP clocks configuration. > > > > > > I'm pleased to see this feature get used on OMAP. Plus your driver gets > > > a negative diffstat :) > > > > > > Reviewed-by: Mike Turquette <mturquette@xxxxxxxxxx> > > > > Thanks. > > > > Would you like to take the arch/ patch in your tree, or should I push it > > through the linux-media tree along with the omap3isp patch ? > > The arch/arm/*omap* clock changes need to be queued by Paul to avoid > potential stupid merge conflicts when the clock data gets moved to > live under drivers/clk/omap. OK. The omap3isp patch can go through Paul's tree as well, it won't conflict with other changes to the driver in this merge window. Paul, can you take both patches together ? If so I'll send you a pull request. -- Regards, Laurent Pinchart -- 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
