Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: <intel-gfx@lists.freedesktop.org>
Cc: Jani Nikula <jani.nikula@intel.com>
Subject: Re: [Intel-gfx] [PATCH v5 0/7] drm/i915: Media freq factor and per-gt enhancements/fixes
Date: Wed, 11 May 2022 21:38:10 -0700	[thread overview]
Message-ID: <878rr774ct.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <cover.1652320806.git.ashutosh.dixit@intel.com>

On Wed, 11 May 2022 19:32:13 -0700, Ashutosh Dixit wrote:
>
> Some recent Intel dGfx platforms allow media IP to work at a different
> frequency from the base GT. This patch series exposes sysfs controls for
> this functionality in the new per-gt sysfs. Some enhancements and fixes to
> previous per-gt functionality are also included to complete the new
> functionality:
> * Patches 1 and 2 implement basic sysfs controls for media freq
> * Patch 3 extends previous pcode functions for multiple gt's
> * Patch 4 inits pcode on different gt's
> * Patch 5 adds a couple of pcode helpers
> * Patch 6 uses the new pcode functions to retrieve media RP0/RPn freq
> * Patch 7 fixes memory leaks in the previous per-gt sysfs implementation
>   and some code refactoring

In this v5 I have dropped the last two patches of the v4 series, these
ones:

[PATCH 7/8] drm/i915/gt: Expose per-gt RPS defaults in sysfs
[PATCH 8/8] drm/i915/gt: Expose default value for media_freq_factor in per-gt sysfs

Because these need more work based on the review comments. If this series
is merged I will submit these patches as a separate series, otherwise I
will re-add them to this series and resubmit (due to dependence between
this series and those patches).

Apart from this, I believe I have addressed all previous review comments on
the patches in this series.

Thanks for reviewing,
Ashutosh

  parent reply	other threads:[~2022-05-12  4:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-12  2:32 [Intel-gfx] [PATCH v5 0/7] drm/i915: Media freq factor and per-gt enhancements/fixes Ashutosh Dixit
2022-05-12  2:32 ` [Intel-gfx] [PATCH 1/7] drm/i915: Introduce has_media_ratio_mode Ashutosh Dixit
2022-05-12  2:32 ` [Intel-gfx] [PATCH 2/7] drm/i915/gt: Add media freq factor to per-gt sysfs Ashutosh Dixit
2022-05-12  2:32 ` [Intel-gfx] [PATCH 3/7] drm/i915/pcode: Extend pcode functions for multiple gt's Ashutosh Dixit
2022-05-12  7:56   ` Tvrtko Ursulin
2022-05-12 10:36   ` Jani Nikula
2022-05-12 18:22     ` Dixit, Ashutosh
2022-05-12  2:32 ` [Intel-gfx] [PATCH 4/7] drm/i915/pcode: Init pcode on different gt's Ashutosh Dixit
2022-05-12  2:32 ` [Intel-gfx] [PATCH 5/7] drm/i915/pcode: Add a couple of pcode helpers Ashutosh Dixit
2022-05-12  2:32 ` [Intel-gfx] [PATCH 6/7] drm/i915/gt: Add media RP0/RPn to per-gt sysfs Ashutosh Dixit
2022-05-12  2:32 ` [Intel-gfx] [PATCH 7/7] drm/i915/gt: Fix memory leaks in " Ashutosh Dixit
2022-05-12  2:48 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Media freq factor and per-gt enhancements/fixes (rev5) Patchwork
2022-05-12  2:48 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-05-12  4:38 ` Dixit, Ashutosh [this message]
2022-05-12  7:59   ` [Intel-gfx] [PATCH v5 0/7] drm/i915: Media freq factor and per-gt enhancements/fixes Tvrtko Ursulin
2022-05-12 18:49     ` Dixit, Ashutosh

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=878rr774ct.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@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