From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: "daniel@ffwll.ch" <daniel@ffwll.ch>,
"dh.herrmann@gmail.com" <dh.herrmann@gmail.com>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"airlied@linux.ie" <airlied@linux.ie>
Subject: Re: [PATCH 2/4 v3] drm: Introduce drm_connector_register_all() helper
Date: Wed, 23 Mar 2016 13:41:05 +0000 [thread overview]
Message-ID: <1458740464.3213.9.camel@synopsys.com> (raw)
In-Reply-To: <CANq1E4QSaEOM8Ug_KxCO1unqY_iEP+WOttx=9xHH1oNWd-X2Mg@mail.gmail.com>
Hi David,
On Wed, 2016-03-23 at 12:13 +0100, David Herrmann wrote:
> Hi
>
> On Wed, Mar 23, 2016 at 9:42 AM, Alexey Brodkin
> <Alexey.Brodkin@synopsys.com> wrote:
> >
> > As a pair to already existing drm_connector_unregister_all() we're adding
> > generic implementation of what is already done in some drivers.
> >
> > Once this helper is implemented we'll be ready to switch existing
> > driver-specific implementations with the generic one.
> >
> > Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> > Cc: Daniel Vetter <daniel@ffwll.ch>
> > Cc: David Airlie <airlied@linux.ie>
> > ---
> >
> > Changes v2 -> v3:
> > * Updated title with capital after colon
> > * Simplified failure path with direct and unconditional invocation of
> > unregister_all()
> > * Updated kerneldoc description of the drm_connector_register_all()
> >
> > Changes v1 -> v2:
> > * Rename drm_connector_unplug_all() to drm_connector_unregister_all()
> > * Use drm_for_each_connector() instead of list_for_each_entry()
> > * Updated kerneldoc for drm_dev_register()
> >
> > drivers/gpu/drm/drm_crtc.c | 43 +++++++++++++++++++++++++++++++++++++++++++
> > drivers/gpu/drm/drm_drv.c | 6 +++++-
> > include/drm/drm_crtc.h | 3 ++-
> > 3 files changed, 50 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/drm_crtc.c b/drivers/gpu/drm/drm_crtc.c
> > index 65488a6..21eea11 100644
> > --- a/drivers/gpu/drm/drm_crtc.c
> > +++ b/drivers/gpu/drm/drm_crtc.c
> > @@ -1081,6 +1081,49 @@ void drm_connector_unregister(struct drm_connector *connector)
> > EXPORT_SYMBOL(drm_connector_unregister);
> >
> > /**
> > + * drm_connector_register_all - register all connectors
> > + * @dev: drm device
> > + *
> > + * This function registers all connectors in sysfs and other places so that
> > + * userspace can start to access them. Drivers can call it after calling
> > + * drm_dev_register() to complete the device registration, if they don't call
> > + * drm_connector_register() on each connector individually.
> > + *
> > + * When a device is unplugged and should be removed from userspace access,
> > + * call drm_connector_unregister_all(), which is the inverse of this
> > + * function.
> > + *
> > + * Returns:
> > + * Zero on success, error code on failure.
> > + */
> > +int drm_connector_register_all(struct drm_device *dev)
> > +{
> > + struct drm_connector *connector;
> > + int ret;
> > +
> > + mutex_lock(&dev->mode_config.mutex);
> > +
> > + drm_for_each_connector(connector, dev) {
> > + ret = drm_connector_register(connector);
> > + if (ret) {
> > + /*
> > + * We may safely call unregister_all() here within
> > + * area locked with mutex because unregister_all()
> > + * doesn't use locks inside (see a comment in that
> > + * function).
> > + */
> Ugh? unregister_all() says:
>
> /* FIXME: taking the mode config mutex ends up in a clash with sysfs */
>
> This strongly contradicts your comment. Anyway, regardless how you
> want to fix it: You better unlock the mode-config mutex before
> returning below.
So good catch.
But what I really meant since we didn't get any further after registering
all "good" connections (see we're not releasing mutex still) the will be
no clashes with sysfs.
Still I;d like Daniel to comment on that separately.
-Alexey
next prev parent reply other threads:[~2016-03-23 13:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 8:42 [PATCH 0/4 v3] drm: Introduce drm_connector_register_all() helper Alexey Brodkin
2016-03-23 8:42 ` [PATCH 1/4 v3] drm: Rename drm_connector_unplug_all() to drm_connector_unregister_all() Alexey Brodkin
2016-03-23 9:02 ` Boris Brezillon
2016-03-23 8:42 ` [PATCH 2/4 v3] drm: Introduce drm_connector_register_all() helper Alexey Brodkin
2016-03-23 11:13 ` David Herrmann
2016-03-23 13:41 ` Alexey Brodkin [this message]
2016-03-29 8:19 ` Daniel Vetter
2016-03-29 9:12 ` Alexey Brodkin
2016-03-29 12:52 ` Daniel Vetter
2016-03-23 8:42 ` [PATCH 3/4 v3] drm: atmel_hldc: Use generic " Alexey Brodkin
2016-03-23 8:42 ` [PATCH 4/4 v3] drm: rcar-du: " Alexey Brodkin
2016-03-23 10:37 ` [PATCH 0/4 v3] drm: Introduce " Daniel Vetter
2016-03-28 10:36 ` Alexey Brodkin
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=1458740464.3213.9.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dh.herrmann@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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