Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Bharadiya\,Pankaj" <pankaj.laxminarayan.bharadiya@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
	Wambui Karuga <wambui.karugax@gmail.com>
Subject: Re: [Intel-gfx] [PATCH 02/17] drm/i915/panel: use struct drm_device based logging
Date: Mon, 06 Apr 2020 14:07:44 +0300	[thread overview]
Message-ID: <87mu7olvnj.fsf@intel.com> (raw)
In-Reply-To: <20200406105401.GA16300@plaxmina-desktop.iind.intel.com>

On Mon, 06 Apr 2020, "Bharadiya,Pankaj" <pankaj.laxminarayan.bharadiya@intel.com> wrote:
> On Thu, Apr 02, 2020 at 02:48:04PM +0300, Jani Nikula wrote:
>> Convert all the DRM_* logging macros to the struct drm_device based
>> macros to provide device specific logging.
>> 
>> No functional changes.
>> 
>> Generated using the following semantic patch, originally written by
>> Wambui Karuga <wambui.karugax@gmail.com>, with manual fixups on top:
>> 
>> @@
>> identifier fn, T;
>> @@
>> 
>> fn(...,struct drm_i915_private *T,...) {
>> <+...
>> (
>> -DRM_INFO(
>> +drm_info(&T->drm,
>> ...)
>> |
>> -DRM_NOTE(
>> +drm_notice(&T->drm,
>> ...)
>> |
>> -DRM_ERROR(
>> +drm_err(&T->drm,
>> ...)
>> |
>> -DRM_WARN(
>> +drm_warn(&T->drm,
>> ...)
>> |
>> -DRM_DEBUG_DRIVER(
>> +drm_dbg(&T->drm,
>> ...)
>> |
>> -DRM_DEBUG_KMS(
>> +drm_dbg_kms(&T->drm,
>> ...)
>> |
>> -DRM_DEBUG_ATOMIC(
>> +drm_dbg_atomic(&T->drm,
>> ...)
>> )
>> ...+>
>> }
>> 
>> @@
>> identifier fn, T;
>> @@
>> 
>> fn(...) {
>> ...
>> struct drm_i915_private *T = ...;
>> <+...
>> (
>> -DRM_INFO(
>> +drm_info(&T->drm,
>> ...)
>> |
>> -DRM_NOTE(
>> +drm_notice(&T->drm,
>> ...)
>> |
>> -DRM_ERROR(
>> +drm_err(&T->drm,
>> ...)
>> |
>> -DRM_WARN(
>> +drm_warn(&T->drm,
>> ...)
>> |
>> -DRM_DEBUG_DRIVER(
>> +drm_dbg(&T->drm,
>> ...)
>> |
>> -DRM_DEBUG_KMS(
>> +drm_dbg_kms(&T->drm,
>> ...)
>> |
>> -DRM_DEBUG_ATOMIC(
>> +drm_dbg_atomic(&T->drm,
>> ...)
>> )
>> ...+>
>> }
>> 
>> Cc: Wambui Karuga <wambui.karugax@gmail.com>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>>  drivers/gpu/drm/i915/display/intel_panel.c | 19 +++++++++++--------
>>  1 file changed, 11 insertions(+), 8 deletions(-)
>> 
>> diff --git a/drivers/gpu/drm/i915/display/intel_panel.c b/drivers/gpu/drm/i915/display/intel_panel.c
>> index 276f43870802..a080a623bed6 100644
>> --- a/drivers/gpu/drm/i915/display/intel_panel.c
>> +++ b/drivers/gpu/drm/i915/display/intel_panel.c
>> @@ -684,9 +684,10 @@ static void
>>  intel_panel_actually_set_backlight(const struct drm_connector_state *conn_state, u32 level)
>>  {
>>  	struct intel_connector *connector = to_intel_connector(conn_state->connector);
>> +	struct drm_i915_private *i915 = to_i915(connector->base.dev);
>
> This addition does not match with the cocci script mentioned in the
> commit description.
> Are you sure same script is used to generate this patch?

I've made some manual changes, such as adding locals first and then
running the script.

BR,
Jani.

>
>>  	struct intel_panel *panel = &connector->panel;
>>  
>> -	DRM_DEBUG_DRIVER("set backlight PWM = %d\n", level);
>> +	drm_dbg_kms(&i915->drm, "set backlight PWM = %d\n", level);
>>  
>>  	level = intel_panel_compute_brightness(connector, level);
>>  	panel->backlight.set(conn_state, level);
>> @@ -867,8 +868,8 @@ void intel_panel_disable_backlight(const struct drm_connector_state *old_conn_st
>>  	 * another client is not activated.
>>  	 */
>>  	if (dev_priv->drm.switch_power_state == DRM_SWITCH_POWER_CHANGING) {
>> -		drm_dbg(&dev_priv->drm,
>> -			"Skipping backlight disable on vga switch\n");
>> +		drm_dbg_kms(&dev_priv->drm,
>> +			    "Skipping backlight disable on vga switch\n");
>>  		return;
>>  	}
>>  
>> @@ -1244,7 +1245,7 @@ static u32 intel_panel_get_backlight(struct intel_connector *connector)
>>  
>>  	mutex_unlock(&dev_priv->backlight_lock);
>>  
>> -	drm_dbg(&dev_priv->drm, "get backlight PWM = %d\n", val);
>> +	drm_dbg_kms(&dev_priv->drm, "get backlight PWM = %d\n", val);
>>  	return val;
>>  }
>>  
>> @@ -1335,6 +1336,7 @@ static const struct backlight_ops intel_backlight_device_ops = {
>>  
>>  int intel_backlight_device_register(struct intel_connector *connector)
>>  {
>> +	struct drm_i915_private *i915 = to_i915(connector->base.dev);
>
> Same as above.
>
>>  	struct intel_panel *panel = &connector->panel;
>>  	struct backlight_properties props;
>>  
>> @@ -1374,14 +1376,15 @@ int intel_backlight_device_register(struct intel_connector *connector)
>>  					  &intel_backlight_device_ops, &props);
>>  
>>  	if (IS_ERR(panel->backlight.device)) {
>> -		DRM_ERROR("Failed to register backlight: %ld\n",
>> -			  PTR_ERR(panel->backlight.device));
>> +		drm_err(&i915->drm, "Failed to register backlight: %ld\n",
>> +			PTR_ERR(panel->backlight.device));
>>  		panel->backlight.device = NULL;
>>  		return -ENODEV;
>>  	}
>>  
>> -	DRM_DEBUG_KMS("Connector %s backlight sysfs interface registered\n",
>> -		      connector->base.name);
>> +	drm_dbg_kms(&i915->drm,
>> +		    "Connector %s backlight sysfs interface registered\n",
>> +		    connector->base.name);
>>  
>>  	return 0;
>>  }
>> -- 
>> 2.20.1
>> 
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2020-04-06 11:07 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-02 11:48 [Intel-gfx] [PATCH 01/17] drm/i915/audio: use struct drm_device based logging Jani Nikula
2020-04-02 11:48 ` [Intel-gfx] [PATCH 02/17] drm/i915/panel: " Jani Nikula
2020-04-06 10:54   ` Bharadiya,Pankaj
2020-04-06 11:07     ` Jani Nikula [this message]
2020-04-06 11:16       ` Bharadiya,Pankaj
2020-04-06 12:44         ` Jani Nikula
2020-04-07 11:16   ` Wambui Karuga
2020-04-02 11:48 ` [Intel-gfx] [PATCH 03/17] drm/i915/tc: " Jani Nikula
2020-04-07 11:26   ` Wambui Karuga
2020-04-02 11:48 ` [Intel-gfx] [PATCH 04/17] drm/i915/dp: " Jani Nikula
2020-04-06 11:04   ` Bharadiya,Pankaj
2020-04-06 12:50     ` Jani Nikula
2020-04-07 11:35   ` Wambui Karuga
2020-04-02 11:48 ` [Intel-gfx] [PATCH 05/17] drm/i915/crt: " Jani Nikula
2020-04-07 11:40   ` Wambui Karuga
2020-04-02 11:48 ` [Intel-gfx] [PATCH 06/17] drm/i915/debugfs: " Jani Nikula
2020-04-07 11:49   ` Wambui Karuga
2020-04-02 11:48 ` [Intel-gfx] [PATCH 07/17] drm/i915/bw: " Jani Nikula
2020-04-07 15:54   ` Wambui Karuga
2020-04-02 11:48 ` [Intel-gfx] [PATCH 08/17] drm/i915/state: " Jani Nikula
2020-04-08  7:59   ` Wambui Karuga
2020-04-02 11:48 ` [Intel-gfx] [PATCH 09/17] drm/i915/switcheroo: " Jani Nikula
2020-04-08  8:12   ` Wambui Karuga
2020-04-02 11:48 ` [Intel-gfx] [PATCH 10/17] drm/i915/uc: prefer " Jani Nikula
2020-04-08  8:31   ` Wambui Karuga
2020-04-02 11:48 ` [Intel-gfx] [PATCH 11/17] drm/i915/error: " Jani Nikula
2020-04-08  8:31   ` Wambui Karuga
2020-04-02 11:48 ` [Intel-gfx] [PATCH 12/17] drm/i915/pmu: " Jani Nikula
2020-04-08  8:42   ` Wambui Karuga
2020-04-02 11:48 ` [Intel-gfx] [PATCH 13/17] drm/i915/dram: " Jani Nikula
2020-04-08  8:43   ` Wambui Karuga
2020-04-02 11:48 ` [Intel-gfx] [PATCH 14/17] drm/i915/uncore: " Jani Nikula
2020-04-08  8:44   ` Wambui Karuga
2020-04-02 11:48 ` [Intel-gfx] [PATCH 15/17] drm/i915/stolen: " Jani Nikula
2020-04-08  8:45   ` Wambui Karuga
2020-04-02 11:48 ` [Intel-gfx] [PATCH 16/17] drm/i915/gt: " Jani Nikula
2020-04-08  8:49   ` Wambui Karuga
2020-04-15  7:01   ` Chris Wilson
2020-04-15 11:08     ` Jani Nikula
2020-04-02 11:48 ` [Intel-gfx] [PATCH 17/17] drm/i915/uc: " Jani Nikula
2020-04-08  8:51   ` Wambui Karuga
2020-04-02 12:41 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [01/17] drm/i915/audio: use " Patchwork
2020-04-03 12:11 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-04-07 11:12 ` [Intel-gfx] [PATCH 01/17] " Wambui Karuga
2020-04-08 10:54   ` Jani Nikula

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=87mu7olvnj.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=pankaj.laxminarayan.bharadiya@intel.com \
    --cc=wambui.karugax@gmail.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