Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>
To: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
Cc: igt-dev@lists.freedesktop.org, juha-pekka.heikkila@intel.com,
	petri.latvala@intel.com
Subject: Re: [igt-dev] [PATCH i-g-t v4 02/16] include/drm-uapi: Introduce new Tile 4 format
Date: Tue, 22 Feb 2022 18:41:37 +0200	[thread overview]
Message-ID: <20220222164137.GA31344@intel.com> (raw)
In-Reply-To: <YhM8DzfyNHVt4sLg@zkempczy-mobl2>

On Mon, Feb 21, 2022 at 08:15:27AM +0100, Zbigniew Kempczyński wrote:
> On Fri, Feb 18, 2022 at 02:39:22PM +0530, Jeevan B wrote:
> > This tiling layout uses 4KB tiles in a row-major layout. It has the same
> > shape as Tile Y at two granularities: 4KB (128B x 32) and 64B (16B x 4). It
> > only differs from Tile Y at the 256B granularity in between. At this
> > granularity, Tile Y has a shape of 16B x 32 rows, but this tiling has a shape
> > of 64B x 8 rows.
> > 
> > Signed-off-by: Jeevan B <jeevan.b@intel.com>
> > ---
> >  include/drm-uapi/drm_fourcc.h | 11 +++++++++++
> >  include/drm-uapi/i915_drm.h   |  3 ++-
> >  2 files changed, 13 insertions(+), 1 deletion(-)
> > 
> > diff --git a/include/drm-uapi/drm_fourcc.h b/include/drm-uapi/drm_fourcc.h
> > index 91b6a0fd..318b50fa 100644
> > --- a/include/drm-uapi/drm_fourcc.h
> > +++ b/include/drm-uapi/drm_fourcc.h
> > @@ -559,6 +559,17 @@ extern "C" {
> >   */
> >  #define I915_FORMAT_MOD_Y_TILED_GEN12_RC_CCS_CC fourcc_mod_code(INTEL, 8)
> >  
> > +/*
> > + * Intel Tile 4 layout
> > + *
> > + * This is a tiled layout using 4KB tiles in a row-major layout. It has the same
> > + * shape as Tile Y at two granularities: 4KB (128B x 32) and 64B (16B x 4). It
> > + * only differs from Tile Y at the 256B granularity in between. At this
> > + * granularity, Tile Y has a shape of 16B x 32 rows, but this tiling has a shape
> > + * of 64B x 8 rows.
> > + */
> > +#define I915_FORMAT_MOD_4_TILED         fourcc_mod_code(INTEL, 9)
> > +
> >  /*
> >   * Tiled, NV12MT, grouped in 64 (pixels) x 32 (lines) -sized macroblocks
> >   *
> > diff --git a/include/drm-uapi/i915_drm.h b/include/drm-uapi/i915_drm.h
> > index 9c9e1afa..75206fc3 100644
> > --- a/include/drm-uapi/i915_drm.h
> > +++ b/include/drm-uapi/i915_drm.h
> > @@ -1522,13 +1522,14 @@ struct drm_i915_gem_caching {
> >  #define I915_TILING_NONE	0
> >  #define I915_TILING_X		1
> >  #define I915_TILING_Y		2
> > +#define I915_TILING_4		3
> >  /*
> >   * Do not add new tiling types here.  The I915_TILING_* values are for
> >   * de-tiling fence registers that no longer exist on modern platforms.  Although
> >   * the hardware may support new types of tiling in general (e.g., Tile4), we
> >   * do not need to add them to the uapi that is specific to now-defunct ioctls.
> >   */
> 
> Looks comment + change are in a contradiction.
> 
> I think we should rework tiling a bit in IGT to break away from I915_TILING_*.
> Newer gens supports different tilings and it would be good if we would have
> single point of information what is supported on devid we're on. 
> 
> --
> Zbigniew

Yes, Jeevan I think, you just need to place it where those I915_TILING_Yf/I915_TILING_Ys
are located. See your previous igt/lib patch.
Otherwise we are not supposed to use those modifiers here.

Stan

> 
> > -#define I915_TILING_LAST	I915_TILING_Y
> > +#define I915_TILING_LAST	I915_TILING_4
> >  
> >  #define I915_BIT_6_SWIZZLE_NONE		0
> >  #define I915_BIT_6_SWIZZLE_9		1
> > -- 
> > 2.17.1
> > 

  reply	other threads:[~2022-02-22 16:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18  9:09 [igt-dev] [PATCH i-g-t v4 00/16] DG2 platform definition and Tile 4 plane format support Jeevan B
2022-02-18  9:09 ` [igt-dev] [PATCH i-g-t v4 01/16] lib/intel_device_info: Add a flag to indicate tiling 4 support Jeevan B
2022-02-21  7:42   ` Zbigniew Kempczyński
2022-02-18  9:09 ` [igt-dev] [PATCH i-g-t v4 02/16] include/drm-uapi: Introduce new Tile 4 format Jeevan B
2022-02-21  7:15   ` Zbigniew Kempczyński
2022-02-22 16:41     ` Lisovskiy, Stanislav [this message]
2022-02-18  9:09 ` [igt-dev] [PATCH i-g-t v4 03/16] igt/lib: Add tile 4(F-tile) format support Jeevan B
2022-02-18  9:09 ` [igt-dev] [PATCH i-g-t v4 04/16] lib/igt_draw: Add pixel math for tile-4 Jeevan B
2022-02-18  9:09 ` [igt-dev] [PATCH i-g-t v4 05/16] igt/tests: Add support for Tile4(TileF) format to kms_draw_crc Jeevan B
2022-02-18  9:09 ` [igt-dev] [PATCH i-g-t v4 06/16] igt/tests: Add support for Tile4(TileF) format to kms_rotation_crc Jeevan B
2022-02-18  9:09 ` [igt-dev] [PATCH i-g-t v4 07/16] igt/tests: Add support for Tile4(TileF) format to tests/kms_plane_multiple Jeevan B
2022-02-18  9:09 ` [igt-dev] [PATCH i-g-t v4 08/16] igt/tests: Add support for Tile4(TileF) format to tests/kms_plane_lowres Jeevan B
2022-02-18  9:09 ` [igt-dev] [PATCH i-g-t v4 09/16] igt/tests: Add support for Tile4(TileF) format to tests/kms_big_fb Jeevan B
2022-02-18  9:09 ` [igt-dev] [PATCH i-g-t v4 10/16] igt/tests: Add support for Tile4(TileF) format to testdisplay Jeevan B
2022-02-18  9:09 ` [igt-dev] [PATCH i-g-t v4 11/16] lib/igt_draw: Use XY_FAST_COLOR_BLT on DG2 Jeevan B
2022-02-18  9:09 ` [igt-dev] [PATCH i-g-t v4 12/16] igt/tests: Add support for Tile4(TileF) format to tests/kms_addfb_basic Jeevan B
2022-02-18  9:09 ` [igt-dev] [PATCH i-g-t v4 13/16] tests/kms_frontbuffer_tracking: Add support for 4 tiling Jeevan B
2022-02-18  9:09 ` [igt-dev] [PATCH i-g-t v4 14/16] tests/kms_draw_crc: Use 4 tiling when filling framebuffer Jeevan B
2022-02-18  9:09 ` [igt-dev] [PATCH i-g-t v4 15/16] tests/kms_plane_scaling: Adding Tile-4 support Jeevan B
2022-02-18  9:09 ` [igt-dev] [PATCH i-g-t v4 16/16] tests/kms_plane_scaling: Use tiling 4 if platform has support for it Jeevan B
2022-02-18 10:21 ` [igt-dev] ✓ Fi.CI.BAT: success for DG2 platform definition and Tile 4 plane format support (rev4) Patchwork
2022-02-18 23:08 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=20220222164137.GA31344@intel.com \
    --to=stanislav.lisovskiy@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=juha-pekka.heikkila@intel.com \
    --cc=petri.latvala@intel.com \
    --cc=zbigniew.kempczynski@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