dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Abbas Raza <abbas_raza@mentor.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: drm init call takes large time
Date: Tue, 09 Jul 2013 01:26:15 +0500	[thread overview]
Message-ID: <51DB2067.1040808@mentor.com> (raw)
In-Reply-To: <20130702101444.GK5004@intel.com>

On 07/02/2013 03:14 PM, Ville Syrjälä wrote:
> On Sun, Jun 30, 2013 at 05:41:59AM +0500, Abbas Raza wrote:
>> From: Abbas Raza <Abbas_Raza@mentor.com>
>>
>> DRM_INFO calls in the drm init routines are causing a large delay at boot time
>> due to which imx_drm_init call average takes around 26 ms. Changing DRM_INFO to
>> DRM_DEBUG reduces startup time to < 3ms.
> 
> Serial console enabled?
> 
> Not that I think these printks are particularly useful...

Yes serial console is enabled. these printk's seem useful but they take lot of time, increasing the boot time.
> 
>> Signed-off-by: Abbas Raza <Abbas_Raza@mentor.com>
>> CC: David Airlie <airlied@linux.ie>
>> Acked-by: Dmitry Eremin-Solenikov <dmitry_eremin@mentor.com>
>> ---
>>  drivers/gpu/drm/drm_irq.c      | 6 +++---
>>  drivers/gpu/drm/drm_platform.c | 2 +-
>>  2 files changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/drm_irq.c b/drivers/gpu/drm/drm_irq.c
>> index c798eea..782f5ff 100644
>> --- a/drivers/gpu/drm/drm_irq.c
>> +++ b/drivers/gpu/drm/drm_irq.c
>> @@ -252,13 +252,13 @@ int drm_vblank_init(struct drm_device *dev, int num_crtcs)
>>  	if (!dev->_vblank_time)
>>  		goto err;
>>  
>> -	DRM_INFO("Supports vblank timestamp caching Rev 1 (10.10.2010).\n");
>> +	DRM_DEBUG("Supports vblank timestamp caching Rev 1 (10.10.2010).\n");
>>  
>>  	/* Driver specific high-precision vblank timestamping supported? */
>>  	if (dev->driver->get_vblank_timestamp)
>> -		DRM_INFO("Driver supports precise vblank timestamp query.\n");
>> +		DRM_DEBUG("Driver supports precise vblank timestamp query.\n");
>>  	else
>> -		DRM_INFO("No driver support for vblank timestamp query.\n");
>> +		DRM_DEBUG("No driver support for vblank timestamp query.\n");
>>  
>>  	/* Zero per-crtc vblank stuff */
>>  	for (i = 0; i < num_crtcs; i++) {
>> diff --git a/drivers/gpu/drm/drm_platform.c b/drivers/gpu/drm/drm_platform.c
>> index 82431dc..7649963 100644
>> --- a/drivers/gpu/drm/drm_platform.c
>> +++ b/drivers/gpu/drm/drm_platform.c
>> @@ -92,7 +92,7 @@ int drm_get_platform_dev(struct platform_device *platdev,
>>  
>>  	mutex_unlock(&drm_global_mutex);
>>  
>> -	DRM_INFO("Initialized %s %d.%d.%d %s on minor %d\n",
>> +	DRM_DEBUG("Initialized %s %d.%d.%d %s on minor %d\n",
>>  		 driver->name, driver->major, driver->minor, driver->patchlevel,
>>  		 driver->date, dev->primary->index);
>>  
>> -- 
>> 1.8.2
>>
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/dri-devel
> 

Thanks .
Abbas Raza

      reply	other threads:[~2013-07-08 20:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-30  0:41 [PATCH] drm: drm init call takes large time Abbas Raza
2013-07-02 10:14 ` Ville Syrjälä
2013-07-08 20:26   ` Abbas Raza [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=51DB2067.1040808@mentor.com \
    --to=abbas_raza@mentor.com \
    --cc=dri-devel@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