On Mon, 12 Jul 2010, Thomas Petazzoni wrote: > I know this structure already exists, but do we really need a new > structure for this ? Couldn't these infos (OPP list, set/get rate > methods) be stored in an existing device-specific structure (omap_hwmod > for hardware-related things are omap_device for ~software-related > things) ? > > For example, why aren't OPPs attached to the hwmod description of the > particular device ? These OPPs definitions really look like a > characteristic of a particular IP, don't they ? hwmod data is intended to be used for RTL-level data, e.g., data that is invariant of the underlying process technology. OPP data can vary by the underlying fabrication process or per-die speed validation (e.g., speed-binning). So I don't think it belongs in the hwmod data. - 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
