On Tue, Apr 05, 2011 at 11:37 AM +0300, Felipe Balbi wrote: > On Tue, Apr 05, 2011 at 12:32:50PM +0300, Felipe Balbi wrote: > > From: Michael Fillinger <m-fillinger@xxxxxx> > > > > MCOP is an FPGA-based Silicon Validation platform > > which is used to test particular IPs inside OMAP > > before we have a real ASIC. > > > > Signed-off-by: Michael Fillinger <m-fillinger@xxxxxx> > > > > [ balbi@xxxxxx : few cleanups here an there and also > > removal of some unnecessary code. ] > > > > Signed-off-by: Felipe Balbi <balbi@xxxxxx> > > I should have RFCed this one, but bear with me for a minute. > > This is just the bare minimum board-file for MCOP, there's still a bunch > of changes needed to get it actually booting. The attached diff shows > many of them. > > Now, we don't want to send that patch upstream for obvious reasons and > we also don't want to add ifdefs to clock data files as that would break > multi-omap. What do you guys suggest ? How should we handle detection of > MCOP so that we choose correct HWMODs and clock data files for it ? > > I don't think Linus will like if we add yet another hwmod + clk data > file just for MCOP, so we need to re-use what's in tree. > > -- > Balbi What you need to know about the MCOP system, based on OMAP2420, is that there is no PRCM and no complex clock trees, or power management. There is just 1 main driver clock. As such the "clock tree" can be extremely simplified. Michael Texas Instruments France SA, 821 Avenue Jack Kilby, 06270 Villeneuve Loubet. 036 420 040 R.C.S Antibes. Capital de EUR 753.920 -- 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
