From: Ashutosh Dixit <ashutosh.dixit@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org, Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [Intel-gfx] [PATCH 0/3] i915: freq caps and perf_limit_reasons changes for MTL
Date: Fri, 9 Sep 2022 17:11:59 -0700 [thread overview]
Message-ID: <20220910001202.1733349-1-ashutosh.dixit@intel.com> (raw)
Since https://patchwork.freedesktop.org/series/107908/ is now merged,
rebase this series on latest drm-tip and post a clean series.
Ashutosh Dixit (2):
drm/i915/mtl: PERF_LIMIT_REASONS changes for MTL
drm/i915/rps: Freq caps for MTL
Tilak Tangudu (1):
drm/i915/debugfs: Add perf_limit_reasons in debugfs
drivers/gpu/drm/i915/gt/intel_gt.c | 6 +++
drivers/gpu/drm/i915/gt/intel_gt.h | 1 +
drivers/gpu/drm/i915/gt/intel_gt_pm_debugfs.c | 31 +++++++++++++
drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.c | 6 +--
drivers/gpu/drm/i915/gt/intel_rps.c | 46 +++++++++++++++----
drivers/gpu/drm/i915/i915_reg.h | 11 +++++
6 files changed, 89 insertions(+), 12 deletions(-)
--
2.34.1
next reply other threads:[~2022-09-10 0:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-10 0:11 Ashutosh Dixit [this message]
2022-09-10 0:12 ` [Intel-gfx] [PATCH 1/3] drm/i915/debugfs: Add perf_limit_reasons in debugfs Ashutosh Dixit
2022-09-10 0:12 ` [Intel-gfx] [PATCH 2/3] drm/i915/mtl: PERF_LIMIT_REASONS changes for MTL Ashutosh Dixit
2022-09-10 0:12 ` [Intel-gfx] [PATCH 3/3] drm/i915/rps: Freq caps " Ashutosh Dixit
2022-09-10 0:44 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for i915: freq caps and perf_limit_reasons changes for MTL (rev4) Patchwork
2022-09-10 1:06 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2022-09-10 14:38 [Intel-gfx] [PATCH 0/3] i915: freq caps and perf_limit_reasons changes for MTL Ashutosh Dixit
2022-09-16 15:43 ` Rodrigo Vivi
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=20220910001202.1733349-1-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@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