01.05.2014 23:51, Felipe Balbi пишет:
I don't think you need that. Have tusb_get_revision() run only one during tusb6010 probe/init function and cache the returned value inside musb->revision or something like that, then remove all other calls to tusb_get_revision() and have tusb6010_omap.c check revision using if (musb->revision >= TUSB_REV30) and your problem is solved.
Do you think that it is possible to add another tusb6010-specific field to struct musb, which seems to be general interface?
-- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
