Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki On 13/10/17 17:58, Laurent Pinchart wrote: > Hello, > > This patch series merges the omapdrm and omapdss drivers into a single driver > called omapdrm. The split in two drivers was historical, in order to support So how do the loadtime and runtime dependencies go with this series? In the current mainline, it's kind of clear: We have omapdss, and the panel and encoder drivers register themselves to omapdss. So panels and encoders depend on omapdss. On top of that we have omapdrm which then uses both omapdss and panels. Unloading happens in reverse order. With only omapdrm, the panels and encoders must depend on that. But omapdrm will use the panels, so there's a runtime dependency that way. Do we need to use sysfs's unbind first to remove some drivers, before module unloading is possible? Which ones? Does it work? Tomi _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
