All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Chris Wilson <chris@chris-wilson.co.uk>
Cc: Yadav Jyoti <jyoti.r.yadav@intel.com>,
	IGT development <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t 1/2] [CI] tests/pm_backlight.c: Fix brightness failure with system suspend
Date: Thu, 18 Oct 2018 17:16:48 +0300	[thread overview]
Message-ID: <878t2viblb.fsf@intel.com> (raw)
In-Reply-To: <87bm7ribny.fsf@intel.com>

On Thu, 18 Oct 2018, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Wed, 17 Oct 2018, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
>> On Wed, Oct 17, 2018 at 11:44 AM Chris Wilson <chris@chris-wilson.co.uk> wrote:
>>>
>>> Quoting Jyoti Yadav (2018-10-17 10:13:20)
>>> > This patch tries to fix the faliure occuring during subtest
>>> > "fade_with_suspend". Failure is occuring because, brightness
>>> > value is being checked before driver initializes fully after resume.
>>> >
>>> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107847
>>> > Signed-off-by: Jyoti Yadav <jyoti.r.yadav@intel.com>
>>> > ---
>>> >  tests/pm_backlight.c | 1 +
>>> >  1 file changed, 1 insertion(+)
>>> >
>>> > diff --git a/tests/pm_backlight.c b/tests/pm_backlight.c
>>> > index 32808cd..ec047b3 100644
>>> > --- a/tests/pm_backlight.c
>>> > +++ b/tests/pm_backlight.c
>>> > @@ -183,6 +183,7 @@ test_fade_with_suspend(struct context *context, igt_output_t *output)
>>> >         igt_require(igt_wait_for_pm_status(IGT_RUNTIME_PM_STATUS_SUSPENDED));
>>> >
>>> >         igt_system_suspend_autoresume(SUSPEND_STATE_MEM, SUSPEND_TEST_NONE);
>>> > +       igt_require(igt_wait_for_pm_status(IGT_RUNTIME_PM_STATUS_ACTIVE));
>>>
>>> Why would the device be active on system resume if it was asleep
>>> beforehand? In fact, that sounds like the opposite of what we would like
>>> ;)
>>
>> This also looks like papering over a kernel bug I think. Or a test
>> bug. Doing an igt_require after we've done a rather expensive
>> operation already (suspend/resume cycle) is definitely not correct -
>> we should know what should work, not dynamically skip the test if it
>> turns out it didn't work.
>
> It's a test bug.
>
> How about just
>
> diff --git a/tests/pm_backlight.c b/tests/pm_backlight.c
> index 32808cdf6ca4..702ee046d5cb 100644
> --- a/tests/pm_backlight.c
> +++ b/tests/pm_backlight.c
> @@ -177,9 +177,6 @@ test_fade_with_suspend(struct context *context, igt_output_t *output)
>  {
>  	igt_require(igt_setup_runtime_pm());
>  
> -	kmstest_set_connector_dpms(output->display->drm_fd,
> -				   output->config.connector,
> -				   DRM_MODE_DPMS_OFF);
> -  	igt_require(igt_wait_for_pm_status(IGT_RUNTIME_PM_STATUS_SUSPENDED));
>  
>  	igt_system_suspend_autoresume(SUSPEND_STATE_MEM, SUSPEND_TEST_NONE);

I sneaked in another "-" line there ;)

BR,
Jani.

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2018-10-18 14:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-17  9:13 [igt-dev] [PATCH i-g-t 1/2] [CI] tests/pm_backlight.c: Fix brightness failure with system suspend Jyoti Yadav
2018-10-17  9:13 ` [igt-dev] [PATCH i-g-t 2/2] [CI] HAX: Adding test to fast feedback testlist Jyoti Yadav
2018-10-17  9:42 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2,CI] tests/pm_backlight.c: Fix brightness failure with system suspend Patchwork
2018-10-17  9:44 ` [igt-dev] [PATCH i-g-t 1/2] [CI] " Chris Wilson
2018-10-17 14:19   ` Daniel Vetter
2018-10-18 14:15     ` Jani Nikula
2018-10-18 14:16       ` Jani Nikula [this message]
2018-10-17 12:03 ` [igt-dev] ✗ Fi.CI.IGT: failure for series starting with [i-g-t,1/2,CI] " Patchwork
2018-10-18 15:09 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2,CI] tests/pm_backlight.c: Fix brightness failure with system suspend (rev2) Patchwork
2018-10-18 20:56 ` [igt-dev] ✓ 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=878t2viblb.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jyoti.r.yadav@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 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.