Stefan Schake <stschake@xxxxxxxxx> writes: > We were calling enable_irq on bind, where it was already enabled previously > by the IRQ helper. Additionally, dev->irq is not set correctly until after > postinstall and so was always zero here, triggering a warning in 4.15. > Fix both by moving the enable to the power management resume path, where we > know there was a previous disable invocation during suspend. > > Fixes: 253696ccd613 ("drm/vc4: Account for interrupts in flight") > Signed-off-by: Stefan Schake <stschake@xxxxxxxxx> > --- > I tested replacing the enable/disable dance with just synchronize_irq, > but that only made the original kernel OOPS more sporadic. Reviewed and applied. Thanks! Somewhere on the infinite TODO list is to stop using the DRM IRQ helpers and just install our IRQ handler on our own, which I think would have avoided this trouble.
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel