Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
	"kamil.konieczny@linux.intel.com"
	<kamil.konieczny@linux.intel.com>
Cc: "Konieczny, Kamil" <kamil.konieczny@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] lib/i915: Add a helper lib to read mmio registers via ioctl
Date: Fri, 25 Aug 2023 17:41:34 +0000	[thread overview]
Message-ID: <6cc0f9cf9f0ff5dbaa1acdd107e50b6a84f4fc26.camel@intel.com> (raw)
In-Reply-To: <97e776c356d5a7b7bc7a78423e4f0502c97810e4.camel@intel.com>

On Fri, 2023-08-25 at 10:25 -0700, Teres Alexis, Alan Previn wrote:
> > > -	do_ioctl(drm_fd, DRM_IOCTL_I915_REG_READ, &rr);
> > > +	i915_reg_read_ioctl(drm_fd, 0x2358, &val);
> > ----------------------------------- ^^^^^^
> > Maybe define it at i915_mmio_reg.h ?
> > 
> > #define MMIO_REG_RENDER_RING_TIMESTAMP 0x2358
> > 
> alan: yes - my bad - i should have done that up front.
Just realized this thing is used/defined in a few places (below is the grep)
but i guess the right place would be lib/intel_reg.h with all the others?
I also feel we dont need the "MMIO_REG" in front (like others in intel_reg.h).
I'll re-rev and we can take a 2nd look. Thanks in advance.

   tests/i915/i915_pm_rpm.c:1862:	i915_reg_read_ioctl(drm_fd, 0x2358, &val);
   tests/i915/gem_reg_read.c:57:#define RENDER_RING_TIMESTAMP 0x2358
   tests/i915/gem_ctx_isolation.c:230:	{ "RCS timestamp", GEN6, ~0u, 0x2358 },
   
   tests/xe/xe_mmio.c:23:#define RCS_TIMESTAMP 0x2358
   
   lib/intel_reg.h:462:#define TIMESTAMP_QW           0x2358
   tools/intel_forcewaked.c:62:	return (intel_register_read(mmio_data, 0x2358) != 0);
   tools/i915-perf/i915_perf_recorder.c:626:#define RENDER_RING_TIMESTAMP 0x2358
   

      reply	other threads:[~2023-08-25 17:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15 17:36 [igt-dev] [PATCH i-g-t] lib/i915: Add a helper lib to read mmio registers via ioctl Alan Previn
2023-08-15 18:11 ` [igt-dev] ○ CI.xeBAT: info for " Patchwork
2023-08-15 18:25 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-08-15 20:13 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-08-16 14:27 ` [igt-dev] [PATCH i-g-t] " Kamil Konieczny
2023-08-17 13:23   ` Dixit, Ashutosh
2023-08-17 17:12     ` Kamil Konieczny
2023-08-25 17:19       ` Teres Alexis, Alan Previn
2023-08-25 17:25   ` Teres Alexis, Alan Previn
2023-08-25 17:41     ` Teres Alexis, Alan Previn [this message]

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=6cc0f9cf9f0ff5dbaa1acdd107e50b6a84f4fc26.camel@intel.com \
    --to=alan.previn.teres.alexis@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@intel.com \
    --cc=kamil.konieczny@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