Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>, intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 0/2] i915: Extract, polish, and document multicast handling
Date: Mon, 13 Jun 2022 11:13:09 +0300	[thread overview]
Message-ID: <87mtehyoa2.fsf@intel.com> (raw)
In-Reply-To: <20220611005711.596098-1-matthew.d.roper@intel.com>

On Fri, 10 Jun 2022, Matt Roper <matthew.d.roper@intel.com> wrote:
> Multicast/replicated (MCR) registers on Intel hardware are a purely
> GT-specific concept.  Rather than leaving MCR register handling spread
> across several places throughout the driver (intel_uncore.c, intel_gt.c,
> etc.) with confusing combinations of handler functions living in
> different namespaces, let's consolidate it all into a single place
> (intel_gt_mcr.c) and provide a more consistent and clearly-documented
> interface for the rest of the driver to access such registers:

I don't have the time for review, but overall this seems like a nice
cleanup. Ack.

As to documentation, I think usually documenting static functions using
kernel-doc is excessive, and a short regular comment might suffice. On
the other hand, the nice documentation doesn't show up anywhere, because
you also need to bolt it to some .rst!

BR,
Jani.


>
>  * intel_gt_mcr_read -- unicast read from specific instance
>  * intel_gt_mcr_read_any[_fw] -- unicast read from any non-terminated
>    instance
>  * intel_gt_mcr_unicast_write -- unicast write to specific instance
>  * intel_gt_mcr_multicast_write[_fw] -- multicast write to all instances
>
> Matt Roper (2):
>   drm/i915/gt: Move multicast register handling to a dedicated file
>   drm/i915/gt: Cleanup interface for MCR operations
>
>  drivers/gpu/drm/i915/Makefile               |   1 +
>  drivers/gpu/drm/i915/gem/i915_gem_stolen.c  |   3 +-
>  drivers/gpu/drm/i915/gt/intel_engine_cs.c   |  36 +-
>  drivers/gpu/drm/i915/gt/intel_gt.c          | 297 +-----------
>  drivers/gpu/drm/i915/gt/intel_gt.h          |  15 -
>  drivers/gpu/drm/i915/gt/intel_gt_debugfs.c  |   3 +-
>  drivers/gpu/drm/i915/gt/intel_gt_mcr.c      | 483 ++++++++++++++++++++
>  drivers/gpu/drm/i915/gt/intel_gt_mcr.h      |  34 ++
>  drivers/gpu/drm/i915/gt/intel_region_lmem.c |   5 +-
>  drivers/gpu/drm/i915/gt/intel_workarounds.c |   9 +-
>  drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c  |   3 +-
>  drivers/gpu/drm/i915/i915_drv.h             |   2 -
>  drivers/gpu/drm/i915/intel_uncore.c         | 112 -----
>  drivers/gpu/drm/i915/intel_uncore.h         |   8 -
>  14 files changed, 551 insertions(+), 460 deletions(-)
>  create mode 100644 drivers/gpu/drm/i915/gt/intel_gt_mcr.c
>  create mode 100644 drivers/gpu/drm/i915/gt/intel_gt_mcr.h

-- 
Jani Nikula, Intel Open Source Graphics Center

  parent reply	other threads:[~2022-06-13  8:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-11  0:57 [Intel-gfx] [PATCH 0/2] i915: Extract, polish, and document multicast handling Matt Roper
2022-06-11  0:57 ` [Intel-gfx] [PATCH 1/2] drm/i915/gt: Move multicast register handling to a dedicated file Matt Roper
2022-06-11  0:57 ` [Intel-gfx] [PATCH 2/2] drm/i915/gt: Cleanup interface for MCR operations Matt Roper
2022-06-13  8:13 ` Jani Nikula [this message]
2022-06-13 22:11 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for i915: Extract, polish, and document multicast handling Patchwork
2022-06-13 22:11 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-06-13 22:35 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-06-14 23:17 ` [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=87mtehyoa2.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.d.roper@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