From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 02/11] drm: Add a callback from connector registering
Date: Mon, 30 May 2016 10:49:43 +0200 [thread overview]
Message-ID: <20160530084943.GC27098@phenom.ffwll.local> (raw)
In-Reply-To: <1464357644-16775-3-git-send-email-chris@chris-wilson.co.uk>
On Fri, May 27, 2016 at 03:00:35PM +0100, Chris Wilson wrote:
> If a driver wants to more precisely control its initialisation and in
> particular, defer registering its interfaces with userspace until after
> everything is setup, it also needs to defer registering the connectors.
> As some devices need more work during registration, add a callback so
> that drivers can do additional work if required for a connector.
>
> Correspondingly, we also require an unregister callback.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Cc: dri-devel@lists.freedesktop.org
Smells a bit too much like midlayer too me ;-) Imo perfectly fine to have
a driver loop besides the register_all which registers stuff like
backlights and similar things. But otoh this is a bit a high-grade
bikeshed ...
-Daniel
> ---
> drivers/gpu/drm/drm_crtc.c | 18 ++++++++++++++++--
> include/drm/drm_crtc.h | 21 +++++++++++++++++++++
> 2 files changed, 37 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_crtc.c b/drivers/gpu/drm/drm_crtc.c
> index d2a6d958ca76..81641544ac3e 100644
> --- a/drivers/gpu/drm/drm_crtc.c
> +++ b/drivers/gpu/drm/drm_crtc.c
> @@ -1036,13 +1036,24 @@ int drm_connector_register(struct drm_connector *connector)
>
> ret = drm_debugfs_connector_add(connector);
> if (ret) {
> - drm_sysfs_connector_remove(connector);
> - return ret;
> + goto err_sysfs;
> + }
> +
> + if (connector->funcs->late_register) {
> + ret = connector->funcs->late_register(connector);
> + if (ret)
> + goto err_debugfs;
> }
>
> drm_mode_object_register(connector->dev, &connector->base);
>
> return 0;
> +
> +err_debugfs:
> + drm_debugfs_connector_remove(connector);
> +err_sysfs:
> + drm_sysfs_connector_remove(connector);
> + return ret;
> }
> EXPORT_SYMBOL(drm_connector_register);
>
> @@ -1054,6 +1065,9 @@ EXPORT_SYMBOL(drm_connector_register);
> */
> void drm_connector_unregister(struct drm_connector *connector)
> {
> + if (connector->funcs->early_unregister)
> + connector->funcs->early_unregister(connector);
> +
> drm_sysfs_connector_remove(connector);
> drm_debugfs_connector_remove(connector);
> }
> diff --git a/include/drm/drm_crtc.h b/include/drm/drm_crtc.h
> index d1559cd04e3d..0f7425444a44 100644
> --- a/include/drm/drm_crtc.h
> +++ b/include/drm/drm_crtc.h
> @@ -926,6 +926,27 @@ struct drm_connector_funcs {
> uint64_t val);
>
> /**
> + * @late_register:
> + *
> + * Register the connector with userspace, called from
> + * drm_connector_register. This should be called after driver
> + * load during its registration phase. All actions such as registering
> + * with auxiliary devices (such as drm_dp_aux_register) should be done
> + * during this callback.
> + */
> + int (*late_register)(struct drm_connector *connector);
> +
> + /**
> + * @early_unregister:
> + *
> + * Unregister the connector with userspace, called from
> + * drm_connector_unregister. This is called early in the driver
> + * unload sequence to disable userspace access before data
> + * structures are torndown.
> + */
> + void (*early_unregister)(struct drm_connector *connector);
> +
> + /**
> * @destroy:
> *
> * Clean up connector resources. This is called at driver unload time
> --
> 2.8.1
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-05-30 8:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 14:00 Reordering debugfs registration vs driver loading Chris Wilson
2016-05-27 14:00 ` [PATCH 01/11] drm: Export drm_dev_init() for subclassing Chris Wilson
2016-05-27 15:29 ` Nils Wallménius
2016-05-27 15:36 ` Chris Wilson
2016-05-27 15:54 ` Emil Velikov
2016-05-27 16:08 ` [Intel-gfx] " Chris Wilson
2016-05-27 16:11 ` Emil Velikov
2016-05-27 14:00 ` [PATCH 02/11] drm: Add a callback from connector registering Chris Wilson
2016-05-30 8:49 ` Daniel Vetter [this message]
2016-05-30 8:57 ` Chris Wilson
2016-05-27 14:00 ` [PATCH 03/11] drm/i915: Perform async fbdev initialisation much later Chris Wilson
2016-05-27 14:00 ` [PATCH 04/11] drm/i915: Move connector registration to driver registration phase Chris Wilson
2016-05-27 14:00 ` [PATCH 05/11] drm/i915: Register debugfs interface last Chris Wilson
2016-05-27 14:00 ` [PATCH 06/11] drm/i915: Demidlayer driver loading Chris Wilson
2016-05-27 14:00 ` [PATCH 07/11] drm/i915: Demidlayer driver unloading Chris Wilson
2016-05-27 14:00 ` [PATCH 08/11] drm/i915: Start exploiting drm_device subclassing Chris Wilson
2016-05-27 14:15 ` Tvrtko Ursulin
2016-05-27 14:46 ` [PATCH] drm/i915: Remove drm_i915_private->dev backpointer Chris Wilson
2016-05-30 6:58 ` Joonas Lahtinen
2016-05-30 8:21 ` Chris Wilson
2016-05-27 14:00 ` [PATCH 09/11] drm/i915: Merge i915_dma.c into i915_drv.c Chris Wilson
2016-05-30 6:30 ` Joonas Lahtinen
2016-05-27 14:00 ` [PATCH 10/11] drm/i915: Split out the PCI driver interface to i915_pci.c Chris Wilson
2016-05-30 6:36 ` Joonas Lahtinen
2016-05-27 14:00 ` [PATCH 11/11] drm/i915: Move module init/exit " Chris Wilson
2016-05-30 6:44 ` Joonas Lahtinen
2016-05-30 7:55 ` Chris Wilson
2016-05-27 14:58 ` ✗ Ro.CI.BAT: failure for series starting with [01/11] drm: Export drm_dev_init() for subclassing (rev2) Patchwork
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=20160530084943.GC27098@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
/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