diff options
author | Andy Lutomirski <luto@amacapital.net> | 2013-05-13 23:58:43 (GMT) |
---|---|---|
committer | Dave Airlie <airlied@redhat.com> | 2013-05-31 03:37:31 (GMT) |
commit | f435046d38af631920b299455db9e95dfc06d055 (patch) | |
tree | 34ed84a701acbb024af166e553743901f0b29cc1 /drivers/char/pcmcia/Kconfig | |
parent | ff47eaf24d01b5753e4964b10c606e0d711b143e (diff) | |
download | linux-fsl-qoriq-f435046d38af631920b299455db9e95dfc06d055.tar.xz |
drm, agpgart: Use pgprot_writecombine for AGP maps and make the MTRR optional
I'm not sure I understand the intent of the previous behavior. mmap
on /dev/agpgart and DRM_AGP maps had no cache flags set, so they
would be fully cacheable. But the DRM code (most of the time) would
add a write-combining MTRR that would change the effective memory
type to WC.
The new behavior just requests WC explicitly for all AGP maps.
If there is any code out there that expects cacheable access to the
AGP aperture (because the drm driver doesn't request an MTRR or
because it's using /dev/agpgart directly), then it will now end up
with a UC or WC mapping, depending on the architecture and PAT
availability. But cacheable access to the aperture seems like it's
asking for trouble, because, AIUI, the aperture is an alias of RAM.
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Andy Lutomirski <luto@amacapital.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
Diffstat (limited to 'drivers/char/pcmcia/Kconfig')
0 files changed, 0 insertions, 0 deletions