intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [i-g-t PATCH] tests: don't skip kms_panel_fitting when non-eDP connected
Date: Wed, 23 Mar 2016 16:47:28 +0200	[thread overview]
Message-ID: <20160323144728.GT4329@intel.com> (raw)
In-Reply-To: <20160323134414.GB31168@mcvlad-wk.rb.intel.com>

On Wed, Mar 23, 2016 at 03:44:15PM +0200, Marius Vlad wrote:
> Is there a reason why other connectors do not support panel fitting?

LVDS supports it, and with this [1] DSI too. No clue why the test checks
for eDP only. What it really should be testing is the presence of the
"scaling mode" property, and then it magically works on everything.

There have also been a few half hearted attempts at adding panel fitter
support for external displays, but those didn't really go anywhere. My
plan for this is that we'd add a "fixed mode" property to all
connectors, and then the user could set that to whatever actual display
timings they want to use, and the normal mode would then provide the
pfit source size just like it does for connectors where we currently
enable the panel fitter.

[1] https://lists.freedesktop.org/archives/intel-gfx/2016-March/089786.html

> 
> Removed the check and using a HDMI connector the test passes...
> 
> On Wed, Mar 23, 2016 at 02:19:25PM +0200, Jani Nikula wrote:
> > kms_panel_fitting skips if there's a non-eDP display connected. Fix it.
> > 
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=93012
> > Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> > ---
> >  tests/kms_panel_fitting.c | 5 +++--
> >  1 file changed, 3 insertions(+), 2 deletions(-)
> > 
> > diff --git a/tests/kms_panel_fitting.c b/tests/kms_panel_fitting.c
> > index 829d9cdd0631..1f9412f6e2d5 100644
> > --- a/tests/kms_panel_fitting.c
> > +++ b/tests/kms_panel_fitting.c
> > @@ -150,8 +150,9 @@ static void test_panel_fitting(data_t *d)
> >  	for_each_connected_output(display, output) {
> >  		drmModeModeInfo *mode, native_mode;
> >  
> > -		igt_require(output->config.connector->connector_type ==
> > -			DRM_MODE_CONNECTOR_eDP);
> > +		if (output->config.connector->connector_type !=
> > +		    DRM_MODE_CONNECTOR_eDP)
> > +			continue;
> >  
> >  		pipe = output->config.pipe;
> >  		igt_output_set_pipe(output, pipe);
> > -- 
> > 2.1.4
> > 
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/intel-gfx



> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx


-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2016-03-23 14:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-23 12:19 [i-g-t PATCH] tests: don't skip kms_panel_fitting when non-eDP connected Jani Nikula
2016-03-23 13:44 ` Marius Vlad
2016-03-23 14:47   ` Ville Syrjälä [this message]

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=20160323144728.GT4329@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@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;
as well as URLs for NNTP newsgroup(s).