- 11 Jan, 2016 40 commits
-
-
Ben Skeggs authored
Signed-off-by:Ben Skeggs <bskeggs@redhat.com>
-
Karol Herbst authored
v2: remove error and only set link for pcie devices v6: remove check for pcie device Signed-off-by:Karol Herbst <nouveau@karolherbst.de>
-
Karol Herbst authored
Signed-off-by: -
Karol Herbst authored
Signed-off-by: -
Karol Herbst authored
v2: rename functions v3: remove pcie2 accessors v6: fix alignement and line width, also remove useless code Signed-off-by: -
Karol Herbst authored
v5: don't set kepler func pointers v6: fix alignment and line length
-
Karol Herbst authored
v5: don't set fermi or kepler func pointers v6: fix alignment
-
Karol Herbst authored
v2: rename and group functions v4: change copyright information move printing of pcie speeds into oneinit, rename all pcie functions to nvkm_pcie_* don't try to raise the pcie version when no higher one is supported v5: revert Copyright changes and rename nvkm_pcie_raise_version to nvkm_pcie_set_version v6: remove some useless pci_is_pcie checks and rework messages Signed-off-by: -
Karol Herbst authored
v2: change email used in header v4: change Copyright information v5: revert Copyright changes Signed-off-by: -
Karol Herbst authored
v2: change email used in header v4: change Copyright information v5: revert Copyright changes Signed-off-by: -
Ben Skeggs authored
fdo#93634 Signed-off-by: -
Karol Herbst authored
Signed-off-by:
-
Karol Herbst authored
Signed-off-by:
-
Karol Herbst authored
Signed-off-by:
-
Karol Herbst authored
Signed-off-by:
-
Karol Herbst authored
We will need our own debugfs_init and cleanup functions, because nouveau_drm isn't ready while the DRM ones are called by DRM. Signed-off-by:
-
Karol Herbst authored
v2: use the same object for private data as with the drm debugfs functions Signed-off-by:
-
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ilia Mirkin authored
Signed-off-by:
Ilia Mirkin <imirkin@alum.mit.edu> Signed-off-by:
-
Ben Skeggs authored
From DCB 4.1 spec. Signed-off-by: -
Ben Skeggs authored
Differences from GM10x: - GM20x LTC count detection differs from GM10x - GM20x init doesn't require large page size setting Signed-off-by: -
Ben Skeggs authored
resman and nvgpu both do this, presumably for good reason. Signed-off-by: -
Ben Skeggs authored
GM20x doesn't require the priv ring timeout bumps that GK/GM10x have. Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Should be no functional change here. Signed-off-by: -
Alexandre Courbot authored
Commit 69c49382 ("drm/nouveau/instmem/gk20a: use direct CPU access") tried to be smart while using the DMA-API by managing the CPU mappings of buffers allocated with the DMA-API by itself. In doing so, it relied on dma_to_phys() which is an architecture-private function not available everywhere. This broke the build on several architectures. Since there is no reliable and portable way to obtain the physical address of a DMA-API buffer, stop trying to be smart and just use the CPU mapping that the DMA-API can provide. This means that buffers will be CPU-mapped for all their life as opposed to when we need them, but anyway using the DMA-API here is a fallback for when no IOMMU is available so we should not expect optimal behavior. This makes the IOMMU and DMA-API implementations of instmem diverge enough that we should maybe put them into separate files... Signed-off-by:
Alexandre Courbot <acourbot@nvidia.com> Signed-off-by:
-
Alexandre Courbot authored
The LRU list used for recycling CPU mappings was handling concurrency very poorly. For instance, if an instobj was acquired twice before being released once, it would end up into the LRU list even though there is still a client accessing it. This patch fixes this by properly counting how many clients are currently using a given instobj. While at it, we also raise errors when inconsistencies are detected, and factorize some code. Signed-off-by:
-
