From: Simon Ser <contact@emersion.fr>
To: Tomohito Esaki <etom@igel.co.jp>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATH 0/4] [RFC] Support virtual DRM
Date: Tue, 22 Jun 2021 08:04:53 +0000 [thread overview]
Message-ID: <08kxmstH-uYXe0-6PB5pM0R4Ng9s8AKF4IUiqVzHUDVR3eztlXVsNCY_syeRm6ItQtYAqUysd2NxbeF9YYY4NgwEjPEgIUza7BtuGYmFoI4=@emersion.fr> (raw)
In-Reply-To: <20210621064403.26663-1-etom@igel.co.jp>
On Monday, June 21st, 2021 at 08:43, Tomohito Esaki <etom@igel.co.jp> wrote:
> Virtual DRM splits the overlay planes of a display controller into multiple
> virtual devices to allow each plane to be accessed by each process.
> This makes it possible to overlay images output from multiple processes on a
> display. For example, one process displays the camera image without compositor
> while another process overlays the UI.
Updating the KMS state from multiple processes doesn't sound like a
good idea. This opens up synchronization and global device limits
issues.
Are you aware of DRM leasing?
next prev parent reply other threads:[~2021-06-22 8:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 6:43 [PATH 0/4] [RFC] Support virtual DRM Tomohito Esaki
2021-06-21 6:44 ` [PATH 1/4] drm: Add Virtual DRM device driver Tomohito Esaki
2021-06-21 13:55 ` kernel test robot
[not found] ` <20210621155517.GB823900@ravnborg.org>
2021-06-22 4:10 ` Esaki Tomohito
2021-06-21 6:44 ` [PATH 2/4] rcar-du: Add support virtual DRM device Tomohito Esaki
2021-06-21 11:25 ` kernel test robot
2021-06-21 6:44 ` [PATH 3/4] dt-bindings: display: Add virtual DRM Tomohito Esaki
2021-06-21 17:40 ` Rob Herring
2021-06-22 4:17 ` Esaki Tomohito
2021-06-22 16:54 ` Rob Herring
2021-06-21 6:44 ` [PATH 4/4] doc-rst: Add virtual DRM documentation Tomohito Esaki
2021-06-22 8:04 ` Simon Ser [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-21 6:27 [PATH 0/4] [RFC] Support virtual DRM Tomohito Esaki
2021-06-21 7:10 ` Thomas Zimmermann
2021-06-21 9:24 ` Maxime Ripard
2021-06-22 4:36 ` Esaki Tomohito
2021-06-23 14:39 ` Maxime Ripard
2021-06-22 4:02 ` Esaki Tomohito
2021-06-22 7:57 ` Pekka Paalanen
2021-06-23 8:04 ` Michel Dänzer
2021-06-23 8:21 ` Esaki Tomohito
2021-06-22 9:12 ` Thomas Zimmermann
2021-06-21 16:05 ` Enrico Weigelt, metux IT consult
2021-06-22 4:03 ` Esaki Tomohito
2021-06-22 8:12 ` Pekka Paalanen
2021-06-22 19:12 ` Daniel Vetter
2021-06-23 6:56 ` Esaki Tomohito
2021-06-23 8:39 ` Pekka Paalanen
2021-06-23 9:22 ` Esaki Tomohito
2021-06-23 11:41 ` Pekka Paalanen
2021-06-25 1:55 ` Esaki Tomohito
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='08kxmstH-uYXe0-6PB5pM0R4Ng9s8AKF4IUiqVzHUDVR3eztlXVsNCY_syeRm6ItQtYAqUysd2NxbeF9YYY4NgwEjPEgIUza7BtuGYmFoI4=@emersion.fr' \
--to=contact@emersion.fr \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=etom@igel.co.jp \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).