On 2014-01-02 11:19, Archit Taneja wrote: > At the moment, the omapdrm driver doesn't work on panda/beagle when built-in > the kernel. The problem is that omapdrm doesn't defer probe if resources like > regulator/I2C etc are missing. The first patch fixes that. > > The next 3 patches make sure that omapdrm module can be inserted and removed > successively, and that omapdss is left in a consistent state when omapdrm is > removed. > > In the previous version of this series, there was a warning related to apply_irq > being registered seen while removing omapdrm. This was a relatively scary > warning, therefore, the "change dev_unload order" patch was added to make sure > we don't see that. > > After these fixes, I still see the warning below once in a while. I don't know > how to fix it at the moment, but it's harmless and omapdrm is now usable again. > These are critical fixes which I have posted since 3.12-rcs, it would be nice if > they can go in as soon as possible. These look ok to me: Reviewed-by: Tomi Valkeinen <tomi.valkeinen@xxxxxx> Tomi
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
