dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Mauro Rossi <issor.oruam@gmail.com>
Cc: Robert Foss <robert.foss@collabora.com>,
	cwhuang@linux.org.tw, Emil Velikov <emil.l.velikov@gmail.com>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] xf86drm: add drmOpenByFB
Date: Sun, 24 May 2020 20:53:07 +0200	[thread overview]
Message-ID: <CAKMK7uGKps4AfLKTSP2HZTHd1cm+1dMD9r8M9rKobqwXGgv5EQ@mail.gmail.com> (raw)
In-Reply-To: <20200523154426.1088988-1-issor.oruam@gmail.com>

On Sat, May 23, 2020 at 5:44 PM Mauro Rossi <issor.oruam@gmail.com> wrote:
>
> OpenByFB is introduced to overcome GPU driver loading order issue
> on a device with multiple GPUs, e.g. Intel iGPU and Nvidia dGPU
> where the first drmfb kernel module loaded will become device file
> /dev/dri/card0 and the second will become /dev/dri/card1
>
> The use case is to prefer Intel iGPU over dGPU, or viceversa,
> in a deterministic and reliable manner.
>
> OpenByFB function opens the DRM device with specified fb and node type,
> thus enabling gralloc to open the correct device node of the primary fb,
> regardless of the GPU driver loading order.

The fbdev load ordering is as inconsistent/random as the dri node
loading. Well more so, because you might have random firmware fbdev
drivers hanging out there. Hence I'm not following how this solves
anything for your problem.

I think usually what userspace does it look at the boot_vga property
of the underlying device in sysfs, and prefer that one. Iirc (but
might be wrong) that's patched to essentially mean "primary display
device, the same the firmware used for boot-up screens". Either way I
think the proper way to solve this is you figure out matching rules
you care about using udev/sysfs, and then use that information to open
the right drm node. Opening by fbdev seems a most convoluted way to
get to a drm device (we're trying to deprecate fbdev outright as much
as possible), and you could even match for any specific device with
sysfs already if that's what you're doing using udev rules.
-Daniel


>
> Signed-off-by: Chih-Wei Huang <cwhuang@linux.org.tw>
> ---
>  core-symbols.txt |  1 +
>  xf86drm.c        | 42 ++++++++++++++++++++++++++++++++++++++++++
>  xf86drm.h        |  1 +
>  3 files changed, 44 insertions(+)
>
> diff --git a/core-symbols.txt b/core-symbols.txt
> index 1ff4ecaa..6bf8c70d 100644
> --- a/core-symbols.txt
> +++ b/core-symbols.txt
> @@ -146,6 +146,7 @@ drmModeSetCursor2
>  drmModeSetPlane
>  drmMsg
>  drmOpen
> +drmOpenByFB
>  drmOpenControl
>  drmOpenOnce
>  drmOpenOnceWithType
> diff --git a/xf86drm.c b/xf86drm.c
> index b49d42f7..229a54bf 100644
> --- a/xf86drm.c
> +++ b/xf86drm.c
> @@ -793,6 +793,48 @@ drm_public int drmOpenRender(int minor)
>      return drmOpenMinor(minor, 0, DRM_NODE_RENDER);
>  }
>
> +/**
> + * Open the DRM device with specified type of specified framebuffer.
> + *
> + * Looks up the associated DRM device with specified type of the
> + * specified framebuffer and opens it.
> + *
> + * \param fb the index of framebuffer.
> + * \param type the device node type to open, PRIMARY, CONTROL or RENDER
> + *
> + * \return a file descriptor on success, or a negative value on error.
> + *
> + */
> +drm_public int drmOpenByFB(int fb, int type)
> +{
> +#ifdef __linux__
> +    DIR *sysdir;
> +    struct dirent *ent;
> +    char buf[64];
> +    const char *name = drmGetMinorName(type);
> +    int fd = -1, len = strlen(name);
> +
> +    snprintf(buf, sizeof(buf), "/sys/class/graphics/fb%d/device/drm", fb);
> +    sysdir = opendir(buf);
> +    if (!sysdir)
> +        return -errno;
> +
> +    while ((ent = readdir(sysdir))) {
> +        if (!strncmp(ent->d_name, name, len)) {
> +            snprintf(buf, sizeof(buf), "%s/%s", DRM_DIR_NAME, ent->d_name);
> +            fd = open(buf, O_RDWR | O_CLOEXEC, 0);
> +            break;
> +        }
> +    }
> +
> +    closedir(sysdir);
> +    return fd;
> +#else
> +#warning "Missing implementation of drmOpenByFB"
> +    return -EINVAL;
> +#endif
> +}
> +
>  /**
>   * Free the version information returned by drmGetVersion().
>   *
> diff --git a/xf86drm.h b/xf86drm.h
> index 7b85079a..d45d696f 100644
> --- a/xf86drm.h
> +++ b/xf86drm.h
> @@ -605,6 +605,7 @@ extern int           drmOpenWithType(const char *name, const char *busid,
>
>  extern int           drmOpenControl(int minor);
>  extern int           drmOpenRender(int minor);
> +extern int           drmOpenByFB(int fb, int type);
>  extern int           drmClose(int fd);
>  extern drmVersionPtr drmGetVersion(int fd);
>  extern drmVersionPtr drmGetLibVersion(int fd);
> --
> 2.25.1
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel



-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-05-24 18:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-23 15:44 [PATCH] xf86drm: add drmOpenByFB Mauro Rossi
2020-05-23 21:36 ` Simon Ser
2020-05-24 18:53 ` Daniel Vetter [this message]
2020-05-24 19:25   ` Simon Ser
2020-05-28  9:46     ` Chih-Wei Huang
2020-05-28 12:38       ` Emil Velikov
2020-05-29  7:48       ` Pekka Paalanen
2020-05-29 14:20         ` Alex Deucher

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=CAKMK7uGKps4AfLKTSP2HZTHd1cm+1dMD9r8M9rKobqwXGgv5EQ@mail.gmail.com \
    --to=daniel@ffwll.ch \
    --cc=cwhuang@linux.org.tw \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    --cc=issor.oruam@gmail.com \
    --cc=robert.foss@collabora.com \
    /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).