drm/vc4: Disable V3D interactions if the v3d component didn't probe.
authorEric Anholt <eric@anholt.net>
Mon, 1 Apr 2019 18:35:59 +0000 (11:35 -0700)
committerEric Anholt <eric@anholt.net>
Wed, 3 Apr 2019 19:49:18 +0000 (12:49 -0700)
commitffc26740714962e3e8801dca7ef32b636b3781db
treefa69c90e11ee7b36c6497e8d7612ed1440ce4c62
parentc9be804c8c7a2d3fcd8e236407c8623be0356a01
drm/vc4: Disable V3D interactions if the v3d component didn't probe.

One might want to use the VC4 display stack without using Mesa.
Similar to the debugfs fixes for not having all of the possible
display bits enabled, make sure you can't oops in vc4 if v3d isn't
enabled.

v2: Fix matching against other v3d variants (review by Paul), don't
    forget to set irq_enabled so that the vblank uapi works
v3: Use -ENODEV instead of -EINVAL on Paul's suggestion.

Signed-off-by: Eric Anholt <eric@anholt.net>
Link: https://patchwork.freedesktop.org/patch/msgid/20190401183559.3823-2-eric@anholt.net
Reviewed-by: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
drivers/gpu/drm/vc4/vc4_drv.c
drivers/gpu/drm/vc4/vc4_drv.h
drivers/gpu/drm/vc4/vc4_gem.c
drivers/gpu/drm/vc4/vc4_irq.c
drivers/gpu/drm/vc4/vc4_kms.c
drivers/gpu/drm/vc4/vc4_perfmon.c
drivers/gpu/drm/vc4/vc4_v3d.c