From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Murad Masimov <m.masimov@maxima.ru>, Dave Airlie <airlied@redhat.com>
Cc: Thomas Zimmermann <tzimmermann@suse.de>,
Jocelyn Falempe <jfalempe@redhat.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org
Subject: Re: [PATCH] drm/mgag200: Apply upper limit for clock variable
Date: Mon, 11 Nov 2024 15:02:26 +0100 [thread overview]
Message-ID: <2cc01a92-ce55-4b05-aa3a-09a610a8dab5@wanadoo.fr> (raw)
In-Reply-To: <20241111134644.1507-1-m.masimov@maxima.ru>
Le 11/11/2024 à 14:46, Murad Masimov a écrit :
> If the value of the clock variable is higher than 800000, the value of the
> variable m, which is used as a divisor, will remain zero, because
> (clock * testp) will be higher than vcomax in every loop iteration, which
> leads to skipping every iteration and leaving variable m unmodified.
>
> Clamp value of the clock variable to the upper limit, the same way it's done
> with the lower limit.
>
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>
> Fixes: 877507bb954e ("drm/mgag200: Provide per-device callbacks for PIXPLLC")
> Signed-off-by: Murad Masimov <m.masimov@maxima.ru>
> ---
> drivers/gpu/drm/mgag200/mgag200_g200se.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/mgag200/mgag200_g200se.c b/drivers/gpu/drm/mgag200/mgag200_g200se.c
> index 7a32d3b1d226..69402a591f59 100644
> --- a/drivers/gpu/drm/mgag200/mgag200_g200se.c
> +++ b/drivers/gpu/drm/mgag200/mgag200_g200se.c
> @@ -218,6 +218,8 @@ static int mgag200_g200se_04_pixpllc_atomic_check(struct drm_crtc *crtc,
>
> if (clock < 25000)
> clock = 25000;
> + else if (clock > 800000)
> + clock = 800000;
Maybe:
clock = clamp(clock, 25000, 800000);
to be less verbose?
CJ
> clock = clock * 2;
>
> /* Permited delta is 0.5% as VESA Specification */
> --
> 2.39.2
>
>
>
prev parent reply other threads:[~2024-11-11 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 13:46 Murad Masimov
2024-11-11 14:02 ` Christophe JAILLET [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=2cc01a92-ce55-4b05-aa3a-09a610a8dab5@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jfalempe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=m.masimov@maxima.ru \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®