From: Dhinakaran Pandiyan <dhinakaran.pandiyan@gmail.com>
To: intel-gfx@lists.freedesktop.org
Cc: "Pandiyan, Dhinakaran" <dhinakaran.pandiyan@intel.com>,
"Vetter, Daniel" <daniel.vetter@intel.com>
Subject: Re: [PATCH] drm/i915: Do not do link training fallback or prune modes for eDP
Date: Thu, 17 Aug 2017 21:00:46 -0700 [thread overview]
Message-ID: <2527505.cMxGEW1dz7@dk> (raw)
In-Reply-To: <CABVU7+tQxn=jpGOKo7w3RgA8DRN7Y=cd19LDYcwSYQC=Or-37g@mail.gmail.com>
On Thursday, August 17, 2017 1:44:14 PM PDT Rodrigo Vivi wrote:
> On Thu, Aug 17, 2017 at 1:11 PM, Pandiyan, Dhinakaran
>
> <dhinakaran.pandiyan@intel.com> wrote:
> > On Thu, 2017-08-17 at 12:46 -0700, Manasi Navare wrote:
> >> On Thu, Aug 17, 2017 at 07:01:05AM +0000, Rodrigo Vivi wrote:
> >> > On Wed, Aug 16, 2017 at 11:51 PM Manasi Navare
> >> >
> >> > <[1]manasi.d.navare@intel.com> wrote:
> >> > In case of eDP because the panel has a fixed mode we cannot
> >> > link train fallback and prune modes since this results in
> >> > no modes available for eDP connector.
> >> >
> >> > What about downclock modes?!
> >>
> >> What are the downclock modes? We have seen an issue with pruning modes
> >> in case of eDP panel where we end up pruning the mode due to link train
> >> fallback and then we get an error saying "No modes available for the
> >> connector"
> >
> > fwiw I've got two laptops with eDP's having more than ten modes.
>
> those ten are probably a list of modes with scaler right?!
Yeah, Clint very graciously explained that to me after I sent the email.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-08-18 4:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 6:58 [PATCH] drm/i915: Do not do link training fallback or prune modes for eDP Manasi Navare
2017-08-17 7:01 ` Rodrigo Vivi
2017-08-17 19:46 ` Manasi Navare
2017-08-17 20:11 ` Pandiyan, Dhinakaran
2017-08-17 20:44 ` Rodrigo Vivi
2017-08-17 22:10 ` Manasi Navare
2017-08-18 4:00 ` Dhinakaran Pandiyan [this message]
2017-08-17 21:01 ` Manasi Navare
2017-08-17 21:16 ` Manasi Navare
2017-08-18 8:08 ` Daniel Vetter
2017-08-17 7:21 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-08-17 9:51 ` [PATCH] " Jani Nikula
2017-08-17 19:29 ` Manasi Navare
2017-08-17 19:28 ` Pandiyan, Dhinakaran
2017-08-17 19:42 ` Manasi Navare
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=2527505.cMxGEW1dz7@dk \
--to=dhinakaran.pandiyan@gmail.com \
--cc=daniel.vetter@intel.com \
--cc=dhinakaran.pandiyan@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.