Specific allocations for each DRM object is not strictly needed in VKMS right now, but in order to implement dynamic configuration of VKMS (configFS), it will be easier to have one allocation per DRM object. There is no need for a dynamic allocation for the writeback connector as there can only be one per CRTC No functionnal changes are intented in this series. This series requires [1] to switch vkms objects to drm-managed objects. [1]: https://lore.kernel.org/all/20240912-google-vkms-managed-v3-0-7708d6ad262d@xxxxxxxxxxx/ Signed-off-by: Louis Chauvet <louis.chauvet@xxxxxxxxxxx> --- Louis Chauvet (3): drm/vkms: Switch to dynamic allocation for connector drm/vkms: Switch to dynamic allocation for encoder drm/vkms: Switch to dynamic allocation for CRTC drivers/gpu/drm/vkms/vkms_crtc.c | 28 +++++++++++--------- drivers/gpu/drm/vkms/vkms_drv.h | 11 ++++---- drivers/gpu/drm/vkms/vkms_output.c | 48 ++++++++++++++++++++++------------- drivers/gpu/drm/vkms/vkms_writeback.c | 17 +++++++------ 4 files changed, 61 insertions(+), 43 deletions(-) --- base-commit: d2194256049910d286cd6c308c2689df521d8842 change-id: 20240909-b4-vkms-allocated-9f5508f4444a prerequisite-message-id: <20240906-writeback-drmm-v1-1-01ede328182c@xxxxxxxxxxx> prerequisite-patch-id: 93bfa5c36385932ea291789faa7356639d9e4bfc prerequisite-message-id: <20240906-vkms-remove-index-v1-1-3cfedd8ccb2f@xxxxxxxxxxx> prerequisite-patch-id: 130816a16434cafa13b7a2b629398a20782be3a6 prerequisite-message-id: 20240912-google-vkms-managed-v3-0-7708d6ad262d@xxxxxxxxxxx prerequisite-patch-id: ec4384a6e16b63691ccc54a71d304722e33443bc prerequisite-patch-id: 4c4bbad8522d8184fb3e6695a98fdf34c2bf784c prerequisite-patch-id: 05df4db485c1454c432e776421b056e3a9c51d7e prerequisite-patch-id: 30a1e033fa43241ca6a43006fd4f29f8e9217224 Best regards, -- Louis Chauvet <louis.chauvet@xxxxxxxxxxx>
