All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <natechancellor@gmail.com>
To: Anthony Koo <Anthony.Koo@amd.com>,
	Alex Deucher <alexander.deucher@amd.com>
Cc: "Jun Lei" <Jun.Lei@amd.com>,
	"Bhawanpreet Lakha" <Bhawanpreet.Lakha@amd.com>,
	"Harry Wentland" <harry.wentland@amd.com>,
	"Leo Li" <sunpeng.li@amd.com>,
	"Christian König" <christian.koenig@amd.com>,
	"David (ChunMing) Zhou" <David1.Zhou@amd.com>,
	amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: arm32 build failure after abe882a39a9c ("drm/amd/display: fix issue with eDP not detected on driver load")
Date: Mon, 17 Jun 2019 18:11:24 -0700	[thread overview]
Message-ID: <20190618011124.GA67760@archlinux-epyc> (raw)

Hi all,

After commit abe882a39a9c ("drm/amd/display: fix issue with eDP not
detected on driver load") in -next, arm32 allyesconfig builds start
failing at link time:

arm-linux-gnueabi-ld: drivers/gpu/drm/amd/display/dc/core/dc_link.o: in
function `dc_link_detect':
dc_link.c:(.text+0x260c): undefined reference to `__bad_udelay'

arm32 only allows a udelay value of up to 2000, see
arch/arm/include/asm/delay.h for more info.

Please look into this when you have a chance!
Nathan

             reply	other threads:[~2019-06-18  1:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18  1:11 Nathan Chancellor [this message]
2019-06-25  3:59 ` arm32 build failure after abe882a39a9c ("drm/amd/display: fix issue with eDP not detected on driver load") Dave Airlie
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
2019-06-25 14:00     ` 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
2019-06-25 14:26       ` Koenig, Christian
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=20190618011124.GA67760@archlinux-epyc \
    --to=natechancellor@gmail.com \
    --cc=Anthony.Koo@amd.com \
    --cc=Bhawanpreet.Lakha@amd.com \
    --cc=David1.Zhou@amd.com \
    --cc=Jun.Lei@amd.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.