From: Gustavo Sousa <gustavo.sousa@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
<intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>
Cc: "Matt Roper" <matthew.d.roper@intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Subject: Re: [PATCH v5 1/3] drm/i915/display: Convert intel_bw.c internally to intel_display
Date: Thu, 13 Mar 2025 10:10:32 -0300 [thread overview]
Message-ID: <174187143210.91144.10112790943902906895@intel.com> (raw)
In-Reply-To: <87zfhrfnqj.fsf@intel.com>
Quoting Jani Nikula (2025-03-11 15:04:04-03:00)
>On Tue, 11 Mar 2025, Gustavo Sousa <gustavo.sousa@intel.com> wrote:
>> diff --git a/drivers/gpu/drm/i915/display/intel_bw.c b/drivers/gpu/drm/i915/display/intel_bw.c
>> index 048be287224774110d94fe2944daa580d8dc20a6..6f805af32926d3608929655de97699747d7a5798 100644
>> --- a/drivers/gpu/drm/i915/display/intel_bw.c
>> +++ b/drivers/gpu/drm/i915/display/intel_bw.c
>> @@ -39,14 +39,15 @@ struct intel_qgv_info {
>> u8 deinterleave;
>> };
>>
>> -static int dg1_mchbar_read_qgv_point_info(struct drm_i915_private *dev_priv,
>> +static int dg1_mchbar_read_qgv_point_info(struct intel_display *display,
>> struct intel_qgv_point *sp,
>> int point)
>> {
>> + struct drm_i915_private *i915 = to_i915(display->drm);
>
>This is reviewed already, and I'm not requesting changes, but for future
>reference, I tend to keep the dev_priv name where it's already being
>used. We don't really benefit from dev_priv -> i915 conversions anymore
>in display, they'll all need to be removed eventually, but this causes
>extra churn where none is required.
Yep. Makes sense. I'll keep that in mind in eventual future conversions
that I work on.
Thanks.
--
Gustavo Sousa
>
>> u32 dclk_ratio, dclk_reference;
>> u32 val;
>>
>> - val = intel_uncore_read(&dev_priv->uncore, SA_PERF_STATUS_0_0_0_MCHBAR_PC);
>> + val = intel_uncore_read(&i915->uncore, SA_PERF_STATUS_0_0_0_MCHBAR_PC);
>
>Like above.
>
>
>BR,
>Jani.
>
>
>--
>Jani Nikula, Intel
next prev parent reply other threads:[~2025-03-13 13:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 17:04 [PATCH v5 0/3] drm/i915/xe3lpd: Update bandwidth parameters Gustavo Sousa
2025-03-11 17:04 ` [PATCH v5 1/3] drm/i915/display: Convert intel_bw.c internally to intel_display Gustavo Sousa
2025-03-11 18:04 ` Jani Nikula
2025-03-13 13:10 ` Gustavo Sousa [this message]
2025-03-14 21:17 ` Matt Roper
2025-03-14 21:29 ` Gustavo Sousa
2025-03-11 17:04 ` [PATCH v5 2/3] drm/i915/display: Convert intel_bw.c externally " Gustavo Sousa
2025-03-11 17:04 ` [PATCH v5 3/3] drm/i915/xe3lpd: Update bandwidth parameters Gustavo Sousa
2025-03-11 18:38 ` ✓ CI.Patch_applied: success for drm/i915/xe3lpd: Update bandwidth parameters (rev5) Patchwork
2025-03-11 18:39 ` ✓ CI.checkpatch: " Patchwork
2025-03-11 18:40 ` ✓ CI.KUnit: " Patchwork
2025-03-11 18:57 ` ✓ CI.Build: " Patchwork
2025-03-11 18:59 ` ✓ CI.Hooks: " Patchwork
2025-03-11 19:01 ` ✗ CI.checksparse: warning " Patchwork
2025-03-11 19:22 ` ✓ Xe.CI.BAT: success " Patchwork
2025-03-12 10:50 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-13 14:02 ` Gustavo Sousa
2025-03-13 14:40 ` [PATCH v5 0/3] drm/i915/xe3lpd: Update bandwidth parameters Gustavo Sousa
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=174187143210.91144.10112790943902906895@intel.com \
--to=gustavo.sousa@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=matthew.d.roper@intel.com \
--cc=ville.syrjala@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