From: Imre Deak <imre.deak@intel.com>
To: "Gupta, Anshuman" <anshuman.gupta@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] ✗ Fi.CI.BAT: failure for igt/i915/i915_pm_lpsp enable pm_lpsp for platforms till Gen11 v2
Date: Wed, 10 Apr 2019 18:55:24 +0300 [thread overview]
Message-ID: <20190410155524.GD18457@ideak-desk.fi.intel.com> (raw)
In-Reply-To: <c18784fc-54e5-a62a-7ece-f372afceeb70@intel.com>
On Tue, Apr 09, 2019 at 06:11:27PM +0530, Gupta, Anshuman wrote:
> Hi Imre ,
> Could you please review the i915_pm_lpsp series.
> "https://patchwork.freedesktop.org/series/59048/"
>
> There is non-edp subtest igt failure for broxton.
> "https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_2797/fi-bxt-j4205/igt@i915_pm_lpsp@non-edp.html"
>
> This broxton machine has a DP1 connector and connected on Pipe A and to
> DDI A. (https://intel-gfx-ci.01.org/hardware/fi-bxt-j4205/fi-bxt-j4205/i915_display_info.txt)
>
>
> Current implementation of lpsp_is_enabled() is checking for state of power
> well 2 for gen9 and power well 3 for gen 11, these power well should be
> turned off in order to lpsp enabled.
>
> But as above broxton machine has connected to port DDI A, that could be the
> reason power well 2 is not active and non-edp igt subtest get failed on this
> machine.
>
> What should be the correct way to check lpsp_is_enabled(), could you
> please provide your suggestion.
Power well#2 is not enabled when the test fails, which is expected for
any outputs on DDI-A regardless of the output being eDP or not.
So the test is broken with its assumption that only eDP outputs will
leave PW#2 disabled.
To fix that You need to determine if the enabled output (regardless
whether it's DP/eDP or HDMI) is using pipe A/port A and expect PW#2 to
be disabled if so. You can use i915_display_info to get at the port the
output is using.
Note that audio could also use PW#2 but the driver doesn't enable it on
port A ever (even if the display would support it).
There is also a PW#2 enable/disable sequence during/after the test exits
it would be good to know what causes that (by instrumenting the PW#2
enabling in the driver).
--Imre
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
prev parent reply other threads:[~2019-04-10 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 8:51 [igt-dev] [PATCH i-g-t v2 0/2] igt/i915/i915_pm_lpsp enable pm_lpsp for platforms till Gen11 v2 Anshuman Gupta
2019-04-05 8:51 ` [igt-dev] [PATCH i-g-t v2 1/2] igt/i915/i915_pm_lpsp enable pm_lpsp for platforms till Gen11 Anshuman Gupta
2019-04-05 8:51 ` [igt-dev] [PATCH i-g-t v2 2/2] DO_NOT_MERGE add i915_pm_lpsp subtests to CI fast feedback list Anshuman Gupta
2019-04-05 10:19 ` [igt-dev] ✗ Fi.CI.BAT: failure for igt/i915/i915_pm_lpsp enable pm_lpsp for platforms till Gen11 v2 Patchwork
2019-04-09 12:41 ` Gupta, Anshuman
2019-04-10 15:55 ` Imre Deak [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=20190410155524.GD18457@ideak-desk.fi.intel.com \
--to=imre.deak@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=igt-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox