Displaying 13 results from an estimated 13 matches similar to: "[PATCH 00/16] clk/gm20b: add basic driver"
2016 Jun 01
15
[PATCH 00/15] clk/tegra: improve code and add DFS support
This series adds support for GM20B PLL's Maxwell features, namely glitchless
switch and (more importantly) DFS support. DFS lets the PLL lower its output
speed according to input current variations, making the clock more stable and
allowing it to run safely at lower voltage.
All GM20B additions are done in the last patch, which consequently ends up
being considerably big ; fortunately, it
2014 Jul 10
10
[PATCH 0/3] drm/gk20a: support for reclocking
This series adds support for reclocking on GK20A. The first two patches touch
the clock subsystem to allow GK20A to operate, by making the presence of the
thermal and voltage devices optional, and allowing pstates to be provided
directly instead of being probed using the BIOS (which Tegra does not have).
The last patch adds the GK20A clock device. Arguably the clock can be seen as a
stripped-down
2014 Jul 26
5
[PATCH v2 0/3] drm/gk20a: support for reclocking
Second version of the gk20a clock patches. I have tried to keep the therm and
volt devices mandatory in the clock driver, but unfortunately they are too tied
to bios to allow this, at least for the moment. Consequently this version is
mostly a port of the first version to Ben's tree.
Ben, please let me know what I have done wrong in terms of integration to your
tree, as the main purpose of
2014 Jul 10
3
[PATCH 3/3] drm/gk20a: reclocking support
Hey Alex,
Thanks. I have a couple of questions and remarks, but really, those
should be treated as discussion points rather than anything else.
Besides some inline comments, I was curious whether it is not necessary
to pause PFIFO and the engines like done with at least NVA3-NVAF? Or is
the transition smooth enough?
op 10-07-14 09:34, Alexandre Courbot schreef:
> Add support for
2014 Jul 10
0
[PATCH 3/3] drm/gk20a: reclocking support
Add support for reclocking on GK20A, using a statically-defined pstates
table. The algorithms for calculating the coefficients and setting the
clocks are directly taken from the ChromeOS kernel.
Signed-off-by: Alexandre Courbot <acourbot at nvidia.com>
---
drivers/gpu/drm/nouveau/Makefile | 1 +
drivers/gpu/drm/nouveau/core/engine/device/nve0.c | 1 +
2016 Jan 13
5
[PATCH 0/2] allow partly reclocking on chipset
some chipset have working engine reclocking, but broken memory reclocking like
Fermi. We should for now, add the functionality to allow partly reclocking for
those.
Allthough this doesn't give as much performance as one might wish, it is till
noticeable and may improve performance enough to be noted.
Karol Herbst (2):
clk: seperate engine and memory reclock toggles
clk: allow engine
2014 Jul 11
1
[PATCH 0/3] drm/gk20a: support for reclocking
Hi Ben,
On 07/11/2014 10:07 AM, Ben Skeggs wrote:
> On Thu, Jul 10, 2014 at 5:34 PM, Alexandre Courbot <acourbot at nvidia.com> wrote:
>> This series adds support for reclocking on GK20A. The first two patches touch
>> the clock subsystem to allow GK20A to operate, by making the presence of the
>> thermal and voltage devices optional, and allowing pstates to be provided
2014 Nov 13
0
[PATCH] clk/gk20a: fix max VCO value
For some reason max_vco was set to a lower value that it can support,
which prevented some clock states to be applied. Fix this by setting it
to the same value as downstream.
Signed-off-by: Alexandre Courbot <acourbot at nvidia.com>
---
nvkm/subdev/clock/gk20a.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/nvkm/subdev/clock/gk20a.c b/nvkm/subdev/clock/gk20a.c
index
2014 Oct 02
0
[PATCH] drm/nouveau: gk20a: Fix type of dividend in do_div()
From: Thierry Reding <treding at nvidia.com>
The semantics of do_div() are (see include/asm-generic/div64.h):
uint32_t do_div(uint64_t *n, uint32_t base)
Using a different type will therefore cause the following warning (as
seen on xtensa/allmodconfig):
CC [M] drivers/gpu/drm/nouveau/core/subdev/clock/gk20a.o
In file included from arch/xtensa/include/generated/asm/div64.h:1:0,
2011 Mar 31
0
[PATCH 7/7] x86: cleanup bogus CONFIG_ACPI_PCI uses
We''re building for one case (CONFIG_ACPI_PCI defined) only, yet still
had the other case''s code in there. Additionally there was quite a bit
of pseudo-duplication between disabled(!) DMI scan and ACPI boot code.
acpi_pci_disabled had only a single reader, which is off by default
(i.e. must be enable on the command line), so it seems pointless to
keep it.
Signed-off-by: Jan
2016 Apr 18
0
[PATCH v4 31/37] clk: split out update code to nv40
this code will change for gf100 and newer
Signed-off-by: Karol Herbst <nouveau at karolherbst.de>
---
drm/nouveau/nvkm/subdev/clk/base.c | 14 ++++++--------
drm/nouveau/nvkm/subdev/clk/g84.c | 1 +
drm/nouveau/nvkm/subdev/clk/gf100.c | 1 +
drm/nouveau/nvkm/subdev/clk/gk104.c | 1 +
drm/nouveau/nvkm/subdev/clk/gk20a.c | 1 +
drm/nouveau/nvkm/subdev/clk/gm20b.c | 1 +
2017 Mar 05
15
[PATCH 0/9] clk subdev updates
This series addresses various issues inside the reclocking code:
1. after resume the set clocks are reset
2. reclocking not possible while GPU is suspended
3. nouveau always does full reclocks even if only a change of the voltage is
required
Some of the patches were part of the bigger reclocking series I sent months
ago, some things have changed though.
This is also preparation work of
2016 Apr 18
63
[PATCH v4 00/37] Volting/Clocking improvements for Fermi and newer
We are slowly getting there!
v4 of the series with some realy good improvements, so I am sure this is like
95% done and only needs some proper polishing and proper Reviews!
I also added the NvVoltOffsetmV module parameter, so that a user is able to
over and !under!-volt the GPU. Overvolting makes sense, when there are still
some reclocking issues left, which might be solved by a higher voltage.