From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Navare, Manasi D" <manasi.d.navare@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: Power management test in DP compliance suite
Date: Thu, 8 Jun 2017 20:19:50 +0300 [thread overview]
Message-ID: <20170608171950.GU12629@intel.com> (raw)
In-Reply-To: <87E1A67218970041879FDD2045F7145D06F2DBB2@ORSMSX106.amr.corp.intel.com>
On Thu, Jun 08, 2017 at 04:36:25PM +0000, Navare, Manasi D wrote:
> On Thu, Jun 08, 2017 at 12:59:23AM +0000, Navare, Manasi D wrote:
> > Hi,
> >
> > I am executing the DP compliance test suite and the only test
> > currently failing with the drm-tip + my patch
> > (https://patchwork.freedesktop.org/series/25191/)
> > Is the power management test (4.4.3) where it expects the source DUT to go into Power state D3 by setting DPCD register 0x600 to 2 as requested by the test GUI and then exit to normal operation by writing 1 to that DPCD register.
> >
> > I see that in the code intel_dp_sink_dpms() with DPMS_OFF will set that register to 2 and then with DPMS on it sets it to 1, but since that happens only during encoder disable and enable, I am not sure how it will happen through this test.
> >
> > Any thoughts? Please refer to the section 4.4.3 in the CTS spec.
>
> There doesn't seem to support for automated test request for this stuff, so it has to be done manually. What we should do in the test application is ConnectorSetProperty(DPMS, OFF) + ConnectorSetProperty(DPMS, ON).
>
> But DPR 120 does not send a special power management test request, so when should the app set DPMS property OFF and ON?
Yes, so presumably the user has to manually do it.
> Is DPMS a property exposed through Connector properties?
Yes. See kmstest_connector_dpms_something() in igt.
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-06-08 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 0:59 Power management test in DP compliance suite Navare, Manasi D
2017-06-08 13:26 ` Ville Syrjälä
2017-06-08 16:36 ` Navare, Manasi D
2017-06-08 17:19 ` 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=20170608171950.GU12629@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=manasi.d.navare@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