From: "José Expósito" <jose.exposito89@gmail.com>
To: louis.chauvet@bootlin.com
Cc: airlied@gmail.com, arthurgrillo@riseup.net, daniel@ffwll.ch,
dri-devel@lists.freedesktop.org, hamohammed.sa@gmail.com,
jeremie.dautheribes@bootlin.com, linux-kernel@vger.kernel.org,
maarten.lankhorst@linux.intel.com, mairacanal@riseup.net,
melissa.srw@gmail.com, miquel.raynal@bootlin.com,
mripard@kernel.org, nicolejadeyee@google.com,
rodrigosiqueiramelo@gmail.com, seanpaul@google.com,
thomas.petazzoni@bootlin.com, tzimmermann@suse.de,
"José Expósito" <jose.exposito89@gmail.com>
Subject: [PATCH RFC 2/4] drm/vkms: Switch to managed for encoder
Date: Tue, 20 Aug 2024 11:09:27 +0200 [thread overview]
Message-ID: <20240820090930.2869-1-jose.exposito89@gmail.com> (raw)
In-Reply-To: <20240814-google-vkms-managed-v1-2-7ab8b8921103@bootlin.com>
> The current VKMS driver uses non-managed function to create encoders. It
> is not an issue yet, but in order to support multiple devices easly,
s/easly/easily
> convert this code to use drm and device managed helpers.
>
> Signed-off-by: Louis Chauvet <louis.chauvet@bootlin.com>
Reviewed-by: José Expósito <jose.exposito89@gmail.com>
> ---
> drivers/gpu/drm/vkms/vkms_drv.h | 1 -
> drivers/gpu/drm/vkms/vkms_output.c | 21 +++++++++------------
> 2 files changed, 9 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/gpu/drm/vkms/vkms_drv.h b/drivers/gpu/drm/vkms/vkms_drv.h
> index cea7b2640c5d..2c9d1f20ce84 100644
> --- a/drivers/gpu/drm/vkms/vkms_drv.h
> +++ b/drivers/gpu/drm/vkms/vkms_drv.h
> @@ -42,7 +42,6 @@
> */
> struct vkms_output {
> struct drm_crtc crtc;
> - struct drm_encoder encoder;
> struct drm_writeback_connector wb_connector;
> struct hrtimer vblank_hrtimer;
> ktime_t period_ns;
> diff --git a/drivers/gpu/drm/vkms/vkms_output.c b/drivers/gpu/drm/vkms/vkms_output.c
> index 4767838c3a73..cb8507917b5f 100644
> --- a/drivers/gpu/drm/vkms/vkms_output.c
> +++ b/drivers/gpu/drm/vkms/vkms_output.c
> @@ -16,9 +16,7 @@ static const struct drm_connector_funcs vkms_connector_funcs = {
> .atomic_destroy_state = drm_atomic_helper_connector_destroy_state,
> };
>
> -static const struct drm_encoder_funcs vkms_encoder_funcs = {
> - .destroy = drm_encoder_cleanup,
> -};
> +static const struct drm_encoder_funcs vkms_encoder_funcs = {};
This struct is not required, drmm_encoder_init() can take a NULL value.
>
> static int vkms_conn_get_modes(struct drm_connector *connector)
> {
> @@ -55,7 +53,7 @@ int vkms_output_init(struct vkms_device *vkmsdev, int possible_crtc_index)
> struct vkms_output *output = &vkmsdev->output;
> struct drm_device *dev = &vkmsdev->drm;
> struct drm_connector *connector;
> - struct drm_encoder *encoder = &output->encoder;
> + struct drm_encoder *encoder;
> struct drm_crtc *crtc = &output->crtc;
> struct vkms_plane *primary, *cursor = NULL;
> int ret;
> @@ -103,8 +101,12 @@ int vkms_output_init(struct vkms_device *vkmsdev, int possible_crtc_index)
>
> drm_connector_helper_add(connector, &vkms_conn_helper_funcs);
>
> - ret = drm_encoder_init(dev, encoder, &vkms_encoder_funcs,
> - DRM_MODE_ENCODER_VIRTUAL, NULL);
> + encoder = drmm_kzalloc(&vkmsdev->drm, sizeof(*encoder), GFP_KERNEL);
&vkmsdev->drm => dev
> + if (!encoder)
The same here, we could log this error:
DRM_ERROR("Failed to allocate encoder\n");
> + return -ENOMEM;
> +
> + ret = drmm_encoder_init(dev, encoder, &vkms_encoder_funcs,
vkms_encoder_funcs can be NULL.
> + DRM_MODE_ENCODER_VIRTUAL, NULL);
> if (ret) {
> DRM_ERROR("Failed to init encoder\n");
> return ret;
> @@ -118,7 +120,7 @@ int vkms_output_init(struct vkms_device *vkmsdev, int possible_crtc_index)
> ret = drm_connector_attach_encoder(connector, encoder);
> if (ret) {
> DRM_ERROR("Failed to attach connector to encoder\n");
> - goto err_attach;
> + return ret;
> }
>
> if (vkmsdev->config->writeback) {
> @@ -130,9 +132,4 @@ int vkms_output_init(struct vkms_device *vkmsdev, int possible_crtc_index)
> drm_mode_config_reset(dev);
>
> return 0;
> -
> -err_attach:
> - drm_encoder_cleanup(encoder);
> -
> - return ret;
> }
next prev parent reply other threads:[~2024-08-20 9:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 10:06 [PATCH RFC 0/4] drm/vkms: Switch all vkms object to DRM managed objects Louis Chauvet
2024-08-14 10:06 ` [PATCH RFC 1/4] drm/vkms: Switch to managed for connector Louis Chauvet
2024-08-20 9:09 ` José Expósito
2024-08-20 10:03 ` Maíra Canal
2024-08-26 16:24 ` Louis Chauvet
2024-08-14 10:06 ` [PATCH RFC 2/4] drm/vkms: Switch to managed for encoder Louis Chauvet
2024-08-20 9:09 ` José Expósito [this message]
2024-08-26 16:24 ` Louis Chauvet
2024-08-14 10:06 ` [PATCH RFC 3/4] drm/vkms: Switch to managed for crtc Louis Chauvet
2024-08-20 9:09 ` José Expósito
2024-08-26 16:24 ` Louis Chauvet
2024-08-14 10:06 ` [PATCH RFC 4/4] drm/vkms: Rename all vkms_crtc instance to be consistent Louis Chauvet
2024-08-20 9:10 ` [PATCH RFC 4/4] drm/vkms: Rename all vkms_crtc instance to be 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=20240820090930.2869-1-jose.exposito89@gmail.com \
--to=jose.exposito89@gmail.com \
--cc=airlied@gmail.com \
--cc=arthurgrillo@riseup.net \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamohammed.sa@gmail.com \
--cc=jeremie.dautheribes@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=louis.chauvet@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mairacanal@riseup.net \
--cc=melissa.srw@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=mripard@kernel.org \
--cc=nicolejadeyee@google.com \
--cc=rodrigosiqueiramelo@gmail.com \
--cc=seanpaul@google.com \
--cc=thomas.petazzoni@bootlin.com \
--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®