Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
linux
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
linux
Commits
acb16cfa
Commit
acb16cfa
authored
Nov 01, 2017
by
Ben Skeggs
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
drm/nouveau: replace use of cpu_coherent with memory types
Signed-off-by:
Ben Skeggs
<
bskeggs@redhat.com
>
parent
b3472020
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
11 additions
and
2 deletions
+11
-2
drivers/gpu/drm/nouveau/nouveau_bo.c
drivers/gpu/drm/nouveau/nouveau_bo.c
+11
-2
No files found.
drivers/gpu/drm/nouveau/nouveau_bo.c
View file @
acb16cfa
...
...
@@ -211,8 +211,17 @@ nouveau_bo_new(struct nouveau_cli *cli, u64 size, int align,
nvbo
->
bo
.
bdev
=
&
drm
->
ttm
.
bdev
;
nvbo
->
cli
=
cli
;
if
(
!
nvxx_device
(
&
drm
->
client
.
device
)
->
func
->
cpu_coherent
)
nvbo
->
force_coherent
=
flags
&
TTM_PL_FLAG_UNCACHED
;
/* This is confusing, and doesn't actually mean we want an uncached
* mapping, but is what NOUVEAU_GEM_DOMAIN_COHERENT gets translated
* into in nouveau_gem_new().
*/
if
(
flags
&
TTM_PL_FLAG_UNCACHED
)
{
/* Determine if we can get a cache-coherent map, forcing
* uncached mapping if we can't.
*/
if
(
mmu
->
type
[
drm
->
ttm
.
type_host
].
type
&
NVIF_MEM_UNCACHED
)
nvbo
->
force_coherent
=
true
;
}
if
(
cli
->
device
.
info
.
family
>=
NV_DEVICE_INFO_V0_FERMI
)
{
nvbo
->
kind
=
(
tile_flags
&
0x0000ff00
)
>>
8
;
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment