From: Manasi Navare <manasi.d.navare@intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v4 1/2] drm/i915/display/icl: Bump up the hdisplay and vdisplay as per transcoder limits
Date: Mon, 16 Sep 2019 12:19:00 -0700 [thread overview]
Message-ID: <20190916191859.GA13413@intel.com> (raw)
In-Reply-To: <eb58efd5-c193-c176-d18d-b7b793794fd1@linux.intel.com>
On Fri, Sep 13, 2019 at 03:36:39PM +0200, Maarten Lankhorst wrote:
> Hey,
>
> Op 29-07-2019 om 21:17 schreef Manasi Navare:
> > Hi Ville,
> >
> > Thanks for your review, so do we want to merge this as is or
> > do we need some function to reject the 8K mode on ICL in intel_dp_mode_valid()?
> >
> > Manasi
>
> I've pushed this series as-is because it blocks my bigjoiner work. We should probably reject modes in the connector specific functions if we can't handle it. :)
Thanks Maarten. So in case of intel_dp_mode_valid() for example the 8K mode will be rejected if big joiner not supported correct?
Manasi
>
>
> >
> > On Fri, Jul 12, 2019 at 11:29:38PM +0300, Ville Syrjälä wrote:
> >> On Fri, Jul 12, 2019 at 01:22:13PM -0700, Manasi Navare wrote:
> >>> On ICL+, the vertical limits for the transcoders are increased to 8192
> >>> and horizontal limits are bumped to 16K so bump up
> >>> limits in intel_mode_valid()
> >>>
> >>> v4:
> >>> * Increase the hdisplay to 16K (Ville)
> >>> v3:
> >>> * Supported starting ICL (Ville)
> >>> * Use the higher limits from TRANS_VTOTAL register (Ville)
> >>> v2:
> >>> * Checkpatch warning (Manasi)
> >>>
> >>> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> >>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >>> Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
> >> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >>
> >>> ---
> >>> drivers/gpu/drm/i915/display/intel_display.c | 9 +++++++--
> >>> 1 file changed, 7 insertions(+), 2 deletions(-)
> >>>
> >>> diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
> >>> index f07081815b80..15006764862b 100644
> >>> --- a/drivers/gpu/drm/i915/display/intel_display.c
> >>> +++ b/drivers/gpu/drm/i915/display/intel_display.c
> >>> @@ -15764,8 +15764,13 @@ intel_mode_valid(struct drm_device *dev,
> >>> DRM_MODE_FLAG_CLKDIV2))
> >>> return MODE_BAD;
> >>>
> >>> - if (INTEL_GEN(dev_priv) >= 9 ||
> >>> - IS_BROADWELL(dev_priv) || IS_HASWELL(dev_priv)) {
> >>> + if (INTEL_GEN(dev_priv) >= 11) {
> >>> + hdisplay_max = 16384;
> >>> + vdisplay_max = 8192;
> >>> + htotal_max = 16384;
> >>> + vtotal_max = 8192;
> >>> + } else if (INTEL_GEN(dev_priv) >= 9 ||
> >>> + IS_BROADWELL(dev_priv) || IS_HASWELL(dev_priv)) {
> >>> hdisplay_max = 8192; /* FDI max 4096 handled elsewhere */
> >>> vdisplay_max = 4096;
> >>> htotal_max = 8192;
> >>> --
> >>> 2.19.1
> >> --
> >> Ville Syrjälä
> >> Intel
>
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-09-16 19:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 20:22 [PATCH v4 1/2] drm/i915/display/icl: Bump up the hdisplay and vdisplay as per transcoder limits Manasi Navare
2019-07-12 20:22 ` [PATCH v4 2/2] drm/i915/display/icl: Bump up the plane/fb height Manasi Navare
2019-07-12 20:30 ` Ville Syrjälä
2019-07-12 20:38 ` [PATCH v5] " Manasi Navare
2019-07-12 20:29 ` [PATCH v4 1/2] drm/i915/display/icl: Bump up the hdisplay and vdisplay as per transcoder limits Ville Syrjälä
2019-07-29 19:17 ` Manasi Navare
2019-09-13 13:36 ` Maarten Lankhorst
2019-09-16 19:19 ` Manasi Navare [this message]
2019-09-17 10:55 ` Maarten Lankhorst
2019-07-12 21:24 ` ✓ Fi.CI.BAT: success for series starting with [v4,1/2] drm/i915/display/icl: Bump up the hdisplay and vdisplay as per transcoder limits (rev2) Patchwork
2019-07-14 16:12 ` ✓ Fi.CI.IGT: " 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=20190916191859.GA13413@intel.com \
--to=manasi.d.navare@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.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