[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPj87rP0HZzdVoH18O6gVe1n8cHjhNn2LFSAAVvqj5m6tN2y_w@mail.gmail.com>
Date: Wed, 14 Aug 2024 10:10:39 +0100
From: Daniel Stone <daniel@...ishbar.org>
To: José Expósito <jose.exposito89@...il.com>
Cc: rodrigosiqueiramelo@...il.com, melissa.srw@...il.com,
mairacanal@...eup.net, hamohammed.sa@...il.com, daniel@...ll.ch,
maarten.lankhorst@...ux.intel.com, mripard@...nel.org, tzimmermann@...e.de,
airlied@...il.com, dri-devel@...ts.freedesktop.org,
linux-kernel@...r.kernel.org, louis.chauvet@...tlin.com
Subject: Re: [RFC PATCH 00/17] VKMS: Add configfs support
Hi José,
On Tue, 13 Aug 2024 at 11:51, José Expósito <jose.exposito89@...il.com> wrote:
> - When a CRTC is added and removed before device creation, there
> is a vblank warning.
> The issue is caused because vblanks are referenced using the
> CRTC index but, because one of the CRTCs is removed, the
> indices are not consecutives and drm_crtc_vblank_crtc() tries to
> access and invalid index
> I'm not sure if CRTC's indices *must* start at 0 and be
> consecutives or if this is a bug in the drm_crtc_vblank_crtc()
> implementation.
CRTCs and planes are not hotpluggable. I recommend you just create a
lot of each of them statically at startup, and hotplug only
connectors.
Cheers,
Daniel
Powered by blists - more mailing lists