From: Rob Clark <robdclark@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: freedreno@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
Daniel Vetter <daniel@ffwll.ch>,
Daniel Stone <daniels@collabora.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Rob Clark <robdclark@chromium.org>,
linux-kernel@vger.kernel.org (open list),
linux-pm@vger.kernel.org (open list:POWER MANAGEMENT CORE),
Marijn Suijten <marijn.suijten@somainline.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Sean Paul <sean@poorly.run>
Subject: [PATCH v3 0/2] drm/msm/gem: Add metadata uapi
Date: Mon, 6 Nov 2023 10:50:24 -0800 [thread overview]
Message-ID: <20231106185028.209462-1-robdclark@gmail.com> (raw)
From: Rob Clark <robdclark@chromium.org>
Add metadata mechanism to provide a back-channel to communicate image
layout information between vk and gl, because EXT_external_objects
doesn't support explicit modifiers and "OPTIMAL_TILING_EXT" is not
enough information for the importer to deduce the layout.
Rob Clark (2):
drm/msm: Small uabi fixes
drm/msm/gem: Add metadata
drivers/gpu/drm/msm/msm_drv.c | 94 ++++++++++++++++++++++++++++++++++-
drivers/gpu/drm/msm/msm_gem.c | 1 +
drivers/gpu/drm/msm/msm_gem.h | 4 ++
include/uapi/drm/msm_drm.h | 2 +
4 files changed, 99 insertions(+), 2 deletions(-)
--
2.41.0
WARNING: multiple messages have this Message-ID (diff)
From: Rob Clark <robdclark@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: Rob Clark <robdclark@chromium.org>,
Daniel Stone <daniels@collabora.com>,
"open list:POWER MANAGEMENT CORE" <linux-pm@vger.kernel.org>,
linux-arm-msm@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Sean Paul <sean@poorly.run>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Marijn Suijten <marijn.suijten@somainline.org>,
freedreno@lists.freedesktop.org
Subject: [PATCH v3 0/2] drm/msm/gem: Add metadata uapi
Date: Mon, 6 Nov 2023 10:50:24 -0800 [thread overview]
Message-ID: <20231106185028.209462-1-robdclark@gmail.com> (raw)
From: Rob Clark <robdclark@chromium.org>
Add metadata mechanism to provide a back-channel to communicate image
layout information between vk and gl, because EXT_external_objects
doesn't support explicit modifiers and "OPTIMAL_TILING_EXT" is not
enough information for the importer to deduce the layout.
Rob Clark (2):
drm/msm: Small uabi fixes
drm/msm/gem: Add metadata
drivers/gpu/drm/msm/msm_drv.c | 94 ++++++++++++++++++++++++++++++++++-
drivers/gpu/drm/msm/msm_gem.c | 1 +
drivers/gpu/drm/msm/msm_gem.h | 4 ++
include/uapi/drm/msm_drm.h | 2 +
4 files changed, 99 insertions(+), 2 deletions(-)
--
2.41.0
next reply other threads:[~2023-11-06 18:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 18:50 Rob Clark [this message]
2023-11-06 18:50 ` [PATCH v3 0/2] drm/msm/gem: Add metadata uapi Rob Clark
2023-11-06 18:50 ` [PATCH v3 1/2] drm/msm: Small uabi fixes Rob Clark
2023-11-06 18:50 ` Rob Clark
2023-11-06 18:50 ` [PATCH v3 2/2] drm/msm/gem: Add metadata Rob Clark
2023-11-06 18:50 ` Rob Clark
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=20231106185028.209462-1-robdclark@gmail.com \
--to=robdclark@gmail.com \
--cc=daniel@ffwll.ch \
--cc=daniels@collabora.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=rafael@kernel.org \
--cc=robdclark@chromium.org \
--cc=sean@poorly.run \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.