Display#
NvDisplay is the display architecture supported on
Linux starting in NVIDIA DriveOS 7.0.
Application Consideration#
The NvDisplay driver uses a hardware FIFO to submit the framebuffer to the display engine. This FIFO has a size of 4 KB.
Frame submissions from the application at a rate higher than the display FPS cause the FIFO to fill, and the display driver thread polls for available space in the FIFO for new submissions. This can lead to high CPU usage.
To avoid high CPU usage, the application must not perform frame submissions at a rate higher than the display FPS. The application must throttle the framebuffer submission rate using an appropriate mechanism.
- Color Management
- Display Picture Quality Pipeline
- Display Software Architectures
- OpenWFD
- NvDisplay Architecture Platform Restrictions
- Components
- Display Connector Configurations
- Display Suspend Resume
- Head to Window Assignment
- Static IMP
- Display Driver SetMode
- Display SerDes
- NvDisplay Behavior upon Unexpected Termination of the Client Process
- Display Virtualization
- Display Device Tree
- DSC Support
- Display SerDes in Automotive Systems
- Automotive Display Architecture Overview
- Display SerDes Driver Role
- Single Driver Module, Multiple Device Architecture
- Device Tree Integration & GPIO Properties
- Driver Scope & Architectural Boundaries
- Kernel Module Load Sequence & Dependencies
- Operating System Architecture Differences
- Summary & Key Takeaways
- Critical Success Factors
- NVDISP SerDes Link Training on HPD PLUG Flow
- Display TellTale CRCs
- Display Scaling
- Frozen Frame Detection