From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH v2 0/4] drm/i915: Per-crtc/connector DRRS debugfs
Date: Sat, 1 Oct 2022 21:25:01 +0300 [thread overview]
Message-ID: <20221001182505.3675-1-ville.syrjala@linux.intel.com> (raw)
From: Ville Syrjälä <ville.syrjala@linux.intel.com>
Chang DRRS debugfs to be per-crtc/connector.
v2: for ci to actually run the drrs tests...
Test-with: 20220929032642.16556-1-ville.syrjala@linux.intel.com
Ville Syrjälä (4):
drm/i915: Move DRRS debugfs next to the implementation
drm/i915: Make the DRRS debugfs contents more consistent
drm/i915: Make DRRS debugfs per-crtc/connector
drm/i915: Fix locking in DRRS debugfs
.../drm/i915/display/intel_display_debugfs.c | 98 +---------------
drivers/gpu/drm/i915/display/intel_drrs.c | 108 ++++++++++++++++++
drivers/gpu/drm/i915/display/intel_drrs.h | 2 +
3 files changed, 113 insertions(+), 95 deletions(-)
--
2.35.1
next reply other threads:[~2022-10-01 18:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 18:25 Ville Syrjala [this message]
2022-10-01 18:25 ` [Intel-gfx] [PATCH v2 1/4] drm/i915: Move DRRS debugfs next to the implementation Ville Syrjala
2022-10-01 18:25 ` [Intel-gfx] [PATCH v2 2/4] drm/i915: Make the DRRS debugfs contents more consistent Ville Syrjala
2022-10-01 18:25 ` [Intel-gfx] [PATCH v2 3/4] drm/i915: Make DRRS debugfs per-crtc/connector Ville Syrjala
2022-10-01 18:25 ` [Intel-gfx] [PATCH v2 4/4] drm/i915: Fix locking in DRRS debugfs Ville Syrjala
2022-10-01 19:02 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Per-crtc/connector DRRS debugfs (rev2) Patchwork
2022-10-01 19:26 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-10-01 23:23 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-10-03 8:37 ` Ville Syrjälä
2022-10-03 8:44 ` Sarvela, Tomi P
2022-10-03 8:48 ` Ville Syrjälä
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=20221001182505.3675-1-ville.syrjala@linux.intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@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