drm/v3d: Add support for V3D v4.2.
No compatible string for it yet, just the version-dependent changes. They've now tied the hub and the core interrupt lines into a single interrupt line coming out of the block. It also turns out I made a mistake in modeling the V3D v3.3 and v4.1 bridge as a part of V3D itself -- the bridge is going away in favor of an external reset controller in a larger HW module. v2: Use consistent checks for whether we're on 4.2, and fix a leak in an error path. v3: Use more general means of determining if the current 4.2 changes are in place, as apparently other platforms may switch back (noted by Dave). Update the binding doc. v4: Improve error handling for IRQ init. Signed-off-by:Eric Anholt <eric@anholt.net> Link: https://patchwork.freedesktop.org/patch/msgid/20190308174336.7866-2-eric@anholt.net Reviewed-by:
Dave Emett <david.emett@broadcom.com>
Showing
- Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.txt 8 additions, 3 deletionsDocumentation/devicetree/bindings/gpu/brcm,bcm-v3d.txt
- drivers/gpu/drm/v3d/v3d_drv.c 17 additions, 4 deletionsdrivers/gpu/drm/v3d/v3d_drv.c
- drivers/gpu/drm/v3d/v3d_drv.h 2 additions, 0 deletionsdrivers/gpu/drm/v3d/v3d_drv.h
- drivers/gpu/drm/v3d/v3d_gem.c 11 additions, 1 deletiondrivers/gpu/drm/v3d/v3d_gem.c
- drivers/gpu/drm/v3d/v3d_irq.c 33 additions, 12 deletionsdrivers/gpu/drm/v3d/v3d_irq.c
Loading
Please register or sign in to comment