[lkml]   [2018]   [Dec]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] drm/vc4: Allow fb modifiers early enough to fill IN_FORMATS property
Paul Kocialkowski <> writes:

> The KMS mode_config elements are currently configured in vc4_kms_load,
> that is called after all components are binded (component_bind_all).
> However, the CRTC component (for the Pixel Valve) needs to access the
> allow_fb_modifiers element at bind time, when initializing its planes
> through drm_universal_plane_init.
> This helpers checks allow_fb_modifiers to decide whether to fill the
> IN_FORMATS property. Because allow_fb_modifiers is still set to false
> at this point, the property is never filled and userspace cannot
> retrieve the combination of supported formats and modifiers.
> Fix this by setting allow_fb_modifiers right after calling
> drm_mode_config_init (which initializes the structure), before binding
> the components of the driver.

This makes me wonder if the flag could be removed and replaced with "did
non-NULL modifiers get supplied to plane init?" I think I've tripped
over this flag in other KMS hacking, too.
[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2018-12-28 00:36    [W:0.089 / U:2.860 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site