public inbox for linux-arm-msm@vger.kernel.org
 help / color / mirror / Atom feed
From: abhinavk@codeaurora.org
To: Rob Clark <robdclark@gmail.com>
Cc: linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	pdhaval@codeaurora.org, Sean Paul <seanpaul@chromium.org>,
	aravindh@codeaurora.org
Subject: Re: [PATCH] drm/msm: call drm_mode_config_reset before drm_dev_register
Date: Thu, 11 Jun 2020 21:15:44 -0700	[thread overview]
Message-ID: <f99fefebb7a0a92c7e07afceb6abad4c@codeaurora.org> (raw)
In-Reply-To: <CAF6AEGsOX_QoOnMhqKuUHhhNjL_PgxF_5O7sYKi1Hkj5FmRpGw@mail.gmail.com>

Hi Rob

Thanks for the review.

Yes, this was a cleanup we noticed.

Abhinav
On 2020-06-11 20:35, Rob Clark wrote:
> On Tue, Jun 9, 2020 at 5:47 PM Abhinav Kumar <abhinavk@codeaurora.org> 
> wrote:
>> 
>> As per the documentation of drm_dev_register, all drivers should
>> call drm_dev_register after all the initialization is completed.
>> This also means that drm_mode_config_reset should be done before
>> drm_dev_register.
>> 
>> Change the sequence to align with this documentation.
>> 
>> Signed-off-by: Abhinav Kumar <abhinavk@codeaurora.org>
> 
> I assume this is just a cleanup you noticed, and not fixing a bug you
> are hitting (in which case I'll pick it up next merge window, rather
> than -fixes)
> 
> Reviewed-by: Rob Clark <robdclark@gmail.com>
> 
>> ---
>>  drivers/gpu/drm/msm/msm_drv.c | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>> 
>> diff --git a/drivers/gpu/drm/msm/msm_drv.c 
>> b/drivers/gpu/drm/msm/msm_drv.c
>> index 29295dee2a2e..9e77cc7f1fa4 100644
>> --- a/drivers/gpu/drm/msm/msm_drv.c
>> +++ b/drivers/gpu/drm/msm/msm_drv.c
>> @@ -538,12 +538,12 @@ static int msm_drm_init(struct device *dev, 
>> struct drm_driver *drv)
>>                 }
>>         }
>> 
>> +       drm_mode_config_reset(ddev);
>> +
>>         ret = drm_dev_register(ddev, 0);
>>         if (ret)
>>                 goto err_msm_uninit;
>> 
>> -       drm_mode_config_reset(ddev);
>> -
>>  #ifdef CONFIG_DRM_FBDEV_EMULATION
>>         if (kms && fbdev)
>>                 priv->fbdev = msm_fbdev_init(ddev);
>> --
>> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora 
>> Forum,
>> a Linux Foundation Collaborative Project
>> 
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2020-06-12  4:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-10  0:46 [PATCH] drm/msm: call drm_mode_config_reset before drm_dev_register Abhinav Kumar
2020-06-12  3:35 ` Rob Clark
2020-06-12  4:15   ` abhinavk [this message]

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=f99fefebb7a0a92c7e07afceb6abad4c@codeaurora.org \
    --to=abhinavk@codeaurora.org \
    --cc=aravindh@codeaurora.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=pdhaval@codeaurora.org \
    --cc=robdclark@gmail.com \
    --cc=seanpaul@chromium.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