>> >> Before the introduction of the component framework I would have said this is >> the way to go. Now, I think bridges should register themselves as components, >> and the DRM master driver should use the component framework to get a >> reference to the bridges it needs. > Well, I have modified the bridge framework exactly the way Thierry wanted it > to be, I mean the same way the current panel framework is. > And, I don't think there is a problem with that. > What problem are you facing with current bridge implementation? > What is the advantage of using the component framework to register bridges? At this point I'd rather merge something that keep iterating out of tree, if this enables current hw to work and is better than what we have we should merge it, and if we can get interest in using the component framework then we should look at that as a separate problem. Dave. -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |