From: Louis Chauvet <louis.chauvet@bootlin.com>
To: "José Expósito" <jose.exposito89@gmail.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
Subject: Re: [PATCH 01/16] drm/vkms: Expose device creation and destruction
Date: Tue, 25 Feb 2025 12:02:03 +0100 [thread overview]
Message-ID: <Z72jKyYAamcd0d3s@louis-chauvet-laptop> (raw)
In-Reply-To: <20250218170808.9507-2-jose.exposito89@gmail.com>
On 18/02/25 - 18:07, José Expósito wrote:
> In preparation for configfs support, expose vkms_create() and
> vkms_destroy().
>
> Co-developed-by: Louis Chauvet <louis.chauvet@bootlin.com>
> Signed-off-by: Louis Chauvet <louis.chauvet@bootlin.com>
> Signed-off-by: José Expósito <jose.exposito89@gmail.com>
Hi José,
First, thanks a lot for this series! I am very happy to see this moving, I
hope we will merge it soon!
> ---
> drivers/gpu/drm/vkms/vkms_drv.c | 4 ++--
> drivers/gpu/drm/vkms/vkms_drv.h | 4 ++++
> 2 files changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/vkms/vkms_drv.c b/drivers/gpu/drm/vkms/vkms_drv.c
> index a24d1655f7b8..23817c7b997e 100644
> --- a/drivers/gpu/drm/vkms/vkms_drv.c
> +++ b/drivers/gpu/drm/vkms/vkms_drv.c
> @@ -146,7 +146,7 @@ static int vkms_modeset_init(struct vkms_device *vkmsdev)
> return vkms_output_init(vkmsdev);
> }
>
> -static int vkms_create(struct vkms_config *config)
> +int vkms_create(struct vkms_config *config)
> {
> int ret;
> struct platform_device *pdev;
> @@ -229,7 +229,7 @@ static int __init vkms_init(void)
> return 0;
> }
>
> -static void vkms_destroy(struct vkms_config *config)
> +void vkms_destroy(struct vkms_config *config)
> {
> struct platform_device *pdev;
>
> diff --git a/drivers/gpu/drm/vkms/vkms_drv.h b/drivers/gpu/drm/vkms/vkms_drv.h
> index a74a7fc3a056..0fe08cd0c461 100644
> --- a/drivers/gpu/drm/vkms/vkms_drv.h
> +++ b/drivers/gpu/drm/vkms/vkms_drv.h
> @@ -223,6 +223,10 @@ struct vkms_device {
> #define to_vkms_plane_state(target)\
> container_of(target, struct vkms_plane_state, base.base)
>
> +/* VKMS device */
> +int vkms_create(struct vkms_config *config);
> +void vkms_destroy(struct vkms_config *config);
Can we add some documentation?
/**
* vkms_create - Create a device from a configuration
* @config: Config used to configure the new device
*
* A pointer to the created vkms_device is stored in @config
* Returns 0 in case of success.
*/
/**
* vkms_destroy - Destroy a device
* @config: Config from which the device was created
*
* The device is completly removed, but the @config pointers remains valid
* and can be reused for new devices.
*/
With this kind of documentation:
Reviewed-by: Louis Chauvet <louis.chauvet@bootlin.com>
> +
> /**
> * vkms_crtc_init() - Initialize a CRTC for VKMS
> * @dev: DRM device associated with the VKMS buffer
> --
> 2.48.1
>
next prev parent reply other threads:[~2025-02-25 11:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 17:07 [PATCH 00/16] drm/vkms: Add configfs support José Expósito
2025-02-18 17:07 ` [PATCH 01/16] drm/vkms: Expose device creation and destruction José Expósito
2025-02-25 11:02 ` Louis Chauvet [this message]
2025-02-18 17:07 ` [PATCH 02/16] drm/vkms: Add and remove VKMS instances via configfs José Expósito
2025-02-25 11:02 ` Louis Chauvet
2025-02-18 17:07 ` [PATCH 03/16] drm/vkms: Allow to configure multiple planes " José Expósito
2025-02-25 11:01 ` Louis Chauvet
2025-02-25 11:02 ` Louis Chauvet
2025-02-18 17:07 ` [PATCH 04/16] drm/vkms: Allow to configure the plane type " José Expósito
2025-02-25 11:02 ` Louis Chauvet
2025-02-18 17:07 ` [PATCH 05/16] drm/vkms: Allow to configure multiple CRTCs " José Expósito
2025-02-25 11:02 ` Louis Chauvet
2025-02-18 17:07 ` [PATCH 06/16] drm/vkms: Allow to configure CRTC writeback support " José Expósito
2025-02-25 11:02 ` Louis Chauvet
2025-02-18 17:07 ` [PATCH 07/16] drm/vkms: Allow to attach planes and CRTCs " José Expósito
2025-02-18 17:08 ` [PATCH 08/16] drm/vkms: Allow to configure multiple encoders " José Expósito
2025-02-25 11:02 ` Louis Chauvet
2025-02-18 17:08 ` [PATCH 09/16] drm/vkms: Allow to attach encoders and CRTCs " José Expósito
2025-02-18 17:08 ` [PATCH 10/16] drm/vkms: Allow to configure multiple connectors " José Expósito
2025-02-25 11:02 ` Louis Chauvet
2025-02-18 17:08 ` [PATCH 11/16] drm/vkms: Allow to attach connectors and encoders " José Expósito
2025-02-18 17:08 ` [PATCH 12/16] drm/vkms: Allow to configure connector status José Expósito
2025-02-18 17:08 ` [PATCH 13/16] drm/vkms: Allow to update the " José Expósito
2025-02-18 17:08 ` [PATCH 14/16] drm/vkms: Allow to configure connector status via configfs José Expósito
2025-02-18 17:08 ` [PATCH 15/16] drm/vkms: Allow to configure the default device creation José Expósito
2025-02-25 11:02 ` Louis Chauvet
2025-02-18 17:08 ` [PATCH 16/16] drm/vkms: Remove completed task from the TODO list José Expósito
2025-02-25 11:01 ` Louis Chauvet
2025-02-25 11:01 ` [PATCH 00/16] drm/vkms: Add configfs support Louis Chauvet
2025-02-25 17:56 ` José Expósito
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=Z72jKyYAamcd0d3s@louis-chauvet-laptop \
--to=louis.chauvet@bootlin.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamohammed.sa@gmail.com \
--cc=jose.exposito89@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®