Thread (8 messages) 8 messages, 2 authors, 2023-09-07

Re: [PATCH v2 2/5] fbdev: Replace fb_pgprotect() with fb_pgprot_device()

From: "Arnd Bergmann" <arnd@arndb.de>
Date: 2023-09-06 20:00:57
Also in: dri-devel, linux-arch, linux-m68k, linux-mips, linuxppc-dev, sparclinux

On Wed, Sep 6, 2023, at 10:35, Thomas Zimmermann wrote:
Rename the fbdev mmap helper fb_pgprotect() to fb_pgprot_device().
The helper sets VMA page-access flags for framebuffers in device I/O
memory. The new name follows pgprot_device(), which does the same for
arbitrary devices.

Also clean up the helper's parameters and return value. Instead of
the VMA instance, pass the individial parameters separately: existing
page-access flags, the VMAs start and end addresses and the offset
in the underlying device memory rsp file. Return the new page-access
flags. These changes align fb_pgprot_device() closer with pgprot_device.

Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
This makes sense as a cleanup, but I'm not sure the new naming is helpful.

The 'pgprot_device' permissions are based on Arm's memory attributes,
which have slightly different behavior for "device", "uncached" and
"writecombine" mappings. I think simply calling this one pgprot_fb()
or fb_pgprot() would be less confusing, since depending on the architecture
it appears to give either uncached or writecombine mappings but not
"device" on the architectures where this is different.

      Arnd
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help