search for: nvkm_mem_target_host

Displaying 9 results from an estimated 9 matches for "nvkm_mem_target_host".

2016 Mar 01
1
[PATCH 1/2] fifo/gf100: take runlist target into account
...arget; mutex_lock(&subdev->mutex); cur = fifo->runlist.mem[fifo->runlist.active]; @@ -67,7 +68,10 @@ gf100_fifo_runlist_commit(struct gf100_fifo *fifo) } nvkm_done(cur); - nvkm_wr32(device, 0x002270, nvkm_memory_addr(cur) >> 12); + target = (nvkm_memory_target(cur) == NVKM_MEM_TARGET_HOST) ? 0x3 : 0x0; + + nvkm_wr32(device, 0x002270, (nvkm_memory_addr(cur) >> 12) | + (target << 28)); nvkm_wr32(device, 0x002274, 0x01f00000 | nr); if (wait_event_timeout(fifo->runlist.wait, -- 2.7.2
2023 Jan 27
3
[REGRESSION] GM20B probe fails after commit 2541626cfb79
...tecnico.ulisboa.pt> wrote: > > > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote: > > > > As a quick check can you try changing > > > > > > > > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target > > > > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ? > > > In addition to Dave's change, can you try changing the > > nvkm_falcon_load_dmem() call in gm20b_pmu_init() to: > > > > nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args, > > sizeof(args), 0, false); > > Hell...
2023 Jan 29
2
[REGRESSION] GM20B probe fails after commit 2541626cfb79
...> On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote: > > > > > > As a quick check can you try changing > > > > > > > > > > > > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target > > > > > > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ? > > > > > > > In addition to Dave's change, can you try changing the > > > > nvkm_falcon_load_dmem() call in gm20b_pmu_init() to: > > > > > > > > nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,...
2017 Nov 10
2
GP10B regression
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 method in 3D class) fails with [ 110.084649] nouveau 17000000.gpu: fifo: read fault at 0000011000 engine 06
2017 Nov 11
0
GP10B regression
...some patches/hacks are needed: - in mmu/gp10b.c, in the constructor we need to select the GM200 path - the GP100 path seems to not to work - as mentioned in the first mail, we need to set .mmu = gp10b_mmu_new, - and in nouveau_mem_memory_target we need to return NVKM_MEM_TARGET_NCOH instead of NVKM_MEM_TARGET_HOST. Cheers, Mikko 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...
2023 Jan 15
3
[REGRESSION] GM20B probe fails after commit 2541626cfb79
...74] nouveau 57000000.gpu: DRM-master: Device allocation failed: -22 > [ 2.162905] nouveau: probe of 57000000.gpu failed with error -22 > > #regzbot introduced: 2541626cfb79 As a quick check can you try changing drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ? Dave. > > Thanks, > > Diogo Ivo >
2022 Dec 28
2
[REGRESSION] GM20B probe fails after commit 2541626cfb79
Hello, Commit 2541626cfb79 breaks GM20B probe with the following kernel log: [ 2.153892] ------------[ cut here ]------------ [ 2.153897] WARNING: CPU: 1 PID: 36 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:273 gf100_vmm_valid+0x2c4/0x390 [ 2.153916] Modules linked in: [ 2.153922] CPU: 1 PID: 36 Comm: kworker/u8:1 Not tainted 6.1.0+ #1 [ 2.153929] Hardware name: Google
2019 Sep 16
9
[PATCH 0/6] drm/nouveau: Preparatory work for GV11B support
From: Thierry Reding <treding at nvidia.com> Hi Ben, these are a couple of patches that are in preparation for adding GV11B support. The fundamental issue that these are trying to solve is that the GV11B is the first Tegra incarnation of the GPU where the aperture really matters. All prior generations would accept any of them. For dGPUs we usually allocate memory in VRAM, so the default
2017 Nov 21
2
GP10B regression
...; - in mmu/gp10b.c, in the constructor we need to select the GM200 path - > the GP100 path seems to not to work > > - as mentioned in the first mail, we need to set .mmu = gp10b_mmu_new, > > - and in nouveau_mem_memory_target we need to return > NVKM_MEM_TARGET_NCOH instead of NVKM_MEM_TARGET_HOST. > > Cheers, > Mikko > > 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 >&g...