On Fri, Jul 13, 2018 at 04:10:58PM +0100, Alexandru Gheorghe wrote: > During iteration process one of the proposed mechanism for not > breaking existing userspace was to report writeback connectors as > disconnected, however the final version used > DRM_CLIENT_CAP_WRITEBACK_CONNECTORS for that purpose. > > Signed-off-by: Alexandru Gheorghe <alexandru-cosmin.gheorghe@xxxxxxx> Reviewed-by: Sean Paul <seanpaul@xxxxxxxxxxxx> > --- > drivers/gpu/drm/drm_writeback.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/drivers/gpu/drm/drm_writeback.c b/drivers/gpu/drm/drm_writeback.c > index 8273950..e7b6e5e 100644 > --- a/drivers/gpu/drm/drm_writeback.c > +++ b/drivers/gpu/drm/drm_writeback.c > @@ -23,8 +23,8 @@ > * from a CRTC to a memory buffer. They are used and act similarly to other > * types of connectors, with some important differences: > * - Writeback connectors don't provide a way to output visually to the user. > - * - Writeback connectors should always report as "disconnected" (so that > - * clients which don't understand them will ignore them). > + * - Writeback connectors are visible to userspace only when the client sets > + * DRM_CLIENT_CAP_WRITEBACK_CONNECTORS. > * - Writeback connectors don't have EDID. > * > * A framebuffer may only be attached to a writeback connector when the > -- > 2.7.4 > -- Sean Paul, Software Engineer, Google / Chromium OS _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
