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/20241122-google-vkms-managed-v5-0-1ab60403e960@xxxxxxxxxxx/ Signed-off-by: Louis Chauvet <louis.chauvet@xxxxxxxxxxx> --- Changes in v2: - Rebased on drm-misc-next - Apply comments from Jose - Link to v1: https://lore.kernel.org/r/20240912-b4-vkms-allocated-v1-0-29abbaa14af9@xxxxxxxxxxx --- Louis Chauvet (4): drm/vkms: Switch to dynamic allocation for connector drm/vkms: Switch to dynamic allocation for encoder drm/vkms: Switch to dynamic allocation for CRTC drm/vkms: Rename vkms_output to vkms_crtc drivers/gpu/drm/vkms/vkms_composer.c | 30 +++++----- drivers/gpu/drm/vkms/vkms_crtc.c | 100 ++++++++++++++++++---------------- drivers/gpu/drm/vkms/vkms_drv.h | 21 ++++--- drivers/gpu/drm/vkms/vkms_output.c | 41 +++++++++----- drivers/gpu/drm/vkms/vkms_writeback.c | 25 +++++---- 5 files changed, 118 insertions(+), 99 deletions(-) --- base-commit: 98efdd02e220fea84c1491012d7292749a71faeb change-id: 20240909-b4-vkms-allocated-9f5508f4444a prerequisite-message-id: 20241122-google-vkms-managed-v5-0-1ab60403e960@xxxxxxxxxxx prerequisite-patch-id: b608594ad493a41000ee703792eac4b23f9e35dc prerequisite-patch-id: 5697aa87c44bbf3eda8a1ba424465dc792545d4c prerequisite-patch-id: 223d59c407ce28dacf3f563b5c0148d2398303f1 prerequisite-patch-id: 720b75b21d06ce3d3f060fb9238f7903834da0e1 prerequisite-patch-id: 30a1e033fa43241ca6a43006fd4f29f8e9217224 Best regards, -- Louis Chauvet <louis.chauvet@xxxxxxxxxxx>
