Intel-XE Archive on 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 v3 3/9] drm/i915/pps: only touch the vlv_ members on VLV/CHV
Date: Thu, 19 Sep 2024 12:13:46 +0300	[thread overview]
Message-ID: <87jzf89fat.fsf@intel.com> (raw)
In-Reply-To: <ZusmX8cRJHIKRAx8@intel.com>

On Wed, 18 Sep 2024, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Wed, Sep 18, 2024 at 08:47:43PM +0300, Jani Nikula wrote:
>> diff --git a/drivers/gpu/drm/i915/display/intel_pps.c b/drivers/gpu/drm/i915/display/intel_pps.c
>> index 2d8d911988ab..649dc6ad2278 100644
>> --- a/drivers/gpu/drm/i915/display/intel_pps.c
>> +++ b/drivers/gpu/drm/i915/display/intel_pps.c
>> @@ -472,16 +472,17 @@ void intel_pps_reset_all(struct intel_display *display)
>>  	for_each_intel_dp(display->drm, encoder) {
>>  		struct intel_dp *intel_dp = enc_to_intel_dp(encoder);
>>  
>> -		drm_WARN_ON(display->drm,
>> -			    intel_dp->pps.vlv_active_pipe != INVALID_PIPE);
>> +		if (IS_VALLEYVIEW(dev_priv) || IS_CHERRYVIEW(dev_priv))
>> +			drm_WARN_ON(display->drm,
>> +				    intel_dp->pps.vlv_active_pipe != INVALID_PIPE);
>
> Might make sense to just split this whole function
> into vlv/chv vs. bxt/glk versions. It's called from
> platform specific code only so each caller knows
> which one it wants.

Agreed. Patch on the list [1].

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

Many thanks, pushed to din.

BR,
Jani.


[1] https://lore.kernel.org/r/20240919090427.1859032-1-jani.nikula@intel.com


-- 
Jani Nikula, Intel

  reply	other threads:[~2024-09-19  9:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-18 17:47 [PATCH v3 0/9] drm/i915/pps: hide VLV/CHV PPS pipe stuff inside intel_pps.c Jani Nikula
2024-09-18 17:47 ` [PATCH v3 1/9] drm/i915/pps: add vlv_ prefix to pps_pipe and active_pipe members Jani Nikula
2024-09-18 17:47 ` [PATCH v3 2/9] drm/i915/pps: add bxt_ prefix to pps_reset Jani Nikula
2024-09-18 17:47 ` [PATCH v3 3/9] drm/i915/pps: only touch the vlv_ members on VLV/CHV Jani Nikula
2024-09-18 19:13   ` Ville Syrjälä
2024-09-19  9:13     ` Jani Nikula [this message]
2024-09-18 17:47 ` [PATCH v3 4/9] drm/i915/pps: add vlv_pps_pipe_init() Jani Nikula
2024-09-18 17:47 ` [PATCH v3 5/9] drm/i915/pps: add vlv_pps_pipe_reset() Jani Nikula
2024-09-18 17:47 ` [PATCH v3 6/9] drm/i915/pps: add vlv_pps_port_disable() Jani Nikula
2024-09-18 17:47 ` [PATCH v3 7/9] drm/i915/pps: rename vlv_pps_init() to vlv_pps_port_enable_unlocked() Jani Nikula
2024-09-18 17:47 ` [PATCH v3 8/9] drm/i915/pps: add vlv_pps_backlight_initial_pipe() Jani Nikula
2024-09-18 17:47 ` [PATCH v3 9/9] drm/i915/pps: move vlv_active_pipe() to intel_pps.c Jani Nikula
2024-09-18 22:21 ` ✓ CI.Patch_applied: success for drm/i915/pps: hide VLV/CHV PPS pipe stuff inside intel_pps.c (rev2) Patchwork
2024-09-18 22:22 ` ✓ CI.checkpatch: " Patchwork
2024-09-18 22:25 ` ✓ CI.KUnit: " Patchwork
2024-09-18 22:38 ` ✓ CI.Build: " Patchwork
2024-09-18 22:41 ` ✓ CI.Hooks: " Patchwork
2024-09-18 22:42 ` ✗ CI.checksparse: warning " Patchwork
2024-09-18 23:05 ` ✓ CI.BAT: success " Patchwork
2024-09-19 12:39 ` ✗ CI.FULL: 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=87jzf89fat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox