From: Maxime Ripard <maxime@cerno.tech>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: Tomohito Esaki <etom@igel.co.jp>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
dri-devlel@lists.freedesktop.org,
linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATH 0/4] [RFC] Support virtual DRM
Date: Mon, 21 Jun 2021 11:24:54 +0200 [thread overview]
Message-ID: <20210621092454.jvdmelk2h427jn5v@gilmour> (raw)
In-Reply-To: <9853d0a9-6053-db64-9c79-40b7e0689eec@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]
Hi,
On Mon, Jun 21, 2021 at 09:10:19AM +0200, Thomas Zimmermann wrote:
> Am 21.06.21 um 08:27 schrieb Tomohito Esaki:
> > 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.
>
> I briefly looked over your patches. I didn't understand how this is
> different to the functionality of a compositor? Shouldn't this be solved in
> userspace?
I think there could be a bunch of use-cases for something that could
"steal" a plane without the compositor knowing.
Something I'd really like to work at some point for example is that the
downstream RaspberryPi display driver has a visual clue when it's
running too hot or is in over-current.
I don't think this is the right solution though. The DT binding makes it
far too static, and if there's a compositor I'd assume it would want to
know about it somehow (at least if it's from the userspace) ?
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2021-06-21 9:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 6:27 [PATH 0/4] [RFC] Support virtual DRM Tomohito Esaki
2021-06-21 6:27 ` [PATH 1/4] drm: Add Virtual DRM device driver Tomohito Esaki
2021-06-21 6:27 ` [PATH 2/4] rcar-du: Add support virtual DRM device Tomohito Esaki
2021-06-21 6:27 ` [PATH 3/4] dt-bindings: display: Add virtual DRM Tomohito Esaki
2021-06-21 6:27 ` [PATH 4/4] doc-rst: Add virtual DRM documentation Tomohito Esaki
2021-06-21 7:10 ` [PATH 0/4] [RFC] Support virtual DRM Thomas Zimmermann
2021-06-21 9:24 ` Maxime Ripard [this message]
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
2021-06-21 6:43 Tomohito Esaki
2021-06-22 8:04 ` Simon Ser
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=20210621092454.jvdmelk2h427jn5v@gilmour \
--to=maxime@cerno.tech \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devlel@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=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).