All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] i915/pm_backlight: ensure driver is loaded before checking backlight
Date: Tue, 11 Feb 2020 15:10:08 +0200	[thread overview]
Message-ID: <87wo8tz2vj.fsf@intel.com> (raw)
In-Reply-To: <158142038106.2359.2223868848546234044@skylake-alporthouse-com>

On Tue, 11 Feb 2020, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Quoting Jani Nikula (2020-02-11 11:16:34)
>> Checking the existence of the backlight interface before ensuring the
>> driver is loaded skips whenever the test is run without the driver
>> loaded. None of the tests would work properly if they were run as the
>> first thing or after tests that unload the driver.
>> 
>> Open the driver (and thus probe it as needed) as the first thing.
>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
>
>> (This is the low-hanging fruit. A proper test for skipping would be
>> based on the presence of embedded displays, not based on the presence of
>> the interface we're aiming to test.)
>
> Slightly different test idea. Here we say this is a test for particular
> interface, what you have in mind is a requirement that if available HW,
> the kernel *must* provide an interface. (I don't really like userspace
> demanding the kernel makes something available, for the cases were it
> really can't be done due to some flaw or another. From the HW vendor
> perspective, such a conformance test is understandable -- but we are
> focusing on the interfaces the kernel does expose and verifying that
> work as expected.)

That's fair. I'll drop the parenthesized paragraph before pushing.

Thanks for the reviews.

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:[~2020-02-11 13:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11 11:16 [igt-dev] [PATCH i-g-t] i915/pm_backlight: ensure driver is loaded before checking backlight Jani Nikula
2020-02-11 11:26 ` Chris Wilson
2020-02-11 13:10   ` Jani Nikula [this message]
2020-02-11 11:28 ` Petri Latvala
2020-02-11 15:34 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2020-02-13 11:19 ` [igt-dev] ✓ Fi.CI.IGT: success for i915/pm_backlight: ensure driver is loaded before checking backlight (rev2) Patchwork
2020-02-13 13:39 ` [igt-dev] [PATCH i-g-t] i915/pm_backlight: ensure driver is loaded before checking backlight Jani Nikula

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=87wo8tz2vj.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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 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.