Does GK20A itself have any kind of thermal protection capabilities?
Upstream SOCTHERM support is not yet available (though I have a driver
in my tree), so we are thinking of disabling CPU DVFS on boards that
don't have always-on active cooling for now. Same might be necessary for
GPU as well.
On 13.06.2017 01:52, Ben Skeggs wrote:
On 06/09/2017 10:25 PM, Mikko Perttunen wrote:
On Tegra186, powergating is handled by the BPMP power domain provider
and the "legacy" powergating API is not available. Therefore skip
these calls if we are attached to a power domain.
Thanks Mik
On Tegra186, powergating is handled by the BPMP power domain provider
and the "legacy" powergating API is not available. Therefore skip
these calls if we are attached to a power domain.
Signed-off-by: Mikko Perttunen <mperttu...@nvidia.com>
---
drivers/gpu/drm/nouveau/nvkm/engin
As with vga_init, this function doesn't make sense on non-PCI devices,
and the Thunderbolt check in it dereferences a NULL pointer in that
case. Add some code to skip this function when the device is not a PCI
device.
Signed-off-by: Mikko Perttunen <mperttu...@nvidia.com>
---
drivers/g
On Tegra186 systems with certain firmware revisions, leaving the GPU in
reset can cause a hang. To prevent this, don't leave the GPU in reset.
Signed-off-by: Mikko Perttunen <mperttu...@nvidia.com>
---
drivers/gpu/drm/nouveau/nvkm/engine/device/tegra.c | 3 ---
1 file changed, 3 del
On 11/10/2017 11:27 PM, Mikko Perttunen wrote:
Hello everyone,
it seems that GP10B support has regressed recently. With linux-next, I
need to modify device/base.c to set
.mmu = gp10b_mmu_new
for GP10B (makes sense - I guess this was left as gf100_mmu_new as a
typo) to probe. After
Hello everyone,
it seems that GP10B support has regressed recently. With linux-next, I
need to modify device/base.c to set
.mmu = gp10b_mmu_new
for GP10B (makes sense - I guess this was left as gf100_mmu_new as a
typo) to probe. After that, running a trivial testcase (running a NOP
},
{}
}
on top of next-20171121 works at least for a simple test.
Mikko
On 11/11/2017 03:02 PM, Mikko Perttunen wrote:
Bisection status report:
The latest commit I have gotten to work is
10842ba074e9 drm/nouveau: remove unused nouveau_fence_work()
i.e. the first bad commit is
d7722134b825 drm/nouveau
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
On 26.04.2018 15:41, Thierry Reding wrote:
On Wed, Apr 25, 2018 at 09:28:49AM -0600, Jordan Crouse wrote:
On Wed, Apr 25, 2018 at 12:10:47PM +0200, Thierry Reding wrote:
From: Thierry Reding
Depending on the kernel configuration, early ARM architecture setup code
may have
If memory allocation fails, `node->base.imem` does not get populated,
causing a NULL pointer dereference on instobj destruction. Fix this
by dereferencing it only if the allocation was successful.
Signed-off-by: Mikko Perttunen
---
drivers/gpu/drm/nouveau/nvkm/subdev/instmem/gk20a.c | 4 ++--
Hi,
I'm observing nouveau not initializing recently on linux-next on my
Tegra186 Jetson TX2 board. Specifically it looks like BO allocation is
failing when initializing the sync subsystem:
[ 21.858149] nouveau 1700.gpu: DRM: failed to initialise sync
subsystem, -28
I have been
uveau_bo_init(nvbo, size, align, domain, sg, robj);
if (ret)
return ret;
That works, thanks for the fix!
Tested-by: Mikko Perttunen
Mikko
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.or
13 matches
Mail list logo