From: Daniel Vetter <daniel@ffwll.ch>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: Deepak Sharma <deepak.sharma@amd.com>,
Haneen Mohammed <hamohammed.sa@gmail.com>,
Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com>,
Maxime Ripard <maxime.ripard@bootlin.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
dri-devel@lists.freedesktop.org, Sean Paul <sean@poorly.run>
Subject: Re: [PATCH] drm/vkms: provide a parent device to drm_dev_init()
Date: Fri, 26 Oct 2018 12:26:58 +0200 [thread overview]
Message-ID: <20181026102658.GI21967@phenom.ffwll.local> (raw)
In-Reply-To: <20181026100550.625-1-emil.l.velikov@gmail.com>
On Fri, Oct 26, 2018 at 11:05:50AM +0100, Emil Velikov wrote:
> From: Emil Velikov <emil.velikov@collabora.com>
>
> Earlier commit updated the vgem driver to improve the topology, by
> passing a platform device as parent to drm_dev_init(). Shortly
> afterwords we updated the core function to BUG() in order to catch any
> buggy drivers passing NULL as parent.
>
> While I missed the vkms driver (as the patch predates vkms by a few
> months), the BUG caught the issue within couple of hours.
>
> Swap the drm_dev_init <> platform_device_register_simple order, to
> the driver back to life.
>
> Fixes: f08877e79485 ("drm: BUG_ON if passing NULL parent to drm_dev_init")
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Cc: Deepak Sharma <deepak.sharma@amd.com>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Cc: Maxime Ripard <maxime.ripard@bootlin.com>
> Cc: Sean Paul <sean@poorly.run>
> Cc: Haneen Mohammed <hamohammed.sa@gmail.com>
> Cc: Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com>
> Reported-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> Signed-off-by: Emil Velikov <emil.velikov@collabora.com>
> ---
> Rodrigo, Haneen, my plan is to push the patch to the drm-misc tree. An
> Ack/Rb will be appreciated.
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
btw just read through this stuff again, and noticed how vgem is using
drm_gem_prime_import_dev(). I think now that your patches have landed we
could get rid of that?
-Daniel
>
> Thanks
> Emil
> ---
> drivers/gpu/drm/vkms/vkms_drv.c | 21 +++++++++++----------
> 1 file changed, 11 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/gpu/drm/vkms/vkms_drv.c b/drivers/gpu/drm/vkms/vkms_drv.c
> index 07cfde1b4132..a3d57e0f5ee5 100644
> --- a/drivers/gpu/drm/vkms/vkms_drv.c
> +++ b/drivers/gpu/drm/vkms/vkms_drv.c
> @@ -108,17 +108,18 @@ static int __init vkms_init(void)
> if (!vkms_device)
> return -ENOMEM;
>
> - ret = drm_dev_init(&vkms_device->drm, &vkms_driver, NULL);
> - if (ret)
> - goto out_free;
> -
> vkms_device->platform =
> platform_device_register_simple(DRIVER_NAME, -1, NULL, 0);
> if (IS_ERR(vkms_device->platform)) {
> ret = PTR_ERR(vkms_device->platform);
> - goto out_fini;
> + goto out_free;
> }
>
> + ret = drm_dev_init(&vkms_device->drm, &vkms_driver,
> + &vkms_device->platform->dev);
> + if (ret)
> + goto out_unregister;
> +
> vkms_device->drm.irq_enabled = true;
>
> ret = drm_vblank_init(&vkms_device->drm, 1);
> @@ -129,20 +130,20 @@ static int __init vkms_init(void)
>
> ret = vkms_modeset_init(vkms_device);
> if (ret)
> - goto out_unregister;
> + goto out_fini;
>
> ret = drm_dev_register(&vkms_device->drm, 0);
> if (ret)
> - goto out_unregister;
> + goto out_fini;
>
> return 0;
>
> -out_unregister:
> - platform_device_unregister(vkms_device->platform);
> -
> out_fini:
> drm_dev_fini(&vkms_device->drm);
>
> +out_unregister:
> + platform_device_unregister(vkms_device->platform);
> +
> out_free:
> kfree(vkms_device);
> return ret;
> --
> 2.19.1
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-10-26 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 10:05 [PATCH] drm/vkms: provide a parent device to drm_dev_init() Emil Velikov
2018-10-26 10:26 ` Daniel Vetter [this message]
2018-10-29 11:24 ` Emil Velikov
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=20181026102658.GI21967@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=deepak.sharma@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=hamohammed.sa@gmail.com \
--cc=maxime.ripard@bootlin.com \
--cc=rodrigosiqueiramelo@gmail.com \
--cc=sean@poorly.run \
/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;
as well as URLs for NNTP newsgroup(s).