dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Larouche <mathieu.larouche@matrox.com>
To: Jan Beulich <JBeulich@suse.com>, airlied@linux.ie
Cc: dri-devel@lists.freedesktop.org
Subject: Re: drm/mgag200: don't use uninitialized variables in mga_g200se_set_plls()
Date: Tue, 20 Oct 2015 10:47:06 -0400	[thread overview]
Message-ID: <562653EA.1030009@matrox.com> (raw)
In-Reply-To: <5624E21E02000078000AC48B@prv-mh.provo.novell.com>


On 19/10/2015 6:29 AM, Jan Beulich wrote:
> I can only guess that instead of testm/testn (which are either
> uninitialized or have pre-determined values at the end of the preceding
> loops) n and m were meant to be used by commit e829d7ef9f
> ("drm/mgag200: Add support for a new rev of G200e"). In any event the
> compiler is right in warning that testm/testn are possibly uninitalized
> at this point, i.e. some change is needed no matter what.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> Cc: Mathieu Larouche <mathieu.larouche@matrox.com>
> ---
>   drivers/gpu/drm/mgag200/mgag200_mode.c |    2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- 4.3-rc6/drivers/gpu/drm/mgag200/mgag200_mode.c
> +++ 4.3-rc6-mgag200-uninit/drivers/gpu/drm/mgag200/mgag200_mode.c
> @@ -194,7 +194,7 @@ static int mga_g200se_set_plls(struct mg
>   			}
>   		}
>   
> -		fvv = pllreffreq * testn / testm;
> +		fvv = pllreffreq * n / m;
>   		fvv = (fvv - 800000) / 50000;
>   
>   		if (fvv > 15)
>
>
>
>
If you are using n/m instead of testn/testm, you need to
add 1 to the variables to keep consistency. However, you
have the same issue where m/n could be used without being
initialized. So, I propose to keep testm, testn & testp
and initialized them with the default value.

Signed-off-by: Mathieu Larouche <mathieu.larouche@matrox.com>
---
  drivers/gpu/drm/mgag200/mgag200_mode.c | 6 ++++++
  1 file changed, 6 insertions(+)

diff --git a/drivers/gpu/drm/mgag200/mgag200_mode.c b/drivers/gpu/drm/mgag200/mgag200_mode.c
index c99d3fe..055799c 100644
--- a/drivers/gpu/drm/mgag200/mgag200_mode.c
+++ b/drivers/gpu/drm/mgag200/mgag200_mode.c
@@ -123,6 +123,9 @@ static int mga_g200se_set_plls(struct mga_device *mdev, long clock)
  		vcomax = 320000;
  		vcomin = 160000;
  		pllreffreq = 25000;
+		testm = 1;
+		testn = 17;
+		testp = 8;
  
  		delta = 0xffffffff;
  		permitteddelta = clock * 5 / 1000;
@@ -157,6 +160,9 @@ static int mga_g200se_set_plls(struct mga_device *mdev, long clock)
  		vcomax        = 1600000;
  		vcomin        = 800000;
  		pllreffreq    = 25000;
+		testm         = 1;
+		testn         = 50;
+		testp         = 16;
  
  		if (clock < 25000)
  			clock = 25000;

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-10-20 14:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-19 10:29 drm/mgag200: don't use uninitialized variables in mga_g200se_set_plls() Jan Beulich
2015-10-20 14:47 ` Mathieu Larouche [this message]
2015-10-20 15:00   ` Jan Beulich
2015-10-20 15:12     ` Mathieu Larouche
2015-10-20 15:55       ` [PATCH v2] " Jan Beulich

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=562653EA.1030009@matrox.com \
    --to=mathieu.larouche@matrox.com \
    --cc=JBeulich@suse.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    /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