From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Rob Clark <robin.clark@oss.qualcomm.com>,
Dmitry Baryshkov <lumag@kernel.org>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
Jessica Zhang <jesszhan0024@gmail.com>,
Sean Paul <sean@poorly.run>,
Marijn Suijten <marijn.suijten@somainline.org>,
David Airlie <airlied@gmail.com>,
Simona Vetter <simona@ffwll.ch>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Bryan O'Donoghue <bod@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Jordan Crouse <jordan@cosmicpenguin.net>,
linux-media@vger.kernel.org,
Vikash Garodia <vikash.garodia@oss.qualcomm.com>,
Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>,
Robert Mader <robert.mader@collabora.com>,
Neil Armstrong <neil.armstrong@linaro.org>
Subject: Re: [PATCH v2 6/8] media: docs: pixfmt-reserved: describe the QC08C and QC10C layout
Date: Fri, 06 Nov 2026 14:58:19 -0500 [thread overview]
Message-ID: <ff90b48a069e4e4af77b7911e1d0b9eb07fae1d7.camel@collabora.com> (raw)
In-Reply-To: <20261106-ubwc-format-docs-v2-6-82949f88f030@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 864 bytes --]
Le vendredi 06 novembre 2026 à 15:44 +0200, Dmitry Baryshkov a écrit :
> QC08C and QC10C are documented as opaque formats with four planes, or
> eight for interlaced video. Neither is true for the drivers: Venus and
> Iris use a single memory plane, nothing produces interlaced buffers, and
> the display controller and the GPU import these buffers, so the layout
> is part of the contract between them.
>
> Describe the sections of the buffer, their order, strides, line counts
> and alignment. The compressed contents stay opaque, they depend on the
> UBWC configuration of the platform.
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Rob just confirmed that this is effectively the mapping we want. The
documentation is very good and clear, thanks!
Reviewed-by: Nicolas Dufresne <nicolas.dufresne@collabora.com>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-11-06 19:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 13:44 [PATCH v2 0/8] drm/msm, media: define the UBWC buffer layout Dmitry Baryshkov
2026-11-06 13:44 ` [PATCH v2 1/8] drm/msm/dpu: fix the comment on the RGB UBWC plane count Dmitry Baryshkov
2026-11-06 13:44 ` [PATCH v2 2/8] drm/msm: separate compressed P010 and P030 (TP10) Dmitry Baryshkov
2026-11-06 14:37 ` Rob Clark
2026-11-06 13:44 ` [PATCH v2 3/8] drm/msm: move the UBWC plane size calculation out of DPU Dmitry Baryshkov
2026-11-06 13:44 ` [PATCH v2 4/8] drm/msm: check UBWC framebuffers against their layout Dmitry Baryshkov
2026-11-06 13:44 ` [PATCH v2 5/8] drm/fourcc: describe the Qualcomm UBWC layout Dmitry Baryshkov
2026-11-06 13:44 ` [PATCH v2 6/8] media: docs: pixfmt-reserved: describe the QC08C and QC10C layout Dmitry Baryshkov
2026-11-06 19:58 ` Nicolas Dufresne [this message]
2026-11-06 13:44 ` [PATCH v2 7/8] media: venus: report the QC10C data stride Dmitry Baryshkov
2026-11-06 13:44 ` [PATCH v2 8/8] media: qcom: iris: describe QC10C as P030 (TP10) Dmitry Baryshkov
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=ff90b48a069e4e4af77b7911e1d0b9eb07fae1d7.camel@collabora.com \
--to=nicolas.dufresne@collabora.com \
--cc=abhinav.kumar@linux.dev \
--cc=airlied@gmail.com \
--cc=bod@kernel.org \
--cc=dikshita.agarwal@oss.qualcomm.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jesszhan0024@gmail.com \
--cc=jordan@cosmicpenguin.net \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marijn.suijten@somainline.org \
--cc=mchehab@kernel.org \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robert.mader@collabora.com \
--cc=robin.clark@oss.qualcomm.com \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=vikash.garodia@oss.qualcomm.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
all inboxes | Powered by JetHome®