drm: rcar-du: Clarify vsp dependency
authorArnd Bergmann <arnd@arndb.de>
Fri, 26 Feb 2016 11:52:20 +0000 (12:52 +0100)
committerLaurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Sat, 23 Apr 2016 23:53:35 +0000 (02:53 +0300)
commit4f5504cfc6ffcc73926de454f000d0409eed2fcb
treea3fd07fb0380c354e9376b68a065579b68be98c6
parent027b3f8ba9277410c3191d72d1ed2c6146d8a668
drm: rcar-du: Clarify vsp dependency

The VSP1 compositor code in DRM links against the respective V4L
driver, but the dependency is not expressed correctly in Kconfig,
which leads to a build error when the DRM driver is built-in
and the V4L driver is a module:

drivers/gpu/built-in.o: In function `rcar_du_vsp_plane_atomic_update':
rcar-du/rcar_du_vsp.c:183: undefined reference to `vsp1_du_atomic_update'

This patch avoids the problem by ensuring that the DRM VSP code can
only be enabled if the V4L driver is linked into the kernel, or
both are loadable modules.

Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Fixes: 6d62ef3ac30b ("drm: rcar-du: Expose the VSP1 compositor through KMS planes")
Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
drivers/gpu/drm/rcar-du/Kconfig
This page took 0.025136 seconds and 5 git commands to generate.