AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: Harry Wentland <harry.wentland@amd.com>,
	airlied@gmail.com, natechancellor@gmail.com
Cc: sunpeng.li@amd.com, Anthony.Koo@amd.com,
	linux-kernel@vger.kernel.org, amd-gfx@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org, alexander.deucher@amd.com,
	Jun.Lei@amd.com, Bhawanpreet.Lakha@amd.com,
	christian.koenig@amd.com
Subject: Re: [PATCH] drm/amd/display: Use msleep instead of udelay for 8ms wait
Date: Tue, 25 Jun 2019 16:12:15 +0200	[thread overview]
Message-ID: <1561471935.2587.11.camel@pengutronix.de> (raw)
In-Reply-To: <20190625140046.31682-1-harry.wentland@amd.com>

Hi Harry,

Am Dienstag, den 25.06.2019, 10:00 -0400 schrieb Harry Wentland:
> arm32's udelay only allows values up to 2000 microseconds. msleep
> does the trick for us here as there is no problem if this isn't
> microsecond accurate and takes a tad longer.

A "tad" longer in this case means likely double the intended wait.
Please see "SLEEPING FOR ~USECS OR SMALL MSECS ( 10us - 20ms)" in
Documentation/timers/timers-howto.txt.

The sleep here should use usleep_range. In general the DC code seems to
use quite a lot of the udelay busy waits. I doubt that many of those
occurrences are in atomic context, so could easily use a sleeping wait.

Digging further this seems to apply across amdgpu, not only DC.

Regards,
Lucas

> Signed-off-by: Harry Wentland <harry.wentland@amd.com>
> ---
>  drivers/gpu/drm/amd/display/dc/core/dc_link.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/amd/display/dc/core/dc_link.c
> b/drivers/gpu/drm/amd/display/dc/core/dc_link.c
> index 4c31930f1cdf..f5d02f89b3f9 100644
> --- a/drivers/gpu/drm/amd/display/dc/core/dc_link.c
> +++ b/drivers/gpu/drm/amd/display/dc/core/dc_link.c
> @@ -548,7 +548,7 @@ static void
> read_edp_current_link_settings_on_detect(struct dc_link *link)
>  			break;
>  		}
>  
> -		udelay(8000);
> +		msleep(8);
>  	}
>  
>  	ASSERT(status == DC_OK);

  parent reply	other threads:[~2019-06-25 14:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18  1:11 arm32 build failure after abe882a39a9c ("drm/amd/display: fix issue with eDP not detected on driver load") Nathan Chancellor
2019-06-25  3:59 ` Dave Airlie
2019-06-25 14:00   ` [PATCH] drm/amd/display: Use msleep instead of udelay for 8ms wait Harry Wentland
     [not found]     ` <20190625140046.31682-1-harry.wentland-5C7GfCeVMHo@public.gmane.org>
2019-06-25 14:03       ` Deucher, Alexander
2019-06-25 14:12     ` Lucas Stach [this message]
2019-06-25 14:26       ` Koenig, Christian

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=1561471935.2587.11.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=Anthony.Koo@amd.com \
    --cc=Bhawanpreet.Lakha@amd.com \
    --cc=Jun.Lei@amd.com \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=harry.wentland@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=natechancellor@gmail.com \
    --cc=sunpeng.li@amd.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