Hi Benoit,
The main motivation is that it's a driver and thus does not have anything to do inside mach-omap2.
Right, I understood that. mach-omap2 is not suitable for full fledged drivers.
Where will you put that otherwise?
Couple of suggestions: drivers/platform/omap/avs? drivers/misc/omap/avs? I prefer first one.
IIRC, David Brownell was referring to the rule of three for such case. Meaning that it worth having a generic fmwk when at least three different drivers are doing the same kind of things.
Yes, I remember that rule, but that's not stopping us to create a fwk, may be others will rise once they see the framework and contribute
if their h/w architecture requirements are not addressed? ---Trilok Soni -- -- Sent by a consultant of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum. -- 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
