From: Paul Kocialkowski Date: Thu, 16 May 2019 14:55:42 +0000 (+0200) Subject: drm/vc4: Check for V3D before binner bo alloc X-Git-Tag: v5.4-rc1~498^2~30^2~4 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=65f50f9761343d3dcc580db8e36e05d321d7e980;p=platform%2Fkernel%2Flinux-rpi.git drm/vc4: Check for V3D before binner bo alloc Check that we have a V3D device registered before attempting to allocate a binner buffer object. Signed-off-by: Paul Kocialkowski Reviewed-by: Eric Anholt Link: https://patchwork.freedesktop.org/patch/msgid/20190516145544.29051-3-paul.kocialkowski@bootlin.com --- diff --git a/drivers/gpu/drm/vc4/vc4_v3d.c b/drivers/gpu/drm/vc4/vc4_v3d.c index 7c49010..c16db46 100644 --- a/drivers/gpu/drm/vc4/vc4_v3d.c +++ b/drivers/gpu/drm/vc4/vc4_v3d.c @@ -241,6 +241,9 @@ static int bin_bo_alloc(struct vc4_dev *vc4) int ret = 0; struct list_head list; + if (!v3d) + return -ENODEV; + /* We may need to try allocating more than once to get a BO * that doesn't cross 256MB. Track the ones we've allocated * that failed so far, so that we can free them when we've got