From: Jani Nikula <jani.nikula@linux.intel.com>
To: Nemesa Garg <nemesa.garg@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v3 0/2] Enable Darkscreen Feature
Date: Wed, 13 Dec 2023 11:58:08 +0200 [thread overview]
Message-ID: <87sf46whjj.fsf@intel.com> (raw)
In-Reply-To: <20231213090641.1153030-1-nemesa.garg@intel.com>
On Wed, 13 Dec 2023, Nemesa Garg <nemesa.garg@intel.com> wrote:
> The logic checks for any black screen at pipe level and
> upon such detection prints error. Darkscreen compares the
> pixels with the compare value(0x00 - black) for the detection
> purpose. This feature can be enables/disabled through debugfs.
This does not address the feedback I've given previously. Alas, it
wasn't on intel-gfx, so I'm copy-pasting it here:
> IGT patches https://patchwork.freedesktop.org/series/125880/ .
> Kernel patches https://patchwork.freedesktop.org/series/125563/ .
The current IGT implementation proposal does this:
+ igt_set_dark_screen_detection(data.drm_fd, pipe, true);
+ test_read_crc(&data, pipe, output, tests[i].flags);
+ igt_set_dark_screen_detection(data.drm_fd, pipe, false);
It *looks* nice. But the dark screen detection is *not* reported during
or after test_read_crc(). With the current kernel implementation, only
the dark screen enable checks if there's a dark screen during enable,
and that's it. The above checks what the state was before.
The kernel and the IGT parts don't work together. You need to come up
with a plan how the hardware feature can be used to our benefit. This
falls short, even for the first phase.
The detection is sticky, so you could fathom enabling it, and checking
later if dark screen has happened during testing. But if you enable it
before you have something on screen, you'll surely flag a dark screen
detection before you've even started the test. Right?
You need to have an idea how it's going to be used in a test case where
everything is disabled in the beginning.
BR,
Jani.
>
> Nemesa Garg (2):
> drm/i915/display: Add support for darskscreen detection
> drm/i915/display: Add darkscreen debugfs entry under crtc
>
> drivers/gpu/drm/i915/Makefile | 1 +
> .../gpu/drm/i915/display/intel_darkscreen.c | 131 ++++++++++++++++++
> .../gpu/drm/i915/display/intel_darkscreen.h | 26 ++++
> .../drm/i915/display/intel_display_debugfs.c | 2 +
> .../drm/i915/display/intel_display_types.h | 2 +
> drivers/gpu/drm/i915/i915_reg.h | 8 ++
> drivers/gpu/drm/xe/Makefile | 1 +
> 7 files changed, 171 insertions(+)
> create mode 100644 drivers/gpu/drm/i915/display/intel_darkscreen.c
> create mode 100644 drivers/gpu/drm/i915/display/intel_darkscreen.h
--
Jani Nikula, Intel
next prev parent reply other threads:[~2023-12-13 9:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 9:06 [PATCH v3 0/2] Enable Darkscreen Feature Nemesa Garg
2023-12-13 9:06 ` [PATCH v3 1/2] drm/i915/display: Add support for darskscreen detection Nemesa Garg
2023-12-13 10:05 ` Jani Nikula
2023-12-13 17:54 ` Rodrigo Vivi
2023-12-16 0:42 ` Matt Roper
2023-12-13 9:06 ` [PATCH v2 2/2] drm/i915/display: Add darkscreen debugfs entry under crtc Nemesa Garg
2023-12-13 9:58 ` Jani Nikula [this message]
2023-12-13 17:16 ` ✗ Fi.CI.BUILD: failure for Enable Darkscreen Feature (rev3) 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=87sf46whjj.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nemesa.garg@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).