All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 07/11] drm/i915/pps: pass intel_dp to pps_name()
Date: Tue, 03 Sep 2024 17:32:35 +0300	[thread overview]
Message-ID: <87le08u7ss.fsf@intel.com> (raw)
In-Reply-To: <ZtcCKQrGqjCMRl62@intel.com>

On Tue, 03 Sep 2024, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Fri, Aug 30, 2024 at 01:15:44PM +0300, Jani Nikula wrote:
>> Currently all of intel_pps.c passes struct intel_dp around. Do the same
>> with pps_name() instead of passing both struct drm_i915_private and
>> struct intel_pps.
>> 
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>>  drivers/gpu/drm/i915/display/intel_pps.c | 61 +++++++++++++-----------
>>  1 file changed, 32 insertions(+), 29 deletions(-)
>> 
>> diff --git a/drivers/gpu/drm/i915/display/intel_pps.c b/drivers/gpu/drm/i915/display/intel_pps.c
>> index 68141af4da54..1e87ce95c85d 100644
>> --- a/drivers/gpu/drm/i915/display/intel_pps.c
>> +++ b/drivers/gpu/drm/i915/display/intel_pps.c
>> @@ -24,9 +24,12 @@ static void vlv_steal_power_sequencer(struct drm_i915_private *dev_priv,
>>  static void pps_init_delays(struct intel_dp *intel_dp);
>>  static void pps_init_registers(struct intel_dp *intel_dp, bool force_disable_vdd);
>>  
>> -static const char *pps_name(struct drm_i915_private *i915,
>> -			    struct intel_pps *pps)
>> +static const char *pps_name(struct intel_dp *intel_dp)
>>  {
>> +	struct intel_display *display = to_intel_display(intel_dp);
>> +	struct drm_i915_private *i915 = to_i915(display->drm);
>> +	struct intel_pps *pps = &intel_dp->pps;
>> +
>
> I've been thinking that we'd eventually turn intel_pps into some kind of
> proper object with a 1:1 relationship to the corresponding hw block.
> This is sort of going in the opposite direction, but looks trivial
> enough to deal with if/when we get to reworking intel_pps.

Right. I think there are more problematic cases than this one.

> Series is
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

Thanks, appreciated. Pushed the lot to drm-intel-next.

BR,
Jani.

-- 
Jani Nikula, Intel

  reply	other threads:[~2024-09-03 14:33 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-30 10:15 [PATCH 00/11] drm/i915/display: hdmi and dp related struct intel_display conversions Jani Nikula
2024-08-30 10:15 ` [PATCH 01/11] drm/xe/display: use xe && 0 to avoid warnings about unused variables Jani Nikula
2024-08-30 10:15 ` [PATCH 02/11] drm/i915/hdmi: convert to struct intel_display Jani Nikula
2024-08-30 10:15 ` [PATCH 03/11] drm/i915/dp: convert g4x_dp.[ch] " Jani Nikula
2024-08-30 10:15 ` [PATCH 04/11] drm/i915/dp: convert intel_dp_tunnel.[ch] " Jani Nikula
2024-08-30 10:15 ` [PATCH 05/11] drm/i915/dp: convert intel_dp_aux.[ch] " Jani Nikula
2024-08-30 10:15 ` [PATCH 06/11] drm/i915/dp: convert intel_dp_link_training.[ch] " Jani Nikula
2024-08-30 10:15 ` [PATCH 07/11] drm/i915/pps: pass intel_dp to pps_name() Jani Nikula
2024-09-03 12:33   ` Ville Syrjälä
2024-09-03 14:32     ` Jani Nikula [this message]
2024-08-30 10:15 ` [PATCH 08/11] drm/i915/pps: convert intel_pps.[ch] to struct intel_display Jani Nikula
2024-08-30 10:15 ` [PATCH 09/11] drm/i915/psr: convert intel_psr.[ch] " Jani Nikula
2024-08-30 10:15 ` [PATCH 10/11] drm/i915/ddi: stop using dp_to_i915() Jani Nikula
2024-08-30 10:15 ` [PATCH 11/11] drm/i915/dp: hide dp_to_i915() inside intel_dp.c Jani Nikula
2024-08-30 10:24 ` ✓ CI.Patch_applied: success for drm/i915/display: hdmi and dp related struct intel_display conversions Patchwork
2024-08-30 10:25 ` ✗ CI.checkpatch: warning " Patchwork
2024-08-30 10:26 ` ✓ CI.KUnit: success " Patchwork
2024-08-30 10:38 ` ✓ CI.Build: " Patchwork
2024-08-30 10:40 ` ✓ CI.Hooks: " Patchwork
2024-08-30 10:42 ` ✗ CI.checksparse: warning " Patchwork
2024-08-30 11:07 ` ✓ CI.BAT: success " Patchwork
2024-08-30 11:20 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2024-08-30 11:20 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-08-30 11:27 ` ✓ Fi.CI.BAT: success " Patchwork
2024-08-30 22:38 ` ✗ CI.FULL: failure " Patchwork
2024-09-01  2:10 ` ✓ Fi.CI.IGT: success " 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=87le08u7ss.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --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 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.