From: "José Expósito" <jose.exposito89@gmail.com>
To: louis.chauvet@bootlin.com
Cc: hamohammed.sa@gmail.com, simona@ffwll.ch, melissa.srw@gmail.com,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
"José Expósito" <jose.exposito89@gmail.com>
Subject: [PATCH v4 00/16] drm/vkms: Add configfs support
Date: Mon, 7 Apr 2025 10:14:09 +0200 [thread overview]
Message-ID: <20250407081425.6420-1-jose.exposito89@gmail.com> (raw)
Hi everyone,
This series allow to configure one or more VKMS instances without having
to reload the driver using configfs.
The series is structured in 3 blocks:
- Patches 1..11: Basic device configuration. For simplicity, I kept the
available options as minimal as possible.
- Patches 12 and 13: New option to skip the default device creation and to-do
cleanup.
- Patches 14, 15 and 16: Allow to hot-plug and unplug connectors. This is not
part of the minimal set of options, but I included in this series so it can
be used as a template/example of how new configurations can be added.
The process of configuring a VKMS device is documented in "vkms.rst".
Finally, the code is thoroughly tested by a collection of IGT tests [1].
Best wishes,
José Expósito
[1] https://lists.freedesktop.org/archives/igt-dev/2025-February/086071.html
Changes in v4:
- Since Louis and I worked on this together, set him as the author of some of
the patches and me as co-developed-by to reflect this joint effort.
- Rebased on top of drm-misc-next
- Link to v3: https://lore.kernel.org/all/20250307163353.5896-1-jose.exposito89@gmail.com/
Changes in v3:
- Applied review comments by Louis Chauvet: (thanks!!)
- Use scoped_guard() instead of guard(mutex)(...)
- Fix a use-after-free error in the connector hot-plug code
- Rebased on top of drm-misc-next
- Link to v2: https://lore.kernel.org/all/20250225175936.7223-1-jose.exposito89@gmail.com/
Changes in v2:
- Applied review comments by Louis Chauvet:
- Use guard(mutex)(...) instead of lock/unlock
- Return -EBUSY when trying to modify a enabled device
- Move the connector hot-plug related patches to the end
- Rebased on top of drm-misc-next
- Link to v1: https://lore.kernel.org/dri-devel/20250218170808.9507-1-jose.exposito89@gmail.com/T/
José Expósito (6):
drm/vkms: Expose device creation and destruction
drm/vkms: Allow to configure the default device creation
drm/vkms: Remove completed task from the TODO list
drm/vkms: Allow to configure connector status
drm/vkms: Allow to update the connector status
drm/vkms: Allow to configure connector status via configfs
Louis Chauvet (10):
drm/vkms: Add and remove VKMS instances via configfs
drm/vkms: Allow to configure multiple planes via configfs
drm/vkms: Allow to configure the plane type via configfs
drm/vkms: Allow to configure multiple CRTCs via configfs
drm/vkms: Allow to configure CRTC writeback support via configfs
drm/vkms: Allow to attach planes and CRTCs via configfs
drm/vkms: Allow to configure multiple encoders via configfs
drm/vkms: Allow to attach encoders and CRTCs via configfs
drm/vkms: Allow to configure multiple connectors via configfs
drm/vkms: Allow to attach connectors and encoders via configfs
Documentation/gpu/vkms.rst | 100 ++-
drivers/gpu/drm/vkms/Kconfig | 1 +
drivers/gpu/drm/vkms/Makefile | 3 +-
drivers/gpu/drm/vkms/tests/vkms_config_test.c | 24 +
drivers/gpu/drm/vkms/vkms_config.c | 8 +-
drivers/gpu/drm/vkms/vkms_config.h | 26 +
drivers/gpu/drm/vkms/vkms_configfs.c | 833 ++++++++++++++++++
drivers/gpu/drm/vkms/vkms_configfs.h | 8 +
drivers/gpu/drm/vkms/vkms_connector.c | 35 +
drivers/gpu/drm/vkms/vkms_connector.h | 9 +
drivers/gpu/drm/vkms/vkms_drv.c | 18 +-
drivers/gpu/drm/vkms/vkms_drv.h | 20 +
12 files changed, 1072 insertions(+), 13 deletions(-)
create mode 100644 drivers/gpu/drm/vkms/vkms_configfs.c
create mode 100644 drivers/gpu/drm/vkms/vkms_configfs.h
base-commit: dd717762761807452ca25634652e180a80349cd8
--
2.48.1
next reply other threads:[~2025-04-07 8:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 8:14 José Expósito [this message]
2025-04-07 8:14 ` [PATCH v4 01/16] drm/vkms: Expose device creation and destruction José Expósito
2025-04-07 8:14 ` [PATCH v4 02/16] drm/vkms: Add and remove VKMS instances via configfs José Expósito
2025-04-07 8:14 ` [PATCH v4 03/16] drm/vkms: Allow to configure multiple planes " José Expósito
2025-04-07 8:14 ` [PATCH v4 04/16] drm/vkms: Allow to configure the plane type " José Expósito
2025-04-15 11:59 ` Louis Chauvet
2025-04-07 8:14 ` [PATCH v4 05/16] drm/vkms: Allow to configure multiple CRTCs " José Expósito
2025-04-15 12:11 ` Louis Chauvet
2025-04-07 8:14 ` [PATCH v4 06/16] drm/vkms: Allow to configure CRTC writeback support " José Expósito
2025-04-15 12:18 ` Louis Chauvet
2025-04-07 8:14 ` [PATCH v4 07/16] drm/vkms: Allow to attach planes and CRTCs " José Expósito
2025-04-15 12:24 ` Louis Chauvet
2025-04-07 8:14 ` [PATCH v4 08/16] drm/vkms: Allow to configure multiple encoders " José Expósito
2025-04-15 12:25 ` Louis Chauvet
2025-04-07 8:14 ` [PATCH v4 09/16] drm/vkms: Allow to attach encoders and CRTCs " José Expósito
2025-04-15 12:26 ` Louis Chauvet
2025-04-15 12:27 ` Louis Chauvet
2025-04-07 8:14 ` [PATCH v4 10/16] drm/vkms: Allow to configure multiple connectors " José Expósito
2025-04-15 12:37 ` Louis Chauvet
2025-04-07 8:14 ` [PATCH v4 11/16] drm/vkms: Allow to attach connectors and encoders " José Expósito
2025-04-15 12:27 ` Louis Chauvet
2025-04-07 8:14 ` [PATCH v4 12/16] drm/vkms: Allow to configure the default device creation José Expósito
2025-04-07 8:14 ` [PATCH v4 13/16] drm/vkms: Remove completed task from the TODO list José Expósito
2025-04-07 8:14 ` [PATCH v4 14/16] drm/vkms: Allow to configure connector status José Expósito
2025-04-15 12:47 ` Louis Chauvet
2025-04-07 8:14 ` [PATCH v4 15/16] drm/vkms: Allow to update the " José Expósito
2025-04-15 12:48 ` Louis Chauvet
2025-04-07 8:14 ` [PATCH v4 16/16] drm/vkms: Allow to configure connector status via configfs José Expósito
2025-04-15 12:53 ` Louis Chauvet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250407081425.6420-1-jose.exposito89@gmail.com \
--to=jose.exposito89@gmail.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamohammed.sa@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=louis.chauvet@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=melissa.srw@gmail.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox