All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/dram: replace __raw_uncore_read32() with intel_uncore_read_fw()
Date: Tue, 04 Jul 2023 18:21:12 +0300	[thread overview]
Message-ID: <87zg4bzorb.fsf@intel.com> (raw)
In-Reply-To: <iwdi2hxv55vbojf7pcmyzjfm7y4skzjgseh3mkiblpgn6tzl56@5bfqk27hrui2>

On Tue, 04 Jul 2023, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> On Tue, Jun 27, 2023 at 01:58:49PM +0300, Jani Nikula wrote:
>>The __raw_uncore_* interface is supposed to be intel_uncore.[ch]
>>internal only. Replace the remaining outside user with
>>intel_uncore_read_fw(), which is essentially the same thing.
>>
>>Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>

Thanks, pushed to din.

> as a follow up, could we perhaps move the private-to-uncore functions to
> the end of the header is a note that they shouldn't be used directly?
> AFAICS the defines would still work fine.

That's what the double underscore is supposed to mean, but people like
to abuse that. :p

BR,
Jani.


>
> Lucas De Marchi
>
>>---
>> drivers/gpu/drm/i915/soc/intel_dram.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>>diff --git a/drivers/gpu/drm/i915/soc/intel_dram.c b/drivers/gpu/drm/i915/soc/intel_dram.c
>>index 9f0651d48d41..15492b69f698 100644
>>--- a/drivers/gpu/drm/i915/soc/intel_dram.c
>>+++ b/drivers/gpu/drm/i915/soc/intel_dram.c
>>@@ -704,7 +704,7 @@ void intel_dram_edram_detect(struct drm_i915_private *i915)
>> 	if (!(IS_HASWELL(i915) || IS_BROADWELL(i915) || GRAPHICS_VER(i915) >= 9))
>> 		return;
>>
>>-	edram_cap = __raw_uncore_read32(&i915->uncore, HSW_EDRAM_CAP);
>>+	edram_cap = intel_uncore_read_fw(&i915->uncore, HSW_EDRAM_CAP);
>>
>> 	/* NB: We can't write IDICR yet because we don't have gt funcs set up */
>>
>>-- 
>>2.39.2
>>

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2023-07-04 15:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 10:58 [Intel-gfx] [PATCH] drm/i915/dram: replace __raw_uncore_read32() with intel_uncore_read_fw() Jani Nikula
2023-06-27 19:33 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-06-28 11:56 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-07-04 13:59 ` [Intel-gfx] [PATCH] " Lucas De Marchi
2023-07-04 15:21   ` Jani Nikula [this message]
2023-07-04 17:32 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/dram: replace __raw_uncore_read32() with intel_uncore_read_fw() (rev2) Patchwork
2023-07-04 17:45 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-07-04 23:00 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=87zg4bzorb.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.