linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kuogee Hsieh <quic_khsieh@quicinc.com>
To: Stephen Boyd <swboyd@chromium.org>, <agross@kernel.org>,
	<airlied@linux.ie>, <bjorn.andersson@linaro.org>,
	<daniel@ffwll.ch>, <dmitry.baryshkov@linaro.org>,
	<robdclark@gmail.com>, <sean@poorly.run>, <vkoul@kernel.org>
Cc: <quic_abhinavk@quicinc.com>, <aravindh@codeaurora.org>,
	<freedreno@lists.freedesktop.org>,
	<dri-devel@lists.freedesktop.org>,
	<linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/msm/dp: add connector type to enhance debug messages
Date: Tue, 25 Jan 2022 10:26:07 -0800	[thread overview]
Message-ID: <7155e3ab-daf1-4104-6712-1c4e3a328b56@quicinc.com> (raw)
In-Reply-To: <CAE-0n505fYR1zpgZnC=J7WSxp_gpn6mnda9TuVjmJD8vMRn2Rg@mail.gmail.com>


On 1/24/2022 5:50 PM, Stephen Boyd wrote:
> Quoting Kuogee Hsieh (2022-01-24 14:44:52)
>> DP driver is a generic driver which supports both eDP and DP.
>> For debugging purpose it is required to have capabilities to
>> differentiate message are generated from eDP or DP. This patch
>> add connector type into debug messages for this purpose.
>>
>> Signed-off-by: Kuogee Hsieh <quic_khsieh@quicinc.com>
>> ---
>>   drivers/gpu/drm/msm/dp/dp_ctrl.c    | 20 +++++------
>>   drivers/gpu/drm/msm/dp/dp_display.c | 71 ++++++++++++++++++++++++++-----------
>>   2 files changed, 60 insertions(+), 31 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/msm/dp/dp_ctrl.c b/drivers/gpu/drm/msm/dp/dp_ctrl.c
>> index 245e1b9..dcd0126 100644
>> --- a/drivers/gpu/drm/msm/dp/dp_ctrl.c
>> +++ b/drivers/gpu/drm/msm/dp/dp_ctrl.c
>> @@ -1396,6 +1396,8 @@ void dp_ctrl_phy_init(struct dp_ctrl *dp_ctrl)
>>
>>          dp_catalog_ctrl_phy_reset(ctrl->catalog);
>>          phy_init(phy);
>> +       DRM_DEBUG_DP("phy=%p init=%d power_on=%d\n",
>> +                       phy, phy->init_count, phy->power_count);
>>   }
>>
>>   void dp_ctrl_phy_exit(struct dp_ctrl *dp_ctrl)
>> @@ -1410,6 +1412,8 @@ void dp_ctrl_phy_exit(struct dp_ctrl *dp_ctrl)
>>
>>          dp_catalog_ctrl_phy_reset(ctrl->catalog);
>>          phy_exit(phy);
>> +       DRM_DEBUG_DP("phy=%p init=%d power_on=%d\n",
>> +                       phy, phy->init_count, phy->power_count);
>>   }
>>
>>   static bool dp_ctrl_use_fixed_nvid(struct dp_ctrl_private *ctrl)
>> @@ -1484,6 +1488,8 @@ static int dp_ctrl_deinitialize_mainlink(struct dp_ctrl_private *ctrl)
>>          phy_exit(phy);
>>          phy_init(phy);
>>
>> +       DRM_DEBUG_DP("phy=%p init=%d power_on=%d\n",
>> +                       phy, phy->init_count, phy->power_count);
>>          return 0;
>>   }
>>
> These are entirely new messages. Adding messages isn't mentioned in the
> commit text. Please either split this out or indicate in the commit text
> what's going on here.
>
>> @@ -1895,14 +1901,12 @@ int dp_ctrl_off_link_stream(struct dp_ctrl *dp_ctrl)
>>
>>          phy_power_off(phy);
>>
>> -       DRM_DEBUG_DP("After, phy=%x init_count=%d power_on=%d\n",
>> -               (u32)(uintptr_t)phy, phy->init_count, phy->power_count);
>> -
>>          /* aux channel down, reinit phy */
>>          phy_exit(phy);
>>          phy_init(phy);
>>
>> -       DRM_DEBUG_DP("DP off link/stream done\n");
>> +       DRM_DEBUG_DP("phy=%p init=%d power_on=%d\n",
> The DRM_DEBUG_DP macro says it's deprecated now and we should use
> drm_dbg_dp() instead. Can you use that macro instead? Then it looks like
> drm->dev can actually be any old struct device, so I guess we're allowed
> to pass in the particular instance of dp device this is for. Allowing us
> to figure out which DP device is actually printing messages.
where it say "deprecated"?
>> +                       phy, phy->init_count, phy->power_count);
>>          return ret;
>>   }
>>

  reply	other threads:[~2022-01-25 18:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-24 22:44 [PATCH] drm/msm/dp: add connector type to enhance debug messages Kuogee Hsieh
2022-01-25  1:50 ` Stephen Boyd
2022-01-25 18:26   ` Kuogee Hsieh [this message]
2022-01-26 10:58     ` Dmitry Baryshkov

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=7155e3ab-daf1-4104-6712-1c4e3a328b56@quicinc.com \
    --to=quic_khsieh@quicinc.com \
    --cc=agross@kernel.org \
    --cc=airlied@linux.ie \
    --cc=aravindh@codeaurora.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=daniel@ffwll.ch \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_abhinavk@quicinc.com \
    --cc=robdclark@gmail.com \
    --cc=sean@poorly.run \
    --cc=swboyd@chromium.org \
    --cc=vkoul@kernel.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;
as well as URLs for NNTP newsgroup(s).