diff options
| author | Arnd Bergmann <[email protected]> | 2016-02-26 12:52:20 +0100 |
|---|---|---|
| committer | Laurent Pinchart <[email protected]> | 2016-04-24 02:53:35 +0300 |
| commit | 4f5504cfc6ffcc73926de454f000d0409eed2fcb (patch) | |
| tree | a3fd07fb0380c354e9376b68a065579b68be98c6 /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | 027b3f8ba9277410c3191d72d1ed2c6146d8a668 (diff) | |
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 <[email protected]>
Fixes: 6d62ef3ac30b ("drm: rcar-du: Expose the VSP1 compositor through KMS planes")
Signed-off-by: Laurent Pinchart <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions