All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915: move display mutex inits to display code
Date: Tue, 07 Nov 2023 12:36:43 +0200	[thread overview]
Message-ID: <874jhxzw78.fsf@intel.com> (raw)
In-Reply-To: <20231102204846.GE5757@mdroper-desk1.amr.corp.intel.com>

On Thu, 02 Nov 2023, Matt Roper <matthew.d.roper@intel.com> wrote:
> On Thu, Nov 02, 2023 at 05:52:22PM +0200, Jani Nikula wrote:
>> The core code has no business accessing i915->display directly. These
>> could be further spread to respective files, but this is a start.
>> 
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> Reviewed-by: Matt Roper <matthew.d.roper@intel.com>

Thanks, both pushed to din.

BR,
Jani.

>
>> ---
>>  drivers/gpu/drm/i915/display/intel_display_driver.c | 6 ++++++
>>  drivers/gpu/drm/i915/i915_driver.c                  | 6 ------
>>  2 files changed, 6 insertions(+), 6 deletions(-)
>> 
>> diff --git a/drivers/gpu/drm/i915/display/intel_display_driver.c b/drivers/gpu/drm/i915/display/intel_display_driver.c
>> index 44b59ac301e6..0a5b922f2ad6 100644
>> --- a/drivers/gpu/drm/i915/display/intel_display_driver.c
>> +++ b/drivers/gpu/drm/i915/display/intel_display_driver.c
>> @@ -181,6 +181,12 @@ void intel_display_driver_early_probe(struct drm_i915_private *i915)
>>  	if (!HAS_DISPLAY(i915))
>>  		return;
>>  
>> +	mutex_init(&i915->display.backlight.lock);
>> +	mutex_init(&i915->display.audio.mutex);
>> +	mutex_init(&i915->display.wm.wm_mutex);
>> +	mutex_init(&i915->display.pps.mutex);
>> +	mutex_init(&i915->display.hdcp.hdcp_mutex);
>> +
>>  	intel_display_irq_init(i915);
>>  	intel_dkl_phy_init(i915);
>>  	intel_color_init_hooks(i915);
>> diff --git a/drivers/gpu/drm/i915/i915_driver.c b/drivers/gpu/drm/i915/i915_driver.c
>> index 80e85cadb9a2..01fd25b622d1 100644
>> --- a/drivers/gpu/drm/i915/i915_driver.c
>> +++ b/drivers/gpu/drm/i915/i915_driver.c
>> @@ -231,16 +231,10 @@ static int i915_driver_early_probe(struct drm_i915_private *dev_priv)
>>  
>>  	spin_lock_init(&dev_priv->irq_lock);
>>  	spin_lock_init(&dev_priv->gpu_error.lock);
>> -	mutex_init(&dev_priv->display.backlight.lock);
>>  
>>  	mutex_init(&dev_priv->sb_lock);
>>  	cpu_latency_qos_add_request(&dev_priv->sb_qos, PM_QOS_DEFAULT_VALUE);
>>  
>> -	mutex_init(&dev_priv->display.audio.mutex);
>> -	mutex_init(&dev_priv->display.wm.wm_mutex);
>> -	mutex_init(&dev_priv->display.pps.mutex);
>> -	mutex_init(&dev_priv->display.hdcp.hdcp_mutex);
>> -
>>  	i915_memcpy_init_early(dev_priv);
>>  	intel_runtime_pm_init_early(&dev_priv->runtime_pm);
>>  
>> -- 
>> 2.39.2
>> 

-- 
Jani Nikula, Intel

  reply	other threads:[~2023-11-07 10:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02 15:52 [Intel-gfx] [PATCH 1/2] drm/i915: move display mutex inits to display code Jani Nikula
2023-11-02 15:52 ` [Intel-gfx] [PATCH 2/2] drm/i915: move display spinlock init " Jani Nikula
2023-11-02 20:49   ` Matt Roper
2023-11-02 20:48 ` [Intel-gfx] [PATCH 1/2] drm/i915: move display mutex inits " Matt Roper
2023-11-07 10:36   ` Jani Nikula [this message]
2023-11-03  0:24 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/2] " Patchwork
2023-11-03  0:42 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-11-03 11:54 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/2] drm/i915: move display mutex inits to display code (rev2) Patchwork
2023-11-03 12:08 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-11-04  6:36 ` [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=874jhxzw78.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.d.roper@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.