>-----Original Message----- >From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of Mike >Chan >Sent: Tuesday, July 28, 2009 8:49 PM >To: Kevin Hilman; linux-omap@xxxxxxxxxxxxxxx >Subject: drivers that require headers in mach-omap > >Omap folks, how are drivers that require access to prm and cm >registers via cm_read_mod_reg() etc... suppose to access these? > >For example if drivers/usb/host/ohci-omap.c wanted to call: >cm_read_mod_reg(OMAP3430ES2_USBHOST_MOD, CM_IDLEST); The design was supposed to encapsulate the PRCM API's from drivers. Driver has control over the iclk and fclk and the clock framework would take care of any CM/PRM register settings. Accessing these registers in drivers would make the driver non-compatible for non-omap platforms. > >It seems some of the headers in mach-omap2 should be in >plat-omap/include/mach, or is there a more elegant way? The other >alternatives are to register calls in all the board files, or #include >../../.. both do not seem very elegant to me. > >-- Mike >-- >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 -- 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
