From: Martin Peres <martin.peres@labri.fr>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Ben Skeggs <bskeggs@redhat.com>
Subject: Re: [PATCH] nouveau reclocking on nv40 not working since 77145f1cbdf8d28b46ff8070ca749bad821e0774
Date: Fri, 16 Aug 2013 06:23:27 -0400 [thread overview]
Message-ID: <520DFD9F.1070006@labri.fr> (raw)
In-Reply-To: <1577797.nVIM0OkmpX@pali>
On 16/08/2013 03:16, Pali Rohár wrote:
> On Thursday 15 August 2013 18:23:06 Martin Peres wrote:
>> On 15/08/2013 13:46, Pali Rohár wrote:
>>> On Tuesday 13 August 2013 11:28:01 Pali Rohár wrote:
>>>> Hello,
>>>>
>>>> in commit 77145f1cbdf8d28b46ff8070ca749bad821e0774 was
>>>> introduced error which cause that on my Nvidia 6600GT card
>>>> reclocking not working anymore. There is missing assigment of
>>>> return value from pll_calc to ret.
>>>>
>>>> After this patch reclocking on my card working fine again.
>>>> Above broken commit was introduced in kernel 3.7, so consider
>>>> backporting this patch to older kernels too.
>>>>
>>>> Signed-off-by: Pali Rohár <pali.rohar@gmail.com>
>>>>
>>>> diff --git a/drivers/gpu/drm/nouveau/nv40_pm.c
>>>> b/drivers/gpu/drm/nouveau/nv40_pm.c index 3af5bcd..625f80d
>>>> 100644
>>>> --- a/drivers/gpu/drm/nouveau/nv40_pm.c
>>>> +++ b/drivers/gpu/drm/nouveau/nv40_pm.c
>>>> @@ -131,7 +131,7 @@ nv40_calc_pll(struct drm_device *dev, u32
>>>> reg, struct nvbios_pll *pll, if (clk < pll->vco1.max_freq)
>>>>
>>>> pll->vco2.max_freq = 0;
>>>>
>>>> - pclk->pll_calc(pclk, pll, clk, &coef);
>>>> + ret = pclk->pll_calc(pclk, pll, clk, &coef);
>>>>
>>>> if (ret == 0)
>>>>
>>>> return -ERANGE;
>>> Martin, can you look at another problem with my graphics card?
>> As I told you before, I'm away from my computers, so I cannot test the
>> patch. However,
>> this one seems quite obvious and should be pushed. Thanks.
> Yes, look at that diff of that problematic commit and you will see that ret
> here is missing. It is possible to push this patch to 3.11?
Please make a proper patch (generated by git format-patch or git
send-email) and
Ben will push it.
You add my Signed-off-by: Martin Peres <martin.peres@labri.fr>
Cheers
next prev parent reply other threads:[~2013-08-16 10:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 9:28 Pali Rohár
2013-08-15 17:46 ` Pali Rohár
2013-08-15 22:23 ` Martin Peres
2013-08-16 7:16 ` Pali Rohár
2013-08-16 10:23 ` Martin Peres [this message]
2013-08-16 12:57 ` [PATCH] nouveau: fix reclocking on nv40 Pali Rohár
2013-08-19 6:59 ` Pali Rohár
2013-08-21 0:24 ` Ben Skeggs
2013-09-08 11:25 ` Pali Rohár
2013-09-09 4:28 ` Ben Skeggs
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=520DFD9F.1070006@labri.fr \
--to=martin.peres@labri.fr \
--cc=airlied@linux.ie \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali.rohar@gmail.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
Powered by JetHome