From: Imre Deak <imre.deak@intel.com>
To: Nanley G Chery <nanley.g.chery@intel.com>,
Jordan Justen <jordan.l.justen@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/fourcc: Document the Intel CCS modifiers' CC plane expected pitch
Date: Tue, 28 Jun 2022 15:07:56 +0300 [thread overview]
Message-ID: <YrrvHCc+/5nEkJa0@ideak-desk.fi.intel.com> (raw)
In-Reply-To: <DM4PR11MB59952D0A2E4B2CA1B01E9BAFDCB49@DM4PR11MB5995.namprd11.prod.outlook.com>
On Sat, Jun 25, 2022 at 12:38:50AM +0300, Chery, Nanley G wrote:
> +Jordan (FYI)
>
> I think the commit message has an extra "color" next to "CC".
IIUC, i915 calls all the planes contained in a framebuffer "color
planes" for consistency (so main-, aux-, CC color planes).
> With or without that dropped,
>
> Reviewed-by: Nanley Chery <nanley.g.chery@intel.com>
The patch is pushed to drm-misc-next, thanks for the reviews.
--Imre
> Thanks for the fix.
>
> > -----Original Message-----
> > From: Deak, Imre <imre.deak@intel.com>
> > Sent: Thursday, June 23, 2022 10:50 AM
> > To: dri-devel@lists.freedesktop.org
> > Cc: intel-gfx@lists.freedesktop.org; Chery, Nanley G <nanley.g.chery@intel.com>
> > Subject: [PATCH] drm/fourcc: Document the Intel CCS modifiers' CC plane expected pitch
> >
> > The driver expects the pitch of the Intel CCS CC color planes to be
> > 64 bytes aligned, adjust the modifier descriptions accordingly.
> >
> > Cc: Nanley Chery <nanley.g.chery@intel.com>
> > Signed-off-by: Imre Deak <imre.deak@intel.com>
> > ---
> > include/uapi/drm/drm_fourcc.h | 8 ++++----
> > 1 file changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/include/uapi/drm/drm_fourcc.h b/include/uapi/drm/drm_fourcc.h
> > index f1972154a5940..c1b4cfda75075 100644
> > --- a/include/uapi/drm/drm_fourcc.h
> > +++ b/include/uapi/drm/drm_fourcc.h
> > @@ -559,7 +559,7 @@ extern "C" {
> > *
> > * The main surface is Y-tiled and is at plane index 0 whereas CCS is linear
> > * and at index 1. The clear color is stored at index 2, and the pitch should
> > - * be ignored. The clear color structure is 256 bits. The first 128 bits
> > + * be 64 bytes aligned. The clear color structure is 256 bits. The first 128 bits
> > * represents Raw Clear Color Red, Green, Blue and Alpha color each represented
> > * by 32 bits. The raw clear color is consumed by the 3d engine and generates
> > * the converted clear color of size 64 bits. The first 32 bits store the Lower
> > @@ -612,9 +612,9 @@ extern "C" {
> > * outside of the GEM object in a reserved memory area dedicated for the
> > * storage of the CCS data for all RC/RC_CC/MC compressible GEM objects. The
> > * main surface pitch is required to be a multiple of four Tile 4 widths. The
> > - * clear color is stored at plane index 1 and the pitch should be ignored. The
> > - * format of the 256 bits of clear color data matches the one used for the
> > - * I915_FORMAT_MOD_Y_TILED_GEN12_RC_CCS_CC modifier, see its description
> > + * clear color is stored at plane index 1 and the pitch should be 64 bytes
> > + * aligned. The format of the 256 bits of clear color data matches the one used
> > + * for the I915_FORMAT_MOD_Y_TILED_GEN12_RC_CCS_CC modifier, see its description
> > * for details.
> > */
> > #define I915_FORMAT_MOD_4_TILED_DG2_RC_CCS_CC fourcc_mod_code(INTEL, 12)
> > --
> > 2.30.2
>
next prev parent reply other threads:[~2022-06-28 12:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 14:49 [Intel-gfx] [PATCH] drm/fourcc: Document the Intel CCS modifiers' CC plane expected pitch Imre Deak
2022-06-23 16:16 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2022-06-23 16:39 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-06-24 21:38 ` [Intel-gfx] [PATCH] " Chery, Nanley G
2022-06-24 21:40 ` Chery, Nanley G
2022-06-26 23:39 ` Jordan Justen
2022-06-28 12:07 ` Imre Deak [this message]
2022-06-27 15:37 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for " Patchwork
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=YrrvHCc+/5nEkJa0@ideak-desk.fi.intel.com \
--to=imre.deak@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jordan.l.justen@intel.com \
--cc=nanley.g.chery@intel.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