From: Matt Roper <matthew.d.roper@intel.com>
To: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
Cc: Suraj Kandpal <suraj.kandpal@intel.com>,
<intel-xe@lists.freedesktop.org>,
<intel-gfx@lists.freedesktop.org>,
Arun R Murthy <arun.r.murthy@intel.com>
Subject: Re: [PATCH 1/4] drm/i915/xe3lpd: Increase resolution for plane to support 6k
Date: Thu, 24 Oct 2024 12:48:48 -0700 [thread overview]
Message-ID: <20241024194848.GP4891@mdroper-desk1.amr.corp.intel.com> (raw)
In-Reply-To: <d0b4e4b8-f6c5-41f7-b1f7-36b06397b852@intel.com>
On Thu, Oct 24, 2024 at 05:16:51PM +0530, Nautiyal, Ankit K wrote:
>
> On 10/24/2024 9:25 AM, Suraj Kandpal wrote:
> > DISPLAY_VER >= 30 onwards CRTC can now support 6k resolution.
> > Increase pipe and plane max width and height to reflect this
>
> Only max width is changed.
>
> > increase in resolution.
> >
> > --v2
> > -Take care of the subsampling scenario sooner rather than later [Matt]
> >
> > Signed-off-by: Arun R Murthy <arun.r.murthy@intel.com>
> > Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> > ---
> > drivers/gpu/drm/i915/display/intel_display.c | 5 ++++-
> > .../gpu/drm/i915/display/skl_universal_plane.c | 16 +++++++++++++++-
> > 2 files changed, 19 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
> > index e1f6255e918b..37bac53f996e 100644
> > --- a/drivers/gpu/drm/i915/display/intel_display.c
> > +++ b/drivers/gpu/drm/i915/display/intel_display.c
> > @@ -8432,7 +8432,10 @@ intel_mode_valid_max_plane_size(struct drm_i915_private *dev_priv,
> > * plane so let's not advertize modes that are
> > * too big for that.
> > */
> > - if (DISPLAY_VER(dev_priv) >= 11) {
> > + if (DISPLAY_VER(dev_priv) >= 30) {
> > + plane_width_max = 6144 * num_joined_pipes;
> > + plane_height_max = 4096;
>
> plane_height_max is not changed, should be 4320.
Where do you see that documented? At least on bspec 68858 it says
Unjoined pipe source size, plane size, and pipe active size
maximum vertical 4096.
and based on bspec 49199, that restriction goes back to at least gen12.
So it looks like we might have a bug on older platforms that needs to be
fixed.
When using the joiner the vertical limit goes up to 4320 (on Xe1
platforms) or 4800 (on Xe2/Xe3 platforms).
Matt
>
> Otherwise looks good to me. With the above fixed:
>
> Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>
>
> > + } else if (DISPLAY_VER(dev_priv) >= 11) {
> > plane_width_max = 5120 * num_joined_pipes;
> > plane_height_max = 4320;
> > } else {
> > diff --git a/drivers/gpu/drm/i915/display/skl_universal_plane.c b/drivers/gpu/drm/i915/display/skl_universal_plane.c
> > index 9207b7e96974..b3660c71e499 100644
> > --- a/drivers/gpu/drm/i915/display/skl_universal_plane.c
> > +++ b/drivers/gpu/drm/i915/display/skl_universal_plane.c
> > @@ -432,6 +432,16 @@ static int icl_plane_min_width(const struct drm_framebuffer *fb,
> > }
> > }
> > +static int xe3_plane_max_width(const struct drm_framebuffer *fb,
> > + int color_plane,
> > + unsigned int rotation)
> > +{
> > + if (intel_format_info_is_yuv_semiplanar(fb->format, fb->modifier))
> > + return 4096;
> > + else
> > + return 6144;
> > +}
> > +
> > static int icl_hdr_plane_max_width(const struct drm_framebuffer *fb,
> > int color_plane,
> > unsigned int rotation)
> > @@ -2511,7 +2521,11 @@ skl_universal_plane_create(struct drm_i915_private *dev_priv,
> > intel_fbc_add_plane(skl_plane_fbc(dev_priv, pipe, plane_id), plane);
> > - if (DISPLAY_VER(dev_priv) >= 11) {
> > + if (DISPLAY_VER(dev_priv) >= 30) {
> > + plane->max_width = xe3_plane_max_width;
> > + plane->max_height = icl_plane_max_height;
> > + plane->min_cdclk = icl_plane_min_cdclk;
> > + } else if (DISPLAY_VER(dev_priv) >= 11) {
> > plane->min_width = icl_plane_min_width;
> > if (icl_is_hdr_plane(dev_priv, plane_id))
> > plane->max_width = icl_hdr_plane_max_width;
--
Matt Roper
Graphics Software Engineer
Linux GPU Platform Enablement
Intel Corporation
next prev parent reply other threads:[~2024-10-24 19:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 3:55 [PATCH 0/4] Add 6k resolution support for a single CRTC Suraj Kandpal
2024-10-24 3:55 ` [PATCH 1/4] drm/i915/xe3lpd: Increase resolution for plane to support 6k Suraj Kandpal
2024-10-24 11:46 ` Nautiyal, Ankit K
2024-10-24 19:48 ` Matt Roper [this message]
2024-10-25 4:05 ` Nautiyal, Ankit K
2024-10-24 3:55 ` [PATCH 2/4] drm/i915/xe3lpd: Increase max_h max_v for PSR Suraj Kandpal
2024-10-24 13:04 ` Nautiyal, Ankit K
2024-10-24 19:59 ` Matt Roper
2024-10-24 3:55 ` [PATCH 3/4] drm/i914/xe3lpd: Increase bigjoiner limitations Suraj Kandpal
2024-10-24 11:51 ` Nautiyal, Ankit K
2024-10-24 3:55 ` [PATCH 4/4] drm/i915/xe3lpd: Prune modes for YUV420 Suraj Kandpal
2024-10-24 12:20 ` Nautiyal, Ankit K
2024-10-24 9:22 ` ✓ Fi.CI.BAT: success for Add 6k resolution support for a single CRTC (rev2) Patchwork
2024-10-24 9:23 ` ✗ Fi.CI.SPARSE: warning " Patchwork
2024-10-24 11:24 ` ✗ Fi.CI.IGT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-10-15 6:10 [PATCH 0/4] Add 6k resolution support for a single CRTC Suraj Kandpal
2024-10-15 6:10 ` [PATCH 1/4] drm/i915/xe3lpd: Increase resolution for plane to support 6k Suraj Kandpal
2024-10-23 21:41 ` Matt Roper
2024-10-24 2:45 ` Kandpal, Suraj
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=20241024194848.GP4891@mdroper-desk1.amr.corp.intel.com \
--to=matthew.d.roper@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=suraj.kandpal@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