On Fri, 2011-04-08 at 10:50 -0600, Paul Walmsley wrote: > Hi Tomi, > > On Mon, 4 Apr 2011, Tomi Valkeinen wrote: > > Not directly related, but something I've been wondering about is how to > > abstract the DSI/HDMI PLLs in DSS. What do you think, would it be > > possible/worth it to create struct clks for the clocks coming out of > > those PLLs? These would, of course, be DSS internal clks. I'm not very > > familiar with the clock framework, so I don't really have any idea what > > this would require and what would be the pros and cons. > > Yes, I think it would be good to try to implement the entire DSS clock > tree in the clock framework. One change to the clock code that we know > we'll need is to put a hwmod pointer in the struct clk which tells the > clock code that the hwmod needs to be enabled in order to access the > clock's registers. Right now, the clock code assumes that all of the > clock registers are accessible, all of the time. It's not quite that simple, as DSI PLL also needs the vdds_dsi regulator to be enabled... And to use DSI PLL, not only do you need to access DSI PLL registers, you also need to use DSI registers. Is it possible to have the driver create its own clock structs when it's loaded, and have the code for that clock inside the driver, or are clocks something that has to be handled in the core platform code? Tomi -- 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
