Provide way for framebuffer driver to request mmap(2) mapping type

On ARM if memattr is not overriden mmap(2) maps framebuffer
memory as WBWA which means part of changes to content in userland
end up in cache and appear on screen gradually as cache lines are
evicted. This change adds configurable memattr that hardware fb
implementation can set to get the memory mapping type it
requires:

- Add new flag FB_FLAG_MEMATTR that indicates that framebuffer
    driver overrides default memattr
- Add new field fb_memattr to struct fb_info to specify requested
    memattr

Reviewed by:	ray
Differential Revision:	https://reviews.freebsd.org/D8064

1 files changed, 2 insertions, 0 deletions

diff --git a/sys/dev/fb/fbd.c b/sys/dev/fb/fbd.c
index b7e45040f65e..6110e4afd25e 100644
--- a/sys/dev/fb/fbd.c
+++ b/sys/dev/fb/fbd.c
@@ -178,6 +178,8 @@ fb_mmap(struct cdev *dev, vm_ooffset_t offset, vm_paddr_t *paddr, int nprot,
 			*paddr = vtophys((uint8_t *)info->fb_vbase + offset);
 		else
 			*paddr = info->fb_pbase + offset;
+		if (info->fb_flags & FB_FLAG_MEMATTR)
+			*memattr = info->fb_memattr;
 		return (0);
 	}
 	return (EINVAL);