[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <08kxmstH-uYXe0-6PB5pM0R4Ng9s8AKF4IUiqVzHUDVR3eztlXVsNCY_syeRm6ItQtYAqUysd2NxbeF9YYY4NgwEjPEgIUza7BtuGYmFoI4=@emersion.fr>
Date: Tue, 22 Jun 2021 08:04:53 +0000
From: Simon Ser <contact@...rsion.fr>
To: Tomohito Esaki <etom@...l.co.jp>
Cc: Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel@...ll.ch>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Kieran Bingham <kieran.bingham+renesas@...asonboard.com>,
devicetree@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
linux-renesas-soc@...r.kernel.org
Subject: Re: [PATH 0/4] [RFC] Support virtual DRM
On Monday, June 21st, 2021 at 08:43, Tomohito Esaki <etom@...l.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?
Powered by blists - more mailing lists