From: Martin Peres <martin.peres-GANU6spQydw@public.gmane.org>
To: Samuel Pitoiset
<samuel.pitoiset-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH 2/2] clk/gf100: allow users to enable reclocking
Date: Thu, 24 Sep 2015 01:00:56 +0300 [thread overview]
Message-ID: <56032118.1000808@free.fr> (raw)
In-Reply-To: <1443043254-12382-2-git-send-email-samuel.pitoiset-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On 24/09/15 00:20, Samuel Pitoiset wrote:
> Only the core clock is currently supported.
>
> Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com>
> ---
> drm/nouveau/nvkm/subdev/clk/gf100.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drm/nouveau/nvkm/subdev/clk/gf100.c b/drm/nouveau/nvkm/subdev/clk/gf100.c
> index a52b7e7..807305a 100644
> --- a/drm/nouveau/nvkm/subdev/clk/gf100.c
> +++ b/drm/nouveau/nvkm/subdev/clk/gf100.c
> @@ -462,5 +462,5 @@ gf100_clk_new(struct nvkm_device *device, int index, struct nvkm_clk **pclk)
> return -ENOMEM;
> *pclk = &clk->base;
>
> - return nvkm_clk_ctor(&gf100_clk, device, index, false, &clk->base);
> + return nvkm_clk_ctor(&gf100_clk, device, index, true, &clk->base);
> }
What changed that suddenly made reclocking OK? You really need to prove
it is and a few hours of testing are not enough ;)
Make sure that the clock tree is parsed correctly, then programmed
correctly. Make sure that reclocking while the card is being used is
also kind of stable, at least on your card.
After that, you may enable it and test on more Fermis. Until then, this
patch is premature, at best.
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2015-09-23 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 21:20 [PATCH 1/2] fb/ramgf100: disable memory reclocking by default Samuel Pitoiset
[not found] ` <1443043254-12382-1-git-send-email-samuel.pitoiset-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-09-23 21:20 ` [PATCH 2/2] clk/gf100: allow users to enable reclocking Samuel Pitoiset
[not found] ` <1443043254-12382-2-git-send-email-samuel.pitoiset-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-09-23 22:00 ` Martin Peres [this message]
[not found] ` <56032118.1000808-GANU6spQydw@public.gmane.org>
2015-09-23 22:37 ` Samuel Pitoiset
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=56032118.1000808@free.fr \
--to=martin.peres-ganu6spqydw@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=samuel.pitoiset-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.