From: Alex Deucher <alexdeucher@gmail.com>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: "Harry Wentland" <harry.wentland@amd.com>,
"Leo Li" <sunpeng.li@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"David (ChunMing) Zhou" <David1.Zhou@amd.com>,
"Rodrigo Siqueira" <Rodrigo.Siqueira@amd.com>,
"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>,
"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/amd/display: Fix 64-bit division error on 32-bit platforms in mod_freesync_build_vrr_params
Date: Tue, 31 Mar 2020 10:37:48 -0400 [thread overview]
Message-ID: <CADnq5_NQKDHmaVsyEMFcwEcGbo9QCHoC5cZ_3DOO8wNY2e_LDA@mail.gmail.com> (raw)
In-Reply-To: <20200330221614.7661-1-natechancellor@gmail.com>
On Tue, Mar 31, 2020 at 3:38 AM Nathan Chancellor
<natechancellor@gmail.com> wrote:
>
> When building arm32 allyesconfig,
>
> ld.lld: error: undefined symbol: __aeabi_uldivmod
> >>> referenced by freesync.c
> >>> gpu/drm/amd/display/modules/freesync/freesync.o:(mod_freesync_build_vrr_params) in archive drivers/built-in.a
> >>> did you mean: __aeabi_uidivmod
> >>> defined in: arch/arm/lib/lib.a(lib1funcs.o)
>
> Use div_u64 in the two locations that do 64-bit divisior, which both
> have a u64 dividend and u32 divisor.
>
> Fixes: 349a370781de ("drm/amd/display: LFC not working on 2.0x range monitors")
> Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>
Applied. Thanks!
Alex
> ---
> drivers/gpu/drm/amd/display/modules/freesync/freesync.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/display/modules/freesync/freesync.c b/drivers/gpu/drm/amd/display/modules/freesync/freesync.c
> index 8911f01671aa..c33454a9e0b4 100644
> --- a/drivers/gpu/drm/amd/display/modules/freesync/freesync.c
> +++ b/drivers/gpu/drm/amd/display/modules/freesync/freesync.c
> @@ -761,10 +761,10 @@ void mod_freesync_build_vrr_params(struct mod_freesync *mod_freesync,
>
> // If a monitor reports exactly max refresh of 2x of min, enforce it on nominal
> rounded_nominal_in_uhz =
> - ((nominal_field_rate_in_uhz + 50000) / 100000) * 100000;
> + div_u64(nominal_field_rate_in_uhz + 50000, 100000) * 100000;
> if (in_config->max_refresh_in_uhz == (2 * in_config->min_refresh_in_uhz) &&
> in_config->max_refresh_in_uhz == rounded_nominal_in_uhz)
> - min_refresh_in_uhz = nominal_field_rate_in_uhz / 2;
> + min_refresh_in_uhz = div_u64(nominal_field_rate_in_uhz, 2);
>
> if (!vrr_settings_require_update(core_freesync,
> in_config, (unsigned int)min_refresh_in_uhz, (unsigned int)max_refresh_in_uhz,
> --
> 2.26.0
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2020-03-31 14:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 22:16 [PATCH] drm/amd/display: Fix 64-bit division error on 32-bit platforms in mod_freesync_build_vrr_params Nathan Chancellor
2020-03-31 14:37 ` Alex Deucher [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=CADnq5_NQKDHmaVsyEMFcwEcGbo9QCHoC5cZ_3DOO8wNY2e_LDA@mail.gmail.com \
--to=alexdeucher@gmail.com \
--cc=David1.Zhou@amd.com \
--cc=Rodrigo.Siqueira@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=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;
as well as URLs for NNTP newsgroup(s).