diff options
| author | Thomas Zimmermann <[email protected]> | 2020-11-03 09:30:15 +0000 |
|---|---|---|
| committer | Thomas Zimmermann <[email protected]> | 2020-11-09 08:20:00 +0000 |
| commit | 222ec45f4c69dfa8cd02c72928147ac06dffffa2 (patch) | |
| tree | 8d308eeaecb657f1924c06503d55591f8f0ffc4e /drivers/gpu/drm/omapdrm/omap_gem.c | |
| parent | dma-buf-map: Add memcpy and pointer-increment interfaces (diff) | |
| download | kernel-222ec45f4c69dfa8cd02c72928147ac06dffffa2.tar.gz kernel-222ec45f4c69dfa8cd02c72928147ac06dffffa2.zip | |
drm/fb_helper: Support framebuffers in I/O memory
At least sparc64 requires I/O-specific access to framebuffers. This
patch updates the fbdev console accordingly.
For drivers with direct access to the framebuffer memory, the callback
functions in struct fb_ops test for the type of memory and call the rsp
fb_sys_ of fb_cfb_ functions. Read and write operations are implemented
internally by DRM's fbdev helper.
For drivers that employ a shadow buffer, fbdev's blit function retrieves
the framebuffer address as struct dma_buf_map, and uses dma_buf_map
interfaces to access the buffer.
The bochs driver on sparc64 uses a workaround to flag the framebuffer as
I/O memory and avoid a HW exception. With the introduction of struct
dma_buf_map, this is not required any longer. The patch removes the rsp
code from both, bochs and fbdev.
v7:
* use min_t(size_t,) (kernel test robot)
* return the number of bytes read/written, if any (fbdev testcase)
v5:
* implement fb_read/fb_write internally (Daniel, Sam)
v4:
* move dma_buf_map changes into separate patch (Daniel)
* TODO list: comment on fbdev updates (Daniel)
Signed-off-by: Thomas Zimmermann <[email protected]>
Reviewed-by: Daniel Vetter <[email protected]>
Reviewed-by: Sam Ravnborg <[email protected]>
Tested-by: Sam Ravnborg <[email protected]>
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'drivers/gpu/drm/omapdrm/omap_gem.c')
0 files changed, 0 insertions, 0 deletions
