From: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
To: intel-gfx@lists.freedesktop.org, jani.nikula@intel.com
Subject: [Intel-gfx] [V2 0/1] drm/i915/debugfs: New debugfs for display clock frequencies
Date: Wed, 12 Apr 2023 16:11:51 +0530 [thread overview]
Message-ID: <20230412104152.828326-1-bhanuprakash.modem@intel.com> (raw)
Instead of mixing display & non-display stuff together, move
display specific clock info to new debugfs. This patch will
create a new debugfs "i915_cdclk_info" to expose Current & Max
cdclk and Max pixel clock frequency info.
Test-with: 20230412103448.826946-1-bhanuprakash.modem@intel.com
Bhanuprakash Modem (1):
drm/i915/debugfs: New debugfs for display clock frequencies
drivers/gpu/drm/i915/display/intel_cdclk.c | 25 +++++++++++++++++++
drivers/gpu/drm/i915/display/intel_cdclk.h | 1 +
.../drm/i915/display/intel_display_debugfs.c | 1 +
3 files changed, 27 insertions(+)
--
2.40.0
next reply other threads:[~2023-04-12 10:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 10:41 Bhanuprakash Modem [this message]
2023-04-12 10:41 ` [Intel-gfx] [V2 1/1] drm/i915/debugfs: New debugfs for display clock frequencies Bhanuprakash Modem
2023-04-12 11:12 ` Jani Nikula
2023-04-13 10:34 ` Jani Nikula
2023-04-13 11:45 ` [Intel-gfx] [V3 " Bhanuprakash Modem
2023-04-14 7:14 ` Jani Nikula
2023-04-12 12:42 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2023-04-12 12:51 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-04-12 21:06 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-04-13 14:45 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/debugfs: New debugfs for display clock frequencies (rev2) Patchwork
2023-04-13 14:55 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-04-13 18:41 ` [Intel-gfx] ✓ 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=20230412104152.828326-1-bhanuprakash.modem@intel.com \
--to=bhanuprakash.modem@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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