From: Jani Nikula <jani.nikula@intel.com>
To: Gustavo Sousa <gustavo.sousa@intel.com>,
Clint Taylor <clinton.a.taylor@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v4 01/11] drm/i915/xe3lpd: Update pmdemand programming
Date: Fri, 25 Oct 2024 17:16:09 +0300 [thread overview]
Message-ID: <87zfmsp8t2.fsf@intel.com> (raw)
In-Reply-To: <172986311694.1548.11080444560306759369@gjsousa-mobl2>
On Fri, 25 Oct 2024, Gustavo Sousa <gustavo.sousa@intel.com> wrote:
> Quoting Clint Taylor (2024-10-24 19:31:04-03:00)
>>@@ -460,7 +479,8 @@ void intel_pmdemand_program_dbuf(struct drm_i915_private *i915,
>> }
>>
>> static void
>>-intel_pmdemand_update_params(const struct intel_pmdemand_state *new,
>>+intel_pmdemand_update_params(struct drm_i915_private *i915,
>>+ const struct intel_pmdemand_state *new,
>> const struct intel_pmdemand_state *old,
>> u32 *reg1, u32 *reg2, bool serialized)
>
> Jani ask been asking in other patches not to add new i915 variables or
> parameters.
Yes.
> As such, I think we should make intel_pmdemand_update_params() receive
> struct intel_display *display instead of i915. The caller can be adapted
> to simply use intel_pmdemand_update_params(&i915->display, ...).
Actually always prefer adding a local display variable instead:
struct intel_display *display = to_intel_display(...);
or
struct intel_display *display = &i915->display;
Otherwise, further struct intel_display conversions wouldn't benefit
from having the display variable available, and you end up having to fix
all the inline &i915->display again.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-10-25 14:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 22:31 [PATCH v4 00/11] drm/i915/xe3lpd: ptl display patches Clint Taylor
2024-10-24 22:31 ` [PATCH v4 01/11] drm/i915/xe3lpd: Update pmdemand programming Clint Taylor
2024-10-25 13:31 ` Gustavo Sousa
2024-10-25 14:16 ` Jani Nikula [this message]
2024-10-24 22:31 ` [PATCH v4 02/11] drm/i915/xe3lpd: Disable HDCP Line Rekeying for Xe3 Clint Taylor
2024-10-24 22:31 ` [PATCH v4 03/11] drm/i915/xe3lpd: Add check to see if edp over type c is allowed Clint Taylor
2024-10-25 5:00 ` Murthy, Arun R
2024-10-25 15:29 ` Jani Nikula
2024-10-24 22:31 ` [PATCH v4 04/11] drm/i915/ptl: Define IS_PANTHERLAKE macro Clint Taylor
2024-10-24 22:31 ` [PATCH v4 05/11] drm/i915/cx0: Extend C10 check to PTL Clint Taylor
2024-10-24 22:31 ` [PATCH v4 06/11] drm/i915/cx0: Remove bus reset after every c10 transaction Clint Taylor
2024-10-25 13:52 ` Gustavo Sousa
2024-10-24 22:31 ` [PATCH v4 07/11] drm/i915/xe3lpd: Move async flip bit to PLANE_SURF register Clint Taylor
2024-10-24 22:31 ` [PATCH v4 08/11] drm/i915/xe3: Underrun recovery does not exist post Xe2 Clint Taylor
2024-10-24 22:31 ` [PATCH v4 09/11] drm/i915/display/xe3: disable x-tiled framebuffers Clint Taylor
2024-10-24 22:31 ` [PATCH v4 10/11] drm/i915/xe3lpd: Skip disabling VRR during modeset disable Clint Taylor
2024-10-25 8:06 ` Golani, Mitulkumar Ajitkumar
2024-10-25 10:18 ` Golani, Mitulkumar Ajitkumar
2024-10-24 22:31 ` [PATCH v4 11/11] drm/i915/xe3lpd: Power request asserting/deasserting Clint Taylor
2024-10-25 13:58 ` Gustavo Sousa
2024-10-24 23:11 ` ✗ Fi.CI.SPARSE: warning for drm/i915/xe3lpd: ptl display patches (rev4) Patchwork
2024-10-24 23:39 ` ✓ Fi.CI.BAT: success " Patchwork
2024-10-25 1:34 ` ✗ 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=87zfmsp8t2.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=clinton.a.taylor@intel.com \
--cc=gustavo.sousa@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
/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