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);

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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to