Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: ville.syrjala@linux.intel.com, jani.nikula@intel.com
Subject: [CI 00/11] drm/i915: mem/fsb/rawclk freq cleanups
Date: Fri, 14 Jun 2024 12:22:28 +0300	[thread overview]
Message-ID: <cover.1718356614.git.jani.nikula@intel.com> (raw)

The earlier series [1] had some init order issues in patch 11/14 as
noted by Ville [2].

I'll look into it, but in the mean time, here are the reviewed patches
1-10 and 14 from that series for CI, with 11-13 dropped and to be
revisited and posted later.

BR,
Jani.

[1] https://lore.kernel.org/r/cover.1717672515.git.jani.nikula@intel.com
[2] https://lore.kernel.org/r/ZmLzcsoMkt3cB48m@intel.com

Jani Nikula (11):
  drm/i915/wm: rename intel_get_cxsr_latency -> pnv_get_cxsr_latency
  drm/i915/wm: clarify logging on not finding CxSR latency config
  drm/i915/dram: separate fsb freq detection from mem freq
  drm/i915/dram: split out pnv DDR3 detection
  drm/i915/dram: rearrange mem freq init
  drm/i915/gt: remove mem freq from gt debugfs
  drm/i915: convert fsb_freq and mem_freq to kHz
  drm/i915: extend the fsb_freq initialization to more platforms
  drm/i915: use i9xx_fsb_freq() for GT clock frequency
  drm/i915/cdclk: use i9xx_fsb_freq() for rawclk_freq initialization
  drm/i915: move comments about FSB straps to proper place

 drivers/gpu/drm/i915/display/i9xx_wm.c        |  27 +--
 drivers/gpu/drm/i915/display/intel_cdclk.c    |  57 +----
 .../gpu/drm/i915/gt/intel_gt_clock_utils.c    |   3 +-
 drivers/gpu/drm/i915/gt/intel_gt_pm_debugfs.c |   1 -
 drivers/gpu/drm/i915/gt/intel_rps.c           |  11 +-
 drivers/gpu/drm/i915/soc/intel_dram.c         | 212 +++++++++++-------
 drivers/gpu/drm/i915/soc/intel_dram.h         |   1 +
 7 files changed, 151 insertions(+), 161 deletions(-)

-- 
2.39.2


             reply	other threads:[~2024-06-14  9:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-14  9:22 Jani Nikula [this message]
2024-06-14  9:22 ` [CI 01/11] drm/i915/wm: rename intel_get_cxsr_latency -> pnv_get_cxsr_latency Jani Nikula
2024-06-14  9:22 ` [CI 02/11] drm/i915/wm: clarify logging on not finding CxSR latency config Jani Nikula
2024-06-14  9:22 ` [CI 03/11] drm/i915/dram: separate fsb freq detection from mem freq Jani Nikula
2024-06-14  9:22 ` [CI 04/11] drm/i915/dram: split out pnv DDR3 detection Jani Nikula
2024-06-14  9:22 ` [CI 05/11] drm/i915/dram: rearrange mem freq init Jani Nikula
2024-06-14  9:22 ` [CI 06/11] drm/i915/gt: remove mem freq from gt debugfs Jani Nikula
2024-06-14  9:22 ` [CI 07/11] drm/i915: convert fsb_freq and mem_freq to kHz Jani Nikula
2024-06-14  9:22 ` [CI 08/11] drm/i915: extend the fsb_freq initialization to more platforms Jani Nikula
2024-06-14  9:22 ` [CI 09/11] drm/i915: use i9xx_fsb_freq() for GT clock frequency Jani Nikula
2024-06-14  9:22 ` [CI 10/11] drm/i915/cdclk: use i9xx_fsb_freq() for rawclk_freq initialization Jani Nikula
2024-06-14  9:22 ` [CI 11/11] drm/i915: move comments about FSB straps to proper place Jani Nikula
2024-06-14 10:00 ` ✓ Fi.CI.BAT: success for drm/i915: mem/fsb/rawclk freq cleanups (rev3) Patchwork
2024-06-14 10:01 ` ✗ Fi.CI.SPARSE: warning " Patchwork
2024-06-15 20:11 ` ✗ Fi.CI.IGT: failure " 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=cover.1718356614.git.jani.nikula@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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