summaryrefslogtreecommitdiffstats
path: root/security
diff options
context:
space:
mode:
authorPaul Kocialkowski <paul.kocialkowski@bootlin.com>2019-01-04 09:56:10 +0100
committerMaxime Ripard <maxime.ripard@bootlin.com>2019-01-11 16:53:55 +0100
commit890880ddfdbe256083170866e49c87618b706ac7 (patch)
treeb87c2669e52ed882ccedc2dc98da5cc448f26998 /security
parentdrm/vc4: Limit SAND tiling support to semiplanar YUV420 formats (diff)
downloadlinux-890880ddfdbe256083170866e49c87618b706ac7.tar.xz
linux-890880ddfdbe256083170866e49c87618b706ac7.zip
drm: Auto-set allow_fb_modifiers when given modifiers at plane init
When drivers pass non-empty lists of modifiers for initializing their planes, we can infer that they allow framebuffer modifiers and set the driver's allow_fb_modifiers mode config element. In case the allow_fb_modifiers element was not set (some drivers tend to set them after registering planes), the modifiers will still be registered but won't be available to userspace unless the flag is set later. However in that case, the IN_FORMATS blob won't be created. In order to avoid this case and generally reduce the trouble associated with the flag, always set allow_fb_modifiers when a non-empty list of format modifiers is passed at plane init. Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch> Signed-off-by: Paul Kocialkowski <paul.kocialkowski@bootlin.com> Signed-off-by: Maxime Ripard <maxime.ripard@bootlin.com> Link: https://patchwork.freedesktop.org/patch/msgid/20190104085610.5829-1-paul.kocialkowski@bootlin.com
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions