Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Atwood <matthew.s.atwood@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
	<intel-gfx@lists.freedesktop.org>, <matthew.d.roper@intel.com>,
	<andi.shyti@kernel.org>
Subject: Re: [PATCH v3] drm/i915:move and rename reg_in_range_table
Date: Fri, 10 Oct 2025 14:26:26 -0700	[thread overview]
Message-ID: <aOl6AvsVUu8rRazo@msatwood-mobl> (raw)
In-Reply-To: <aOkH3NsPp8B0dTUl@intel.com>

On Fri, Oct 10, 2025 at 09:19:24AM -0400, Rodrigo Vivi wrote:
> On Fri, Oct 10, 2025 at 12:55:02PM +0300, Jani Nikula wrote:
> > On Thu, 09 Oct 2025, Matt Atwood <matthew.s.atwood@intel.com> wrote:
> > > reg_in_range_table is a useful function that is used in multiple places,
> > > and will be needed for WA_BB implementation later.
> > >
> > > Let's move this function and i915_range struct to its own file, as we are
> > > trying to move away from i915_utils files.
> > >
> > > v2: move functions to their own file
> > > v3: use correct naming convention
> > 
> > Okay, Message from the Department of Bikeshedding and Nitpicking.
> > 
> > There's really nothing mmio specific about the functionality being
> > abstracted. You have a range represented by two u32's in a struct, and a
> > function to check if another u32 is within that range.
> > 
> > The struct could just as well remain i915_range, the files could be
> > i915_range.[ch], and the function could be, say,
> > i915_range_table_contains(). IMO "mmio" makes it unnecessarily specific.
I think this would best fwiw.
> 
> hmm, I'm really sorry about that... That is my bad. I'm so bad with naming.
> 
> I suggested mmio in the name because i915_range is way to generic.
> The other extreme side.
> 
> Perhaps i915_addr_range ?
> 
> But I would be okay if the consensus is simply i915_range. 
> 
> > 
> > > +bool i915_mmio_range_table_contains(u32 addr, const struct i915_mmio_range *table)
> > 
> > Usually, the "context" parameter goes first. I get that this wasn't the
> > case before, but I'd use the opportunity to swap these around.
> 
> I just had the same feeling while reading this patch again.
> Specially because it phrases like table contain ... table first contain last...
Ack.
> 
> Sorry for not noticing it before as well.
> 
> But I was on the fence on this one because it was already like that addr,range
> and the other range infra that we consider also uses the style addr,range.
> 
> > 
> > 
> > BR,
> > Jani.
> > 
> > 
> > -- 
> > Jani Nikula, Intel

  reply	other threads:[~2025-10-10 21:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-09 21:52 [PATCH v3] drm/i915:move and rename reg_in_range_table Matt Atwood
2025-10-10  0:07 ` ✗ i915.CI.BAT: failure for drm/i915:move and rename reg_in_range_table (rev2) Patchwork
2025-10-10  9:55 ` [PATCH v3] drm/i915:move and rename reg_in_range_table Jani Nikula
2025-10-10 13:19   ` Rodrigo Vivi
2025-10-10 21:26     ` Matt Atwood [this message]
2025-10-13 23:09     ` Andi Shyti
2025-10-16 12:19       ` Rodrigo Vivi
2025-10-16 15:20         ` Jani Nikula
2025-10-16 15:26           ` Raag Jadav
2025-10-16 19:25             ` Rodrigo Vivi
2025-10-10 13:07 ` Ville Syrjälä
2025-10-10 21:23   ` Matt Atwood
2025-10-10 22:56     ` Ville Syrjälä

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=aOl6AvsVUu8rRazo@msatwood-mobl \
    --to=matthew.s.atwood@intel.com \
    --cc=andi.shyti@kernel.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=rodrigo.vivi@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