[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <703110bc-91c8-d872-7709-5dec7aa7c5b0@kapsi.fi>
Date: Wed, 17 Jan 2018 23:11:13 +0200
From: Mikko Perttunen <cyndis@...si.fi>
To: Lyude Paul <lyude@...hat.com>, nouveau@...ts.freedesktop.org
Cc: Kate Stewart <kstewart@...uxfoundation.org>,
David Airlie <airlied@...ux.ie>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
Alexandre Courbot <acourbot@...dia.com>,
Ben Skeggs <bskeggs@...hat.com>,
Philippe Ombredanne <pombredanne@...b.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [Nouveau] [RFC 0/4] Implement full clockgating for Kepler1 and 2
On 01/16/2018 12:06 AM, Lyude Paul wrote:
> It's here! After a lot of investigation, rewrites, and traces, I present
> the patch series to implement all known levels of clockgating for
> Kepler1 and Kepler2 GPUs.
>
> Starting with Fermi GPUs (this is probably present on earlier GPUs as
> well, but with a far less easy to manage interface), nvidia added two
> clockgating levels that are handled mostly in firmware (with the
> exception of course, of the driver initially programming all of the
> register values containing engine delays and that stuff):
> - CG_CTRL - Main register for enabling/disabling clockgating for
> engines and hw blocks
> - BLCG - "Block-level clockgating", a deeper level of clockgating
> Starting with kepler2 as well, nvidia also introduced:
> - SLCG - "??? clockgating" even deeper level of clockgating
FWIW, SLCG stands for "second level clock gating".
Cheers,
Mikko
Powered by blists - more mailing lists