From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: trix@redhat.com
Cc: jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com,
rodrigo.vivi@intel.com, tvrtko.ursulin@linux.intel.com,
airlied@linux.ie, daniel@ffwll.ch, nathan@kernel.org,
ndesaulniers@google.com, matthew.d.roper@intel.com,
lucas.demarchi@intel.com, airlied@redhat.com,
imre.deak@intel.com, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH] drm/i915: rework the error handling in *_dpll_params
Date: Fri, 4 Mar 2022 23:11:54 +0200 [thread overview]
Message-ID: <YiKAmhXEye0fpAyF@intel.com> (raw)
In-Reply-To: <20220304210355.608898-1-trix@redhat.com>
On Fri, Mar 04, 2022 at 01:03:55PM -0800, trix@redhat.com wrote:
> From: Tom Rix <trix@redhat.com>
>
> Clang static analysis reports this issue
> intel_dpll.c:472:31: warning: The left operand of '-'
> is a garbage value [core.UndefinedBinaryOperatorResult]
> this_err = abs(clock.dot - target);
> ~~~~~~~~~ ^
>
> In a loop clock.dot is set on successful call to
> i9xx_calc_dpll_params(). If the call fails, the later
> *is_valid() will use the previous loop's clock.dot.
I don't think this can happen. intel_pll_is_valid() validates
all the dividers first and bails out if they are junk.
>
> The *_dpll_params functions return an arithmetic statement
> with the clock.dot as the variable. Change the error handler
> to set clock.dot to 0 and jump to the return statement.
>
> Fixes: dccbea3b0704 ("drm/i915: calculate the port clock rate along with other PLL params")
> Signed-off-by: Tom Rix <trix@redhat.com>
> ---
> drivers/gpu/drm/i915/display/intel_dpll.c | 32 ++++++++++++++---------
> 1 file changed, 20 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dpll.c b/drivers/gpu/drm/i915/display/intel_dpll.c
> index 0ae37fdbf2a5b..ba7cada704288 100644
> --- a/drivers/gpu/drm/i915/display/intel_dpll.c
> +++ b/drivers/gpu/drm/i915/display/intel_dpll.c
> @@ -309,11 +309,13 @@ int pnv_calc_dpll_params(int refclk, struct dpll *clock)
> {
> clock->m = clock->m2 + 2;
> clock->p = clock->p1 * clock->p2;
> - if (WARN_ON(clock->n == 0 || clock->p == 0))
> - return 0;
> + if (WARN_ON(clock->n == 0 || clock->p == 0)) {
> + clock->dot = 0;
> + goto end;
> + }
> clock->vco = DIV_ROUND_CLOSEST(refclk * clock->m, clock->n);
> clock->dot = DIV_ROUND_CLOSEST(clock->vco, clock->p);
> -
> +end:
> return clock->dot;
> }
>
> @@ -326,11 +328,13 @@ int i9xx_calc_dpll_params(int refclk, struct dpll *clock)
> {
> clock->m = i9xx_dpll_compute_m(clock);
> clock->p = clock->p1 * clock->p2;
> - if (WARN_ON(clock->n + 2 == 0 || clock->p == 0))
> - return 0;
> + if (WARN_ON(clock->n + 2 == 0 || clock->p == 0)) {
> + clock->dot = 0;
> + goto end;
> + }
> clock->vco = DIV_ROUND_CLOSEST(refclk * clock->m, clock->n + 2);
> clock->dot = DIV_ROUND_CLOSEST(clock->vco, clock->p);
> -
> +end:
> return clock->dot;
> }
>
> @@ -338,11 +342,13 @@ int vlv_calc_dpll_params(int refclk, struct dpll *clock)
> {
> clock->m = clock->m1 * clock->m2;
> clock->p = clock->p1 * clock->p2;
> - if (WARN_ON(clock->n == 0 || clock->p == 0))
> - return 0;
> + if (WARN_ON(clock->n == 0 || clock->p == 0)) {
> + clock->dot = 0;
> + goto end;
> + }
> clock->vco = DIV_ROUND_CLOSEST(refclk * clock->m, clock->n);
> clock->dot = DIV_ROUND_CLOSEST(clock->vco, clock->p);
> -
> +end:
> return clock->dot / 5;
> }
>
> @@ -350,12 +356,14 @@ int chv_calc_dpll_params(int refclk, struct dpll *clock)
> {
> clock->m = clock->m1 * clock->m2;
> clock->p = clock->p1 * clock->p2;
> - if (WARN_ON(clock->n == 0 || clock->p == 0))
> - return 0;
> + if (WARN_ON(clock->n == 0 || clock->p == 0)) {
> + clock->dot = 0;
> + goto end;
> + }
> clock->vco = DIV_ROUND_CLOSEST_ULL(mul_u32_u32(refclk, clock->m),
> clock->n << 22);
> clock->dot = DIV_ROUND_CLOSEST(clock->vco, clock->p);
> -
> +end:
> return clock->dot / 5;
> }
>
> --
> 2.26.3
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2022-03-04 21:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 21:03 [PATCH] drm/i915: rework the error handling in *_dpll_params trix
2022-03-04 21:11 ` Ville Syrjälä [this message]
2022-03-04 21:22 ` Ville Syrjälä
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=YiKAmhXEye0fpAyF@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=rodrigo.vivi@intel.com \
--cc=trix@redhat.com \
--cc=tvrtko.ursulin@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