public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Souza, Jose" <jose.souza@intel.com>
Cc: "Zhao, Yakui" <yakui.zhao@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Roper, Matthew D" <matthew.d.roper@intel.com>
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915: Remove memory frequency calculation
Date: Wed, 13 Oct 2021 22:31:39 +0300	[thread overview]
Message-ID: <YWc0GwvlY4DQz84Y@intel.com> (raw)
In-Reply-To: <e85ffbe78d15f8714e88edcdf4d3112c59ae971f.camel@intel.com>

On Wed, Oct 13, 2021 at 07:17:14PM +0000, Souza, Jose wrote:
> On Wed, 2021-10-13 at 12:32 +0300, Ville Syrjälä wrote:
> > On Tue, Oct 12, 2021 at 06:00:46PM -0700, José Roberto de Souza wrote:
> > > This memory frequency calculated is only used to check if it is zero,
> > > what is not useful as it will never actually be zero.
> > > 
> > > Also the calculation is wrong, we should be checking other bit to
> > > select the appropriate frequency multiplier while this code is stuck
> > > with a fixed multiplier.
> > 
> > I don't think the alternate ref clock was ever used.
> > At least I don't recall ever seeing it.
> > 
> > The real problem with this is that IIRC this is just the last
> > requested frequency. So on a system with SAGV this will
> > change dynamically.
> > 
> > > 
> > > So here dropping it as whole.
> > 
> > We have a second copy of this in gen6_update_ring_freq(). Rather
> > than removing one and leaving another potentially broken one behind we
> > should probably just consolidate on a single implementation.
> 
> gen6_update_ring_freq() is related to GPU frequency not memory, don't look related at all to me.
>

GPU, CPU and memory clocks are all needed there, at least on some
platforms. I forget which ones did what exactly.

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2021-10-13 19:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-13  1:00 [Intel-gfx] [PATCH v2] drm/i915: Remove memory frequency calculation José Roberto de Souza
2021-10-13  0:55 ` Souza, Jose
2021-10-13  1:20 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Remove memory frequency calculation (rev2) Patchwork
2021-10-13  1:50 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-10-13  2:54 ` [Intel-gfx] [PATCH v2] drm/i915: Remove memory frequency calculation Matt Roper
2021-10-13  8:20   ` Zhao, Yakui
2021-10-13  9:22 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Remove memory frequency calculation (rev2) Patchwork
2021-10-13  9:32 ` [Intel-gfx] [PATCH v2] drm/i915: Remove memory frequency calculation Ville Syrjälä
2021-10-13 19:17   ` Souza, Jose
2021-10-13 19:31     ` Ville Syrjälä [this message]
2021-10-13 19:38       ` Souza, Jose

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=YWc0GwvlY4DQz84Y@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jose.souza@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=yakui.zhao@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